Microsoft to Retire Azure Developer Tools by 2028
Engineering teams must manually migrate workflows before these services shut down in 2027 and 2028.
Updated on Oct. 30, 2026 in Remote Work
Live Poll
Do you trust that major cloud providers will keep their long-term promises to developer customers?
Microsoft will retire its Azure Deployment Environments service on February 22, 2027, and Microsoft Dev Box on September 18, 2028. Organizations relying on these platforms for development workflows must now begin planning manual transitions for their cloud-based environments.
Why it matters
The retirement of these tools forces engineering teams to overhaul their infrastructure management strategies and manually migrate developer environments. Microsoft is directing users toward Windows 365, which requires new licensing and setup workflows compared to the outgoing services.
Microsoft is ending support for two development services, with Azure Deployment Environments set to close in 16 months and Microsoft Dev Box to follow in 2028. Teams are currently tasked with migrating internal workflows previously used by 10,000 developers.
The players
Microsoft
A global technology company that provides enterprise software, cloud infrastructure, and developer productivity tools.
Windows 365
A cloud-based service that provides persistent virtual desktop infrastructure for enterprise users.
The details
Teams must conduct a complete inventory of existing environment definitions, catalogs, and role assignments before the shutdown dates. Because no automated migration tool is available, administrators are required to manually provision new Cloud PCs, recreate security policies, and deploy applications in target environments. For Microsoft Dev Box users, this shift requires adopting Windows 365, which is licensed independently through Intune.
Timeline
September 14, 2026: Microsoft Dev Box closing-down period begins.
February 22, 2027: Azure Deployment Environments service ends and write operations are blocked.
September 18, 2028: Microsoft Dev Box service ends and workloads are deleted.
Market Landscape
This move signals a shift in Microsoft's cloud developer tool strategy as it consolidates service offerings around Windows 365. It follows the 2023 general availability launches of these services, representing a narrowing of the product roadmap for enterprise cloud environments.
Engineering leads should immediately audit their Azure resource dependencies to avoid service disruptions before the 2027 deadline. Teams should also evaluate the licensing costs associated with moving to Windows 365 via Intune for their development workforce.
The takeaway
The end of these services necessitates a transition strategy that accounts for manual data migration and new licensing requirements. Operators should prioritize documenting their current catalog configurations now to facilitate a cleaner transition to replacement infrastructure before service access is blocked.
Further reading
For more on managing distributed development teams, visit Remote Work.
Source note: This article includes information reported by InfoQ.
Live Poll
Do you trust that major cloud providers will keep their long-term promises to developer customers?
