Azure Blueprints is a cloud-based development environment. It allows designers and developers to create new Azure services without having to learn how to program or code the backend of their service. In this article, we’ll show you how easy it is for beginners get started with Azure Blueprints
The “azure blueprints vs terraform” is a question that has been asked before. The “Getting Started with Azure Blueprints [With Step by Step Instructions]” will answer the question.
Consider regularly installing Azure resources such as resource groups, rules, and virtual networks. Humans are inept at doing activities repeatedly without failing. What if you could bundle these resources and deploy them all at once? Blueprints in Azure are the way to go.
Learn how to get started with Azure Blueprints, what it’s for, and how it may help you become more efficient while deploying resources on Azure in this post. You will have created a blueprint and deployed resources based on it by the conclusion of this tutorial.
What Do Azure Blueprints Entail?
Consider Azure Blueprints to be the blueprint for a construction. A blueprint assists architects, engineers, and laborers in ensuring that what they are creating adheres to the established standards and that the finished product meets the requirements.
Azure Blueprints are similar to templates in that they are preset sets of settings based on use cases. When installing new architectures, they incorporate components that assist firms in implementing best practices and rules. They assist in removing the guesswork from system configuration.
Blueprints are made up of components known as artifacts, which are Azure resources. As of this writing, there are four sorts of artifacts available:
- Resource group – A resource group is a container for organizing Azure resources.
- Role assignment — Assigns current users or groups to a built-in role to guarantee that only those who need access to Azure resources have it.
- Policy assignment — Defines which current Azure Policies will apply to the resources you’re deploying.
- Azure Resource Manager Template — Allows the blueprint to include existing Azure Resource Manager (ARM) templates.
Companies may tailor their designs to meet internal compliance and organizational guidelines.
Why do we need blueprints?
The purpose of cloud infrastructures is to enable businesses better manage their technological resources. However, the cloud includes a wide range of components, which complicates the design.
Microsoft’s cloud architects understand how these fundamental components should be put together, which is why blueprints were created. Companies may use blueprints to capitalize on these architects’ expertise.
IT teams may utilize and alter blueprints to meet their requirements instead of spending thousands of dollars and months of trial and error configuring systems. These blueprints will aid in the configuration of settings with the right components and, in certain cases, suitable access through security mechanisms.
ARM Templates vs. Blueprints
Users who are acquainted with Azure Resource Management (ARM) templates may question why they should utilize Blueprints because ARM templates can achieve much of the same tasks. What is the distinction?
Outside of Azure, ARM templates are documents that are normally saved locally or under source control. There is no longer any link or connectivity between the template and the deployed resources after utilizing an ARM template to deploy resources.
Azure Blueprints, on the other hand, maintains the link or relationship between the blueprint definition (what should be deployed) and the blueprint assignment (what was deployed) even after resources have been deployed. This link allows for better monitoring and auditing of deployment modifications.
Additionally, blueprints are native to Azure and are globally disseminated without user involvement using the Azure Cosmos DB in the backend. As a consequence, blueprints replicate automatically between Azure regions, relieving administrators of the burden of keeping copies.
Do you still have to pick between blueprints and ARM Templates after all that? Certainly not. Blueprints may include one or more ARM template artifacts if necessary, ensuring that existing ARM templates can be reused and that the time and work spent generating them will not be wasted.
Azure Regions and Blueprints
Microsoft Azure is made up of data centers located all around the world. End-users may access these data centers by region, which are classified by geography. When it comes to cloud governance and deployment, these regions are a critical component.
Azure Regional Pairs
Companies may opt to use Microsoft’s regional pairings for disaster recovery reasons when deciding on deployment areas. Two Azure areas in the same geographical make form a regional pair.
Microsoft performs scheduled server and equipment maintenance across regional pairings, ensuring that only one area in each pair is updated at any given moment. Microsoft will not do maintenance on both data centers specified as a pair at the same time when using regional pairings.
You may deploy resources in regional pairs using Azure Blueprints to guarantee that downtime is reduced, if not completely eliminated.
Regions to Avoid Due to Compliance Issues
When distributing systems and resources to specific locations, there may be concerns with compliance. Policies may be used with Azure Blueprints to limit access to limited zones.
If a user attempts to deploy to those areas using the blueprint, the rules of the blueprint will disallow it. This deployment plan may assist you in ensuring that your deployments adhere to regional legal and regulatory requirements.
How to Create and Remediate Compliance with Azure Policy
Creating Azure Blueprints: A Tutorial
Prepare to dig into the lesson now that you have a basic grasp of Azure Blueprints. Are you up for the challenge? Let’s investigate!
Azure Blueprints may be created in a variety of ways. Azure Blueprints may be created using Azure PowerShell, Azure CLI, REST API, ARM Template, and Azure Portal, depending on your desire or ability level. The Azure Portal will be used to develop blueprints in this course.
Getting Started with the Azure CLI is related.
You will create a simple Azure Blueprint in this tutorial that will deploy a resource group with a Contributor role assignment inside it.
You’ll need an Azure membership to follow along with this course. You can create a free Azure account if you don’t already have one. Azure Blueprints permissions are also required for your Azure user account.
The Definition Of A Blueprint
You’ll need to generate a blueprint definition when you’ve completed all of the criteria. A blueprint definition is a list of objects that must be deployed. Follow these steps to establish a blueprint definition.
1. Open your preferred web browser and go to the Azure Portal.
2. Once you’re in the Azure Portal, click All Services —> Management + Governance —> Blueprints.
The Blueprints menu blade is opened.
3. Click Create on the Blueprints | Getting Started page.
Choosing the Create option
4. Go to the Create blueprint page and choose Start with a blank blueprint. This will enable you to start again with a fresh blueprint.
Making a blueprint from scratch
5. In the Blueprint box on the Basics tab, type the name of the new blueprint. Only letters, digits, and dashes are permitted in names. BlueprintFTW is the blueprint name to utilize in this case.
To open the scope selection, click the ellipsis button to the right of the Definition location box.
Select the subscription where you wish to construct the blueprint from the Definition location fly-out and click Select. Click Next: Artifacts once you’ve selected your subscription.
A subscription or a management group might be the blueprint definition site. Only a subscription exists in this case.
Selecting the definition location and adding the blueprint name
6. You’ll find the artifacts list under the Artifacts tab, which should be empty since no artifacts have been entered yet. Under the Subscription tree, click the Add artifact button.
Expand the Artifact type dropdown menu and choose Resource group, then click Add on the Add artifact fly-out that opens. By include the Resource group artifact in the plan, the deployment is guaranteed to establish a new resource group.
A new Resource Group artifact is being added.
The Artifact display name, Resource Group Name, and Location will not be the same in every deployment. If you leave these parameters blank, you may change the values later when assigning the blueprint.
7. Finish by including a Role assignment item in the blueprint. This guarantees that upon deployment, Azure will add a role assignment to the resource group.
To begin, go to the Resource group branch and select the Add artifact button.
Expand the Artifact type dropdown menu and choose Role assignment, then click Add on the Add artifact fly-out that displays.
Select a built-in role from the list by clicking the Role dropdown box. The blueprint will need this role to be added to the resource group during deployment. Any Azure role is available to you. The Contributor role will be chosen in this scenario.
Click Add after you’ve chosen your decision.
Adding an item for role assignment
If you don’t add an assignee in the Add user, app, or group at this point, you’ll be able to select the assignee during the resource deployment, which is particularly useful if each deployment will have various assignees.
8. At this point, you’ve added two artifacts to the subscription where the blueprint was created. Finally, click Save Draft to finish the plan.
Following the construction, you’ll have a blueprint specification that will build a resource group with Contributor role access to the resources for a user or group.
Drafts are always the starting point for new plans. They’d only be given a fresh version once you’d published them.
The blueprint draft is being saved.
The draft blueprint will now appear in the list of blueprint definitions.
The new blueprint draft
Creating A Blueprint
Now that you’ve created the Blueprint definition, you’re ready to get it published. Creating A Blueprint makes it available to use for resource deployments. Follow the steps below to publish the draft blueprint.
1. Select the draft blueprint you previously saved from the list of blueprint definitions. BlueprintFTW is the name of the blueprint in this case.
2.To begin the publishing process, click Publish blueprint.
Choosing the Publish blueprint option
3. In the Version box on the Publish blueprint page, type the version you wish to attach to the blueprint. The version in this case is v1.0.
Every time you publish a blueprint, you must assign it a new version, which implies a blueprint might have several versions. Admins may keep track of modifications to published blueprints using versioning.
After that, enter a descriptive description for this version in the Change notes box and click Publish.
Creating a draft plan and assigning a version
You may view the latest updated version after successfully uploading the plan.
The Azure blueprint is now available.
When adding new objects, for example, you may need to change a blueprint from time to time. When you publish the blueprint, you’re really releasing a new version of it.
The blueprint is shown in two variations in the image below. The original blueprint was version v1.0, and the revised version is v2.0. Under the Published versions page, you can view the various blueprint versions.
Multiple variants of a blueprint
Developing A Blueprint
You’re now able to generate a blueprint assignment once you’ve published the blueprint. Assigning a blueprint to a subscription and subsequently deploying the artifacts under that subscription constitutes creating a blueprint assignment. A subscription may have several blueprint assignments.
To summarize, when you assign the blueprint you established in the previous step, it will create a resource group and a role assignment under that resource group.
Follow these procedures to allocate the blueprint.
1. Select Assign blueprint from the blueprint page.
by selecting Assign blueprint
2. On the Assign blueprint page, you must put in five details.
- This field is greyed off and will default to the subscription name from which the blueprint was built.
- Name of assignment — Give this blueprint assignment a distinctive name. Assignment-BlueprintFTW-01 is the name of the assignment in this case.
- Version of the blueprint definition – Select the blueprint version. There is just one blueprint version in this example, which is v1.0.
- Lock Assignment – Select your preferred resource locking mode. The choices are:
- Locked resources cannot be modified or deleted by those with authority.
- The deployed resources can’t be erased, but they may be changed.
- The deployed resources are read-only and cannot be removed or updated. To keep the resource unlocked, this example will choose Don’t lock.
- Managed Identity — Select whether to generate a temporary owner (System assigned) or manually designate an existing user (User assigned) as the subscription’s owner. All artifacts need this identity to be deployed. This example will use the identity supplied by the system. After the artifacts are deployed, Azure will immediately erase this identity.
- Select a location for the Azure managed identity that will be used to distribute the artifacts. The location in this case is East America.
Creating assignment information for the blueprint
3. Finally, fill in the Artifact parameters that you left blank while creating the blueprint.
- Set the name of the new resource group you wish to deploy. In this case, the term RG-BluePrintTest is used.
- Resource Group: Place – Select the location where the new resource group will be created. The location in this case is East America.
- [User group or application name]: Contributor – Assign the Contributor role to the resource group’s user, group, or application.
Click Assign after you’ve finished setting the parameter values.
Artifact parameter values must be specified.
Now that you’ve assigned the blueprint, Azure will begin deploying all artifacts defined in the blueprint. To check the deployment status, navigate back to Blueprints —> Assigned blueprints.
Click the Assignment-BlueprintFTW-01 assignment name you just generated in the blueprint assignments list. This will take you to the assignment’s property page.
Getting the assignment information from the blueprint
The assignment details for Assignment-BlueprintFTW-01 are now visible. The assignment status is successful, as shown below, and the list of deployed resources is at the bottom of the page.
Details of a successful blueprint assignment
This article aided you in taking the first step toward using Azure Blueprints. You should now be acquainted with Azure Blueprints and how they can help clients save time, headaches, and money!
You’ve learned how to use Azure Blueprints to deploy Azure resources by creating, publishing, and assigning them. Don’t stop there, however. Explore Azure Blueprints further!
How about editing a blueprint and re-publishing it? Or test if unDeveloping A Blueprint will remove the resources it previously deployed? Can you safely delete a blueprint if you don’t need it anymore? There’s a lot more you can learn with Azure Blueprints. Good luck!
Azure Blueprints is a cloud-based tool that allows you to create, edit and run your own interactive workflows. It also includes features like data visualization and collaboration, which are not available in the Azure portal. Reference: you can use azure blueprints to grant permissions to a resource.
- azure blueprints vs arm template
- azure policy vs blueprint
- azure blueprints example
- azure security blueprints
- you can add an azure resource manager template to an azure blueprint