Working with Azure Blueprint in Azure Portal
AZ-304 exam is retired. AZ-305 replacement is available.
In this, we will learn about the process to create and update your Azure resources with managing Azure Blueprint. However, Azure Blueprint provides a mechanism that allows you to create and update artifacts and assign them to environments. Moreover, using this can help in storing these artifacts and managing their versions and relate them to environments.
Creating a new Azure Blueprint in Azure Portal
- Firstly, in the Azure portal, go to All resources and search for Blueprint. There you will find the Blueprint service and click on it.
- Secondly, in the Azure Blueprint blade, the Getting started blade opens automatically. There just click on the Create button.
- After that, fill in a Name for the Blueprint.
- Fourthly, select the Blueprint definition location. Here, Blueprint will be stored. And, the location is an Azure Management Group. However, if you don’t have one, then you need to create one by searching for the Management Group in the All Resources tab in the Azure portal and create. Also make sure to move at least one subscription under that Management group, so that the subscription has that Management Group as a parent. You can also create different hierarchies, which determine the scope of your Blueprint.
- And, once you’ve filled in all of the Blueprint definition details, click on Next: Artifacts.
- Now, you can create the contents of the Blueprint. So, start adding things like Role assignments, ARM templates and Policies.
- Add some artifacts and also add at least one that creates a resource group.
- Lastly, click Save draft to save the Blueprint.
Publishing and assigning the Azure Blueprint
For publishing and assigning it to a subscription for deploying it check the below steps:
- Firstly, for publishing a blueprint you need to take it out of the draft status. That is to say you can’t make any changes to this version of the blueprint anymore. However, in the Blueprints Definitions menu, find and navigate to your blueprint.
- After that, click Publish Blueprint and assign a version number to it.
- Then, click Publish to mark the Blueprint as published and ready for assigning.
- Now, we can assign the published blueprint to a subscription. So, navigate to the blueprint again from the Blueprint Definitions menu. Then right-click on the blueprint and select Assign Blueprint.
- After that, pick the subscription that you want to assign the blueprint to and fill in a Name for the assignment.
- Then, you need to select a location that will be used for deploying the managed identity in which it will be used to deploy your blueprint. There, select the publication version of the blueprint that you want to assign.
- Just, leave the Lock setting to Don’t Lock and fill in the parameter values for the artifacts. However, some of them need values from you, like the identity of a user assignment or a name for a resource group.
- Lastly, click Assign for assigning the blueprint and make it start deploying the artifacts to the subscription.
And, now that the blueprint has been assigned, you can see its status in the Assigned Blueprints menu. From there, you can view details about the assignment and update or unassign the blueprint.
