When working with Microsoft Azure, you may want an environment for learning, whether for an individual or a team. This article aims to highlight some architectural considerations when implementing a Sandbox environment within the Microsoft Azure platform.
Your Sandbox isn’t a pathway to production; it’s a pathway to “CLICK, CLICK, OOPS.”
Inspired by Tagging Azure Resources with a Creator an Azure function + event grid solution, that will tag resources with the creator of the resource. I wanted to see if I could do the same thing using Azure Automation runbooks, instead of using event grid but a schedule instead, to make use of an already existing Azure Automation account.
It turns out you can, so let's take a look.
Enterprise Azure Policy as Code (EPAC) comprises a number of scripts which can be used in a CI/CD-based system or a semi-automated use to deploy Azure Policies, Policy Sets, Assignments, Policy Exemptions and Role Assignments! This is a great way to ensure that your Azure environment complies with your company's policies and standards, so let us look at it!
If you are running a Microsoft-hosted Azure DevOps agent, you may need to access a KeyVault to retrieve secrets. This is a common scenario when deploying resources to Azure.
In this post, I will show you how to access a KeyVault from an Azure DevOps pipeline by adding the IP of the Azure DevOps agent directly into your Azure Keyvault and removing it after it retrieves the secrets.
The Azure Naming Tool was created to help administrators define and manage their naming conventions for Azure resources while providing a simple interface for users to generate a compliant name. The tool was developed using a naming pattern based on Microsoft's best practices. Once an administrator has defined the organizational components, users can use the tool to generate a name for the desired Azure resource.
Today, we will use the Azure Naming Tool API to generate a name for our storage account bicep resource.
