Azure Blueprints samples
Important
On July 11, 2026, Blueprints (Preview) will be deprecated. Migrate your existing blueprint definitions and assignments to Template Specs and Deployment Stacks. Blueprint artifacts are to be converted to ARM JSON templates or Bicep files used to define deployment stacks. To learn how to author an artifact as an ARM resource, see:
The following table includes links to samples for Azure Blueprints. Each sample is production quality and ready to deploy today to assist you in meeting your various compliance needs.
Standards-based blueprint samples
| Sample | Description |
|---|---|
| Australian Government ISM PROTECTED | Provides guardrails for compliance to Australian Government ISM PROTECTED. |
| Azure Security Benchmark Foundation | Deploys and configures Azure Security Benchmark Foundation. |
| Canada Federal PBMM | Provides guardrails for compliance to Canada Federal Protected B, Medium Integrity, Medium Availability (PBMM). |
| ISO 27001 | Provides guardrails for compliance with ISO 27001. |
| ISO 27001 Shared Services | Provides a set of compliant infrastructure patterns and policy guardrails that help toward ISO 27001 attestation. |
| ISO 27001 App Service Environment/SQL Database workload | Provides more infrastructure to the ISO 27001 Shared Services blueprint sample. |
| SWIFT CSP-CSCF v2020 | Aides in SWIFT CSP-CSCF v2020 compliance. |
| UK OFFICIAL and UK NHS Governance | Provides a set of compliant infrastructure patterns and policy guardrails that help toward UK OFFICIAL and UK NHS attestation. |
| CAF Foundation | Provides a set of controls to help you manage your cloud estate in alignment with the Microsoft Cloud Adoption Framework for Azure. |
| CAF Migrate landing zone | Provides a set of controls to help you set up for migrating your first workload and manage your cloud estate in alignment with the Microsoft Cloud Adoption Framework for Azure. |
Samples strategy
Describes a coordinate system where architectural complexity is on the X axis and compliance requirements are on the Y axis. As architectural complexity and compliance requirements increase, adopt standard Blueprint samples from the portal designated in region E. For customers getting started with Azure use Cloud Adoption Framework (C A F) based Foundation and Landing Zone blueprints designated by region A and B. The remaining space is attributed to custom blueprints created by customers are partners for regions C, D, and F.
The CAF foundation and the CAF Migrate landing zone blueprints assume that the customer is preparing an existing clean single subscription for migrating on-premises assets and workloads in to Azure. (Region A and B in the figure).
There's an opportunity to iterate on the sample blueprints and look for patterns of customizations that a customer is applying. There is also an opportunity to proactively address blueprints that are industry-specific like financial services and e-commerce (top end of Region B). Similarly, we envision building blueprints for complex architectural considerations like, multiple subscriptions, high availability, cross region resources and customers who are implementing controls over existing subscriptions and resources (Region C and D).
There are sample blueprints that address customer scenario where the compliance requirements are high and the architectural complexities are high (Region E in the figure). Region F in the figure is one that is addressed by customers and partners who are applying the sample blueprints and customizing each for their unique needs.
Next steps
- Learn about the blueprint lifecycle.
- Understand how to use static and dynamic parameters.
- Learn to customize the blueprint sequencing order.
- Find out how to make use of blueprint resource locking.
- Learn how to update existing assignments.
- Resolve issues during the assignment of a blueprint with general troubleshooting.