SaaS
Microsoft
Azure Deployment Environments (ADE), the service for on-demand, template-based environment provisioning and developer self-service, will be retired on 22 February 2027; the closing-down process begins 14 September 2026 and Microsoft names no drop-in successor
departs 22 Feb 2027
Quick answers
- Is it true that Azure Deployment Environments will be retired on 22 February 2027 — plan a replacement for self-service environment provisioning?
- Yes. Microsoft has officially announced it, effective 22 Feb 2027. Azure Deployment Environments (ADE) — the service that lets platform teams publish infrastructure-as-code **templates in catalogs** and lets developers spin up governed, pre-approved **environments on demand** through projects and environment types — will be **retired on 22 February 2027**, with the closing-down process beginning **14 September 2026**.
- When does it take effect?
- 22 Feb 2027. Verified against the vendor's own announcement.
- What should I use instead?
- There is no named successor, so this is a design decision, not a swap.
What this means for you
Azure Deployment Environments (ADE) — the service that lets platform teams publish infrastructure-as-code **templates in catalogs** and lets developers spin up governed, pre-approved **environments on demand** through projects and environment types — will be **retired on 22 February 2027**, with the closing-down process beginning **14 September 2026**. After retirement the service will no longer be available. If your organization uses ADE for developer self-service environment provisioning — catalogs of ARM/Bicep/Terraform templates, project-scoped environment types, and the governance/access-control layer that sits around them — that entire provisioning path goes away, and Microsoft does **not** name a one-to-one successor. The notice says to "identify the replacement approach that best supports your requirements," which is vendor language for *there is no drop-in migration* — you choose the target platform. The governance piece is the subtle part: ADE didn't just provision resources, it gave platform engineering a controlled catalog and self-service guardrails, and whatever replaces it has to reproduce that control, not just the `az` command that creates a resource group.
Where to go
There is no named successor, so this is a design decision, not a swap. Microsoft's recommended steps: inventory your current environments, templates, catalogs and provisioning workflows; determine the target platform that will replace ADE for your organization; then test the migration path end to end — including governance, access control, infrastructure-as-code compatibility, and developer-workflow readiness — and communicate internal timelines to platform engineering, developers and administrators. In practice most teams will rebuild the capability on a direct IaC pipeline (Bicep or Terraform run through Azure DevOps or GitHub Actions), optionally fronted by a developer portal (for example Backstage) to restore the self-service catalog experience. Start assessing now: the retirement is in February 2027, but re-platforming a governed self-service provisioning system is a multi-month effort.
- Direct infrastructure-as-code pipelines (Bicep or Terraform via Azure DevOps / GitHub Actions)
- Azure Developer CLI (azd) for templated provisioning workflows
- An internal developer portal (e.g. Backstage) to restore the self-service catalog layer
Azure Deployment Environments (ADE) — the service that gives platform teams a way to publish infrastructure-as-code templates in catalogs and gives developers on-demand, governed environments through projects and environment types — will be retired on 22 February 2027. The closing-down process begins 14 September 2026, and after retirement the service will no longer be available.
Where this hurts
ADE’s value was never just “create some Azure resources.” It was self-service with guardrails: a catalog of approved ARM/Bicep/Terraform templates, project-scoped environment types, and the access-control and governance layer that let a platform team say “developers can provision these environments, within these limits, without filing a ticket.” When ADE goes away, you lose that whole control surface, not just a provisioning command.
Microsoft names no drop-in successor. The notice tells customers to “identify the replacement approach that best supports your requirements” — which means the migration target is a decision you make, not a button Microsoft provides. That is the hard part: reproducing governed self-service is more than re-pointing a script.
What to do
Microsoft’s recommended sequence:
- Inventory your environments, templates, catalogs and provisioning workflows.
- Decide the target platform that will replace ADE for your organization.
- Test the migration path end to end — governance, access control, infrastructure-as-code compatibility, and developer-workflow readiness.
- Communicate timelines to platform engineering, developers and administrators.
In practice, most teams will rebuild the capability on a direct IaC pipeline — Bicep or Terraform run through Azure DevOps or GitHub Actions — and, where the self-service catalog matters, front it with an internal developer portal such as Backstage to restore the “pick an environment and go” experience. The Azure Developer CLI (azd) covers templated provisioning for simpler cases. Begin assessing now: February 2027 sounds distant, but re-platforming a governed self-service provisioning system is a multi-month effort.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure Updates retirement notice (id=567934), verified against the Microsoft release-communications API (releasecommunications/api/v2/azure/567934). Retirement date 22 February 2027; closing-down begins 14 September 2026; Microsoft names no drop-in successor and directs customers to identify their own replacement approach. No detect fingerprint: ADE is provisioned through the Azure portal/CLI and ARM/Bicep, with no dependency-manifest string specific enough to fingerprint without false-firing on unrelated Microsoft.DevCenter resources (SOURCING step 6).
Put this countdown in your README
Building on Microsoft? 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-deployment-environments-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.