Microsoft Dev Box retirement and Azure Managed DevOps Pools dependencies

Andre-3987 0 Reputation points
2026-10-15T14:21:13.5433333+00:00

Microsoft has announced that Microsoft Dev Box will be retired on September 18, 2028.
We use Azure Managed DevOps Pools for our Azure DevOps pipelines. Managed DevOps Pools requires a Microsoft Dev Center and Dev Center Project, but we do not use Microsoft Dev Box to provision developer workstations.

My questions are:

  1. Will the retirement of Microsoft Dev Box affect the availability, support, or lifecycle of the Microsoft.DevCenter resource provider, Dev Centers, or Dev Center Projects used exclusively by Azure Managed DevOps Pools?
  2. Will Azure Managed DevOps Pools continue to require a Dev Center and Dev Center Project after September 18, 2028?
  3. Is any migration, configuration change, or alternative resource required for existing Managed DevOps Pools that use Dev Centers solely as a prerequisite?

Thanks

Azure DevOps

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rukshan edirisinghe 2,445 Reputation points
    2026-10-19T03:10:44.99+00:00

    Hi @Andre-3987

    Fair question. The two products share the same resource provider, so it's natural to worry. Here's what the official sources say today, and where they're silent.

    • The Dev Box retirement notice (September 18, 2028) is about the Dev Box service: dev boxes, their pools, images and developer workflows, with Windows 365 as the replacement. It doesn't mention Managed DevOps Pools at all, and it doesn't say the Microsoft.DevCenter provider or dev centers themselves are retiring.
    • The current Managed DevOps Pools prerequisites page still says a pool requires a dev center and dev center project, and lists Microsoft.DevCenter as the provider for them. There's no retirement note on that page.

    So, based on what's published, there's no migration or configuration change you need to make for Managed DevOps Pools right now. What I'd do to stay safe:

    1. Keep the dev center and project that your pools use as they are. Don't clean them up as part of any Dev Box decommissioning.
    2. Watch Azure Updates and the retirement notices in Service Health for anything that names Managed DevOps Pools. Microsoft announces breaking changes there, usually well ahead of time.
    3. If you need a written commitment for planning or audit, ask through a support case or your Microsoft account team. That's the only route to a formal answer beyond the public docs.

    Are your dev center and project used only by Managed DevOps Pools, or do any Dev Box pools live in them too?

    If this answered your question, please consider accepting it as the answer. If Microsoft publishes anything new about this, let me know and I'll be happy to keep helping.

    Reference:

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.