Azure Blueprints

What it is

Azure Blueprints is a retiring Preview service that historically packaged governance artifacts—such as role assignments, policy assignments, resource groups, templates, and parameters—into a versioned baseline for subscriptions. It is not a service to adopt for new work.

Why it exists

Organizations used Blueprints to apply a repeatable starting baseline rather than setting up policy, roles, and templates separately for each subscription. Current designs should use the replacement services; existing Blueprint users need a planned migration before the service is removed.

Key ideas

• A definition was the reusable package; an assignment applied it at a subscription or management-group scope.
• The service is in phased retirement. As of 2026-09-16, new definitions and new versions cannot be created. Existing definitions and assignments remain accessible, but later phases further restrict creation and changes.
• On 2027-01-31, the service is scheduled to retire. Unexported definitions, versions, and assignments are automatically deleted; resources created through Blueprints remain, but Blueprint locks stop functioning.
• Export existing Blueprint data and migrate the intended result. ARM or Bicep templates define the artifacts; template specs or Git store/version them; Azure Deployment Stacks deploy and manage their lifecycle and deny settings.

How it fits (diagram)

Northwind example

Northwind finds an old Blueprint that assigned baseline policies and roles to production subscriptions. Maya exports the definition and assignments, identifies the resource locks that could change at retirement, and recreates the desired baseline in Bicep plus a Deployment Stack. She tests it in a non-production scope before moving the production assignment. She does not create a new Blueprint “just for now,” because new definitions are already unavailable.

Common confusion

• Azure Blueprints is not Azure Policy. A Blueprint could include policy assignments, but Policy is the service that evaluates and enforces policy rules.
• Blueprints is not a generic backup of deployed resources. Export before retirement, then migrate the required definitions and assignments.
• Existing Azure resources do not disappear merely because the Blueprint service retires. Review locks, governance, and lifecycle behavior separately.

Related

management-groups · azure-policy · bicep · arm-template · resource-group · northwind-traders-case-study

Sources and re-audit

• Microsoft Learn — Azure Blueprints retirement, checked 2026-09-16.