Azure Blueprints retirement

From 31 Jan 2027, the Blueprints API no longer responds, Azure CLI and PowerShell commands stop functioning, and Azure Blueprints is removed from the Azure portal. Blueprint definitions, versions and assignments that were not exported are deleted automatically, while resources created through blueprints are not deleted. The blueprint locks "Do Not Delete" and "Read Only" on resources stop functioning, which effectively sets them to a "Don't Lock" state. Microsoft extended the retirement from the July 11, 2026 date it announced in September 2023 and phased it: creating new blueprint definitions and versions is blocked from July 31, 2026, modifying definitions and creating assignments from October 31, 2026, and modifying existing assignments from December 31, 2026.

1. Go to the Blueprints portal to identify impacted blueprint artifacts and export the data before the retirement date.
2. Migrate to Azure deployment stacks for resource grouping, lifecycle and "deny assignments" enforcement.
3. Publish definitions as template specs, or store them in a template folder in Git for versioning.
4. Complete these changes ahead of the phased dates: July 31, 2026, October 31, 2026 and December 31, 2026. Microsoft states that Blueprints functionality decreases as the retirement phases progress.