Clarification required – Microsoft Dev Box retirement impact on Managed DevOps Pools

Question

Clarification required – Microsoft Dev Box retirement impact on Managed DevOps Pools

Erika Prieto 0

Hello,

We currently use Azure Managed DevOps Pools integrated with Azure DevOps to execute CI/CD pipelines that deploy resources to Azure PaaS services through private network connectivity.

Our Managed DevOps Pool is associated with a Dev Center Project and a Dev Center resource.

Following the announcement of Microsoft Dev Box retirement on September 18, 2028, we would like to clarify the following:

Will existing Managed DevOps Pools remain fully operational after Microsoft Dev Box retirement?

Will Dev Center and Dev Center Project resources continue to be supported for Managed DevOps Pools beyond September 2028?

Does Microsoft plan to remove the Dev Center dependency from Managed DevOps Pools?

Will any migration, resource reconfiguration, or customer action be required?

Is there an official roadmap or migration guidance specifically addressing this dependency?

Our main concern is ensuring uninterrupted Azure DevOps pipeline execution and private connectivity to Azure PaaS resources.

Thank you for your clarification.

Best regards,

Rakesh Mishra 11,435 Reputation points Microsoft External Staff Moderator

2026-10-29T15:10:39.74+00:00

Hi @Erika Prieto , thank you for reaching out to Microsoft Q&A portal. I'm looking into this internally and will get back to you with an update.
Suraj Guptha 0 Reputation points Microsoft Employee

2026-10-29T16:23:14.01+00:00

I’m the Product Owner for the Managed DevOps Pools service, and I want to clarify that we** have no plans to deprecate Managed DevOps **Pools. In fact, we continue to actively invest in the service, with new features released as recently as this month.

We have already removed the requirement to specify DevCenter and DevCenter Project, and we are also working on removing these fields from the UI.

I also plan to publish a blog post to explicitly clarify any confusion around its future.
Erika Prieto 0 Reputation points

2026-10-29T16:35:38.6466667+00:00

Okay, thanks for the confirmation @Suraj Guptha . So, will the current Managed DevOps Pools eventually need to be reconfigured to remove the relationships/dependencies with DevCenter and DevCenter Project?.

And, based on what you're saying, this relationship with those resources will no longer be necessary for new pools that are created, correct?. I'll test it in a lab first to validate it.

Thanks!
Suraj Guptha 0 Reputation points Microsoft Employee

2026-10-29T16:59:59.74+00:00

Our goal is to maintain backward compatibility for existing users who are already passing these two fields. We will continue to accept them to avoid breaking existing integrations. However, for new pools, the latest version will no longer require these fields during pool creation.

2 answers

Your answer

Rakesh Mishra 11,435 Reputation points Microsoft External Staff Moderator

2026-10-29T15:10:39.74+00:00

Hi @Erika Prieto , thank you for reaching out to Microsoft Q&A portal. I'm looking into this internally and will get back to you with an update.
Suraj Guptha 0 Reputation points Microsoft Employee

2026-10-29T16:23:14.01+00:00

I’m the Product Owner for the Managed DevOps Pools service, and I want to clarify that we** have no plans to deprecate Managed DevOps **Pools. In fact, we continue to actively invest in the service, with new features released as recently as this month.

We have already removed the requirement to specify DevCenter and DevCenter Project, and we are also working on removing these fields from the UI.

I also plan to publish a blog post to explicitly clarify any confusion around its future.
Erika Prieto 0 Reputation points

2026-10-29T16:35:38.6466667+00:00

Okay, thanks for the confirmation @Suraj Guptha . So, will the current Managed DevOps Pools eventually need to be reconfigured to remove the relationships/dependencies with DevCenter and DevCenter Project?.

And, based on what you're saying, this relationship with those resources will no longer be necessary for new pools that are created, correct?. I'll test it in a lab first to validate it.

Thanks!
Suraj Guptha 0 Reputation points Microsoft Employee

2026-10-29T16:59:59.74+00:00

Our goal is to maintain backward compatibility for existing users who are already passing these two fields. We will continue to accept them to avoid breaking existing integrations. However, for new pools, the latest version will no longer require these fields during pool creation.

Answer 1

What I need to clarify are precisely the points mentioned that are not documented:

whether existing Managed DevOps Pools will remain fully operational after 18 September 2028 if they depend on Dev Center or Dev Center Project resources
whether Dev Center and Dev Center Project resources will continue to be supported for Managed DevOps Pools beyond that date
whether Microsoft will remove the Dev Center dependency from Managed DevOps Pools
whether any migration, reconfiguration, or customer action will be required for this dependency
whether there is official migration guidance specifically for Managed DevOps Pools and Dev Box retirement

Answer 2

The available documentation does not state that Microsoft Dev Box retirement will retire or disable Managed DevOps Pools.

Supported facts from the published guidance:

Microsoft Dev Box retires at 17:00 UTC on 18 September 2028.
Existing Microsoft Dev Box deployments remain supported during the transition period.
Microsoft recommends planning a transition away from Dev Box and avoiding new long-lived dependencies on the retiring service.
Managed DevOps Pools is documented as a separate Azure DevOps service that provides managed compute resources for CI/CD workloads.
Managed DevOps Pools is supported with Azure DevOps Services and Azure public cloud.
The available roadmap content for Managed DevOps Pools includes feature updates such as project-level pool creation permissions and public static IP support, but it does not provide any statement about Dev Box retirement impact, Dev Center dependency removal, or a required migration.

Based on the available documentation, these specific points are not documented:

whether existing Managed DevOps Pools will remain fully operational after 18 September 2028 if they depend on Dev Center or Dev Center Project resources
whether Dev Center and Dev Center Project resources will continue to be supported for Managed DevOps Pools beyond that date
whether Microsoft will remove the Dev Center dependency from Managed DevOps Pools
whether any migration, reconfiguration, or customer action will be required for this dependency
whether there is official migration guidance specifically for Managed DevOps Pools and Dev Box retirement