Feature
Microsoft Azure
Azure Blueprints (Preview) is being retired on a phased timeline — new blueprint definitions can no longer be created as of 31 July 2026, and the service is fully removed on 31 January 2027; Microsoft points teams to Template Specs and Deployment Stacks
departs 31 Jan 2027
Quick answers
- Is it true that Azure Blueprints is being retired: no new definitions since 31 July 2026, full shutdown 31 January 2027?
- Yes. Microsoft Azure has officially announced it, effective 31 Jan 2027. If you use Azure Blueprints to package ARM templates, policy assignments, and role assignments into repeatable environment definitions, it is being retired.
- When does it take effect?
- 31 Jan 2027. Verified against the vendor's own announcement.
- What should I use instead?
- Export and rebuild before 31 January 2027.
What this means for you
If you use Azure Blueprints to package ARM templates, policy assignments, and role assignments into repeatable environment definitions, it is being retired. Microsoft has set a phased timeline that has already started: as of 31 July 2026, new blueprint definitions and versions can no longer be created; on 31 October 2026, existing blueprint definitions can no longer be modified and new blueprint assignments can no longer be created; on 31 December 2026, existing blueprint assignments can no longer be modified; and on 31 January 2027, Azure Blueprints is retired outright — the API stops responding, the Azure CLI and Azure PowerShell commands stop functioning, and Blueprints is removed from the Azure portal. Blueprint definitions, versions, and assignments that have not been exported by then are lost. Because it never left preview, Blueprints is easy to forget, but any landing-zone or governance automation that provisions subscriptions through a blueprint is on this clock: after 31 January 2027 the calls that assign or manage those blueprints simply fail.
Where to go
Export and rebuild before 31 January 2027. Microsoft recommends moving existing blueprint definitions and assignments to Deployment Stacks (its recommended successor for managing a resource lifecycle as a unit) and Template Specs (for storing and versioning the ARM templates themselves); blueprint artifacts convert to ARM JSON templates or Bicep files that a deployment stack then deploys. Because the first two phases have already passed, treat this as time-boxed: you cannot author new blueprint definitions any more, and from 31 October you cannot modify the ones you have, so the practical move is to export every blueprint definition and assignment you still rely on now, port each into a Template Spec plus a deployment stack, and validate the redeployment against a test subscription well before the January cut-off. The policy and role assignments a blueprint used to bundle are expressed directly through Azure Policy and RBAC in the new model.
- Deployment Stacks — Microsoft's recommended replacement for managing a group of Azure resources as a single lifecycle unit
- Template Specs — store and version the underlying ARM JSON / Bicep templates in Azure
- Azure Policy + RBAC assignments applied directly, for the governance that a blueprint previously bundled
Microsoft is retiring Azure Blueprints, the governance service that let teams package ARM templates, policy assignments, and role assignments into a single reusable definition and stamp it across subscriptions. It never left preview, and Microsoft has now set a dated, phased retirement that ends with the service being removed entirely.
According to the official Azure Blueprints retirement article, the timeline is:
- 31 July 2026 — new blueprint definitions and versions can no longer be created.
- 31 October 2026 — existing blueprint definitions can no longer be modified, and new blueprint assignments can no longer be created.
- 31 December 2026 — existing blueprint assignments can no longer be modified.
- 31 January 2027 — Azure Blueprints is retired. The API no longer responds, Azure CLI and Azure PowerShell commands stop functioning, and Blueprints is removed from the Azure portal. Anything not exported by then is lost.
The first two phases have already passed, so this is not a future warning — it is a live migration with a hard end date.
Who this affects
Anyone whose landing-zone, subscription-vending, or governance automation provisions environments through an Azure blueprint. Because Blueprints stayed in preview for its whole life, plenty of these deployments were set up once and left running; they will keep working until the phase dates catch up with them, and then the operations that create or manage the blueprint start failing — first authoring, then modification, then, on 31 January 2027, everything.
What to do
Move off Blueprints before 31 January 2027, and treat the intermediate dates as already binding:
- Export every blueprint definition and assignment you still depend on — you can no longer create new ones, and from 31 October you cannot modify existing ones.
- Re-target to Microsoft’s recommended successors: Deployment Stacks to manage a set of resources as one lifecycle unit, and Template Specs to store and version the ARM JSON or Bicep the blueprint used to carry. The policy and role assignments a blueprint bundled are applied directly through Azure Policy and RBAC in the new model.
- Validate the redeployment against a test subscription and confirm the same policies and role assignments land, then retire the blueprint. Do it with margin — once the January date passes, the API and CLI you would use to read the old definitions are gone.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure Blueprints retirement article (learn.microsoft.com/azure/governance/blueprints/blueprint-retirement). The phased dates — 31 July 2026 (no new definitions), 31 October 2026 (no modifications / no new assignments), 31 December 2026 (no assignment modifications), and 31 January 2027 (full retirement, API and CLI stop) — and the Template Specs / Deployment Stacks migration path are taken directly from that page. Backfill (B-058), verified-first against the primary source.
Put this countdown in your README
Building on Microsoft Azure? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/azure-blueprints-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.