Microsoft GovCloud

x Azure Government x

US Sov Cloud,

Azure blueprints and compliance on Azure Government

FedRAMP compliance

with them also adapted for other markets like Canada.

In this specific video of Azure Government video series, Mr. Alex Frankel, the Program Manager on the Azure Governance team, explains about the Azure Blueprints and the compliance over the Azure Government. At 2:28, he points out the common problem for which the solution has been determined.

The problem is that large enterprises look to efficiently build as well as manage the governed environments that include the subscriptions, resource, and management groups. Though the cloud architects help to achieve this, the period to finalize and implement the scalability and the functionality will be around 3-12 months.

The Process of generating Azure Blueprints

At 5:38, the Azure Blueprints play a vital role in deploying and updating the cloud environments in a rapid manner using the composable artifacts. The Role-based access controls, policy definitions, ARM templates are referred to as artifacts and are composed as Azure Blueprints. This is also known as the Bluetooth definition before the deployment process. At 8:15, he points out to the screen which displays the Microsoft Azure platform where you can easily access the Blueprints by searching in the search bar. He adds on that for easy access, you can pin the Blueprints option.

At 10:01, Mr. Alex shows the screen where the samples of the designed Blueprints is present. The Blueprints for the Basic Networking ( VNET), Resource Groups, ISO 27001: Shared services, ISO 27001: ASE/SQL Workload will be provided as samples that can be used by the people to create their blueprints. At 11:15, he elaborates that the name, description, definition, location needs to be mandatorily provided to create the Blueprint. At 13:27 he adds on that once the blueprint is created, they can be grouped under the headings. You can also edit the artifact that was created and also remove them if you require.

Assignment of the created Azure Blueprint

At 14:52, Mr. Alex briefs that once the artifact is created with the names and the definitions, you will find them listed. Once you are ready, you can publish the Blueprint you created. There are also search and sort options to manage the created Blueprints efficiently. The version of the Blueprint is also provided for your reference. At 15:42, he briefs that by assigning the Blueprint, it means that the blueprint is deployed to the environment. He elaborates that the subscription must be chosen along with the assignment name, location, and the Blueprint definition version. With this process, you can clearly mention to which subscription you desire to assign a specific Blueprint.

At 16:39, he puts forward the idea that the assignment created for the blueprint can be assigned access permissions. You have options to not lock your assignment, to select the never delete option and also the read-only option. At 18:13, he briefs that the Blue Parameters get named, provided location details, You need to enter the organization name, shared service location and the subnet address. He states that along with this, you will be able to preview the artifacts and then deploy. With the demo, the concept of how the Azure Blueprints service combines with Azure Policy is explained.

 

About the Author: CBPN Editor

Leave a Reply

Your email address will not be published. Required fields are marked *