ST-2026-116 · API endpoints & versions
Azure Blueprints enters phased retirement through January 2027
Azure Blueprints stopped accepting new definitions and versions on 31 July 2026 and proceeds through assignment restrictions before service retirement on 31 January 2027.
Previous state
Customers could create and modify blueprint definitions, versions and assignments through the portal, REST API, Azure CLI and Azure PowerShell.
Current state
Creation and update capabilities are removed in phases; at retirement the service and portal are removed, the API stops responding and unexported definitions, versions and assignments are deleted.
Affected users
Who needs to care
Azure customers using Blueprints definitions, versions, assignments, locks, REST APIs, Az CLI or Azure PowerShell commands.
Required response
What to do
Export blueprint data and migrate governance deployments to Azure Deployment Stacks with template specs or Git-based templates before retirement.
Evidence boundary
What the source does not prove
Resources created through Blueprints remain and are not deleted. The source also describes a later read/delete-only technical window, so this record preserves 31 January 2027 as the service-retirement authority without claiming every backend command vanishes at one identical instant.
Lifecycle history
Dated event sequence
- Phase 1
New blueprint definitions and versions can no longer be created.
- Phase 2
Definitions can no longer be modified and new assignments can no longer be created.
- Phase 3
Existing assignments can no longer be modified.
- Service retired
Blueprints is removed and unexported definitions, versions and assignments are deleted.
Evidence ledger
First-party sources
- 01Microsoft Learn — Azure Blueprints retirement
Official retirement documentation · 2026-06-26
Open official source ↗