Microsoft Sets Azure Deployment Environments to Retire Feb. 22, 2027 and Dev Box Sept. 18, 2028; ADE Has No Single One-to-One Replacement
Microsoft's retirement guides give February 22, 2027 for Azure Deployment Environments and September 18, 2028 for Dev Box; InfoQ notes the guides do not explain the withdrawals.
Overview
Microsoft has published retirement guides for two Azure developer-environment services. According to the Azure Deployment Environments retirement guide, “Azure Deployment Environments retires on February 22, 2027.” The Microsoft Dev Box retirement guide says “Microsoft Dev Box will retire at 17:00 UTC on 18 September 2028.” InfoQ, in an article by Steef-Jan Wiggers dated October 30, 2026, reported on both notices.
What the guides say
Azure Deployment Environments (ADE)
The ADE guide states that “ADE doesn’t have a single one-to-one replacement for every workload.” It lists three Microsoft approaches: “direct infrastructure-as-code deployment with Azure Resource Manager templates or Bicep,” reusable Azure verified modules, and Azure DevOps and GitHub workflows. For the last option, the guide says to rebuild ADE-specific commands, SDK integrations and azd configuration that targets the Dev Center platform. On partner tools, the guide says: “None of the third-party solutions we identified directly support a Bicep or ARM lifecycle.”
On the retirement date, the guide says “ADE create, deploy, redeploy, and other write operations are expected to be blocked. Inventory, read, log, and delete operations are planned to remain available for a time-bound cleanup period.” InfoQ notes that “How long that period runs is not stated.”
The guide also tells customers that deleting an ADE environment does not necessarily stop charges: deleting ADE metadata might not delete every Azure resource the environment deployed, so Azure Cost Management data should be reviewed. It adds that ADE environment instances do not have Azure Resource Manager resource IDs, so deployed environments must be inventoried through the developer portal, Azure CLI, ADE data-plane APIs or existing operational telemetry.
Microsoft Dev Box
Per the Dev Box guide, “The closing-down period begins at 16:00 UTC on 14 September 2026.” The guide names Windows 365 as “the recommended path forward for virtualized developer environments,” and its FAQ answers whether Windows 365 is a one-to-one replacement: “No. Windows 365 is the recommended path forward, but architecture, licensing, management, networking, image delivery, and developer self-service can differ. Validate each workload and don’t assume complete feature parity.” It also says “Microsoft Dev Box won’t be available after retirement. Expect deletion of remaining customer workloads.”
The two retirements are linked through shared resources. The ADE guide says “Dev Center will continue to be supported until Microsoft Dev Box retires on September 18, 2028,” and advises against deleting shared dev center resources until it is confirmed they have no remaining Dev Box dependency.
Independent reporting
InfoQ characterized the ADE notice as “a hyperscaler leaving the environment-as-a-service category and telling customers to hand-roll what the product did.” The outlet wrote that self-service from a governed catalog “is the capability going away, and it is the one the retirement guide does not replace,” adding that Bicep, verified modules and pipelines rebuild the provisioning but not the catalog, the role rules or the developer-facing portal. InfoQ also wrote that the service itself was free, with customers paying only for the Azure resources their environments created.
On Dev Box, InfoQ wrote that Windows 365 “is a Microsoft 365 product rather than an Azure service, managed through Intune and licensed separately.” The Dev Box guide itself says Windows 365 provides persistent Cloud PCs that can be managed with Microsoft Intune. InfoQ also reported that Azure Virtual Desktop “is not named anywhere in the retirement guide.”
What is not stated
- InfoQ wrote that “Neither guide explains the withdrawal.” It added that the Dev Box notice says investment is going to Windows 365, while for Deployment Environments there is no equivalent statement.
- The length of the ADE read-and-delete cleanup period is not given in the guide text cited above.