Independent technology-migration research

PT-2026-015 · 17 July 2026

PlatformTrace

The public record of technology change.

Platform retirement bulletin · High confidence

Azure Blueprints enters phased retirement on 31 July 2026.

Microsoft has extended the original retirement date but introduced staged restrictions before full retirement on 31 January 2027.

Scope: deployed Azure resources remain. The retiring surface is Blueprints definitions, assignments, locks, portal and API management.

Verified timeline

  • 31 July 2026: new blueprint definitions and versions can no longer be created.
  • 31 October 2026: definitions can no longer be modified and new assignments cannot be created.
  • 31 December 2026: existing assignments can no longer be modified.
  • 31 January 2027: Azure Blueprints is retired.

Required action

Microsoft recommends exporting definitions, versions and assignments and migrating to Azure Deployment Stacks, with Template Specs also available for relevant artifacts.

Retirement consequence

At retirement the API stops responding, Blueprints is removed from the portal, unexported definitions and assignments are deleted, and Blueprint Locks stop functioning. Resources previously deployed through Blueprints remain in place.

Limitations

This record does not imply that Azure Policy, ARM templates, RBAC or resources deployed by Blueprints are themselves retired.

Sources

Microsoft Learn: Azure Blueprints retirement
Microsoft Learn: retirement FAQ