In previous post, we have defined what are Azure Blueprints and how they are important to deploy Azure Environments with a set of compliance and standards packaged together into a single definition. In this post, we are going to go through Blueprint lifecycle making use of Azure Portal. Like many resources within Azure, a blueprint in Azure Blueprints has a typical and natural lifecycle. They’re created, deployed, and finally deleted when no longer needed or relevant. Blueprints supports standard lifecycle operations. It then builds upon them to provide additional levels of status that support common continuous
Read More »

Traditionally, Blueprints are used by architects and engineers to design and build new things. Blueprints are used to ensure that final product are built up to very specifications as laid out and are in the compliance with certain standards and requirements.

Azure Blueprints are used in the same way as traditional blueprints. Using Azure Blueprints, cloud architects and IT groups can design and deploy azure resources repeatedly that adhere to organizational standards, requirements and patterns. By leveraging Azure Blueprints, cloud architects can quickly build and deploy new environments that are always compliant ready. Using Azure Blueprints, teams can deploy new Azure Environments, with a set of built-in Azure Resources, with a trust that they are deploying in accordance with standards and compliance.
Read More »