|
1 | 1 | --- |
2 | | -title: Microsoft Dev Box capabilities are coming to Windows 365 |
| 2 | +title: Microsoft Dev Box and Windows 365 Update |
3 | 3 | description: Discover how Microsoft Dev Box capabilities are transitioning to Windows 365, offering unified solutions for developers and IT admins starting in November 2025. |
4 | 4 | #customer intent: As an IT admin, I want to understand the changes to Microsoft Dev Box so that I can plan for the transition to Windows 365. |
5 | 5 | author: RoseHJM |
6 | 6 | ms.author: rosemalcolm |
7 | 7 | ms.reviewer: rosemalcolm |
8 | | -ms.date: 11/05/2025 |
| 8 | +ms.date: 03/10/2026 |
9 | 9 | ms.topic: concept-article |
10 | 10 | ms.service: dev-box |
11 | 11 | --- |
12 | 12 |
|
13 | | -# Microsoft Dev Box capabilities are coming to Windows 365 |
| 13 | +# Microsoft Dev Box and Windows 365 update |
| 14 | +Customers have shared the need for development environments that offer: |
| 15 | +- A predictable business model that scales with enterprise adoption |
| 16 | +- Support for smaller and more cost-effective VM sizes (2 vCPU, 4 vCPU) |
| 17 | +- Access to a broader range of options, including GPU-backed VMs |
| 18 | +- Greater flexibility to support evolving development scenarios |
14 | 19 |
|
15 | | -Microsoft Dev Box is evolving and transitioning into a unified business model under Windows 365. This transition reflects feedback from customers who asked for: |
| 20 | +These requests underscore a clear demand for flexible, scalable, and cost-effective development environments in the cloud. |
16 | 21 |
|
17 | | -- A predictable business model that scales with enterprise adoption. |
18 | | -- Support for smaller SKUs (2 vCPU, 4 vCPU). |
19 | | -- Access to a broader range of options, including GPU-backed SKUs. |
20 | | -- Greater flexibility to support hybrid and ephemeral development scenarios. |
| 22 | +Windows 365 delivers personalized, secure Cloud PCs to meet the needs of organizations of all sizes, supporting a broad range of employee personas and business scenarios. Microsoft Dev Box, built on Windows 365, extended this vision by providing ready-to-code, cloud-powered development environments that enable developers to spin up secure, project-specific workspaces to support productivity. |
21 | 23 |
|
22 | | -Windows 365 delivers personalized, persistent Cloud PCs to meet the needs of organizations of all sizes, supporting a broad range of employee personas and business scenarios. The Microsoft Dev Box service in Azure extends this vision by providing cloud-powered, ready-to-code development environments that enable developers to quickly spin up secure, project-specific workspaces optimized for productivity. |
| 24 | +We're excited to announce that we're planning enhancements to Windows 365 that are intended to further empower organizations to deliver an improved experience for information workers, agent makers, and developers. |
23 | 25 |
|
24 | | -We're excited to announce that we're bringing these developer-specific capabilities to Windows 365, further empowering organizations to deliver the best information worker and developer experiences from a single unified solution. |
| 26 | +Windows 365 is a Cloud PC platform that streams a familiar, secure and personalized Windows experience to any device, anywhere. With GPU-enabled configurations and centralized management, Windows 365 already supports a wide range of developer workflows today. As Windows 365 continues to evolve with additional developer capabilities, developers will benefit from increased productivity and flexibility. IT admins and platform engineers can leverage centralized controls, streamlined provisioning, consistent policy enforcement, and unified visibility across Cloud PCs—from task workers to developers—all in one place. |
25 | 27 |
|
26 | | -Dev Box is built on Windows 365, and by consolidating these capabilities into Windows 365 and unifying the solution, developers will benefit from a consistent, flexible solution and seamless integration with enterprise identity and security. IT admins and platform engineers can use centralized controls, streamlined provisioning, consistent policy enforcement, and unified visibility across Cloud PCs—from task workers to developers—all in one place. |
| 28 | +Effective November 1, 2025, the following changes took effect: |
| 29 | +- The Microsoft Dev Box service stopped accepting new customers. |
| 30 | + - *Net new customers* are defined as those with no prior Dev Box deployment in any form within their Microsoft Entra ID tenant. |
| 31 | + - Customers interested in using Windows 365 as a platform for developers should reach out to their Microsoft account team. |
| 32 | +- There's no immediate change for existing customers. |
| 33 | + - Customers who have run a POC, experimented, or begun configuring Dev Box are considered existing customers, and they can continue using and scaling their current Dev Box deployments. |
| 34 | + - If you plan to start using or scaling Dev Boxes into additional tenants, submit a request through [Azure Support](https://aka.ms/azure-support) to get your new tenants *allowlisted*. |
27 | 35 |
|
28 | | -Effective November 1, 2025, the following changes will take place: |
| 36 | +As new developer capabilities are released in Windows 365, Microsoft will provide resources and guidance. |
29 | 37 |
|
30 | | -- The Microsoft Dev Box service stops accepting net new customers. |
31 | | - - *Net new customers* are defined as those with no prior Dev Box deployment in any form. |
32 | | - - As features are integrated into Windows 365 and become publicly available, customers interested in leveraging existing dev box capabilities should contact their Microsoft account team. |
33 | | -- There's no immediate change to existing customers. |
34 | | - - Customers who have run a POC, experimented, or begun configuring Dev Box are considered existing customers, and they can continue using and scaling their current Dev Box deployments. |
35 | | - - If you plan to start using or scaling Dev Boxes into additional tenants, submit a request through [Azure Support](https://go.microsoft.com/fwlink/p/?linkid=2202692&clcid=0x409) to get your new tenants allowlisted. |
| 38 | +## Frequently Asked Questions (FAQs) |
36 | 39 |
|
37 | | -All core workflows and value props remain intact - including managing development teams through the Dev Center/Project platform in Azure, configuring guardrails, providing self-serve capabilities for developers, and offering ready-to-code machines with imaging and customizations, as well as custom network support. |
| 40 | +### Why is Microsoft making this change? |
| 41 | +Dev Box is built on Windows 365, the Cloud PC platform that streams a familiar, secure, and personalized Windows experience to any device, anywhere. As Windows 365 continues to evolve with additional developer capabilities, developers benefit from increased productivity and flexibility, more SKU options, and enhanced integration with enterprise identity and security. For organizations across industries, Windows 365 provides a single platform to support cloud desktops across information workers, agent makers, and developers. |
38 | 42 |
|
39 | | -As new developer capabilities are released in Windows 365, Microsoft will provide resources and tools to ensure a smooth transition. |
| 43 | +### How do we define net-new customers? |
| 44 | +Net-new customers are those with no prior deployment of Dev Box in any form in their Microsoft Entra ID tenant. Existing customers, or those who have run a POC, experimented, or begun configuring Dev Box, aren't affected and can continue to use their deployments. |
40 | 45 |
|
41 | | -## Frequently Asked Questions (FAQs) |
| 46 | +### I'm an existing customer. Will there be any changes to my core Dev Box experience? |
| 47 | +There are no planned changes to your core Dev Box workflows. Existing customers can continue using Microsoft Dev Box as they do today. You can engage with your Microsoft account team to discuss your needs and how Windows 365 might better support you. |
42 | 48 |
|
43 | | -### Why is Microsoft making this change? |
| 49 | +### What is the transition timeline for existing customers? |
| 50 | +Windows 365 already supports many developer workflows today and will continue adding further developer-relevant capabilities over time. As new capabilities become available in Windows 365, Microsoft will provide more guidance and timelines. |
44 | 51 |
|
45 | | -Dev Box is built on Windows 365, and by transitioning these capabilities into Windows 365 and unifying the solution, developers will benefit from a consistent, flexible solution with additional SKUs to choose from, and seamless integration with enterprise identity and security. By consolidating value propositions, we aim to offer a predictable license-based business model that supports multi-environment and ephemeral scenarios, along with a broader range of SKUs, including 2-core, 4-core, 8-core, and 16-core GPU options. This shift addresses critical feedback from our customers. |
46 | | - |
47 | | -### Which edition of Windows 365 will incorporate Microsoft Dev Box functionalities? |
48 | | - |
49 | | -Dev Box capabilities will be enabled with Windows 365 Frontline. This edition is best suited for developers who need flexible work setups, advanced workstations, and support for multi-environment and hybrid development scenarios, which benefit geographically distributed development teams. Each Windows 365 Frontline license allows the provisioning of up to three Cloud PCs or development workstations, each dedicated to a specific user or workstation. |
50 | | - |
51 | | -### How do we define net new customers? |
52 | | - |
53 | | -Net new customers are those with no prior deployment of Dev Box in any form. Existing customers, or those who have run a POC, experimented, or begun configuring Dev Box, aren't affected and can continue to use and scale their deployments. |
54 | | - |
55 | | -### Will there be any changes to my core Dev Box experience? |
56 | | - |
57 | | -No. All core workflows will remain unchanged, including management of development teams through the Dev Center/Project platform in Azure, configuration of guardrails, access to self-service for developers, provisioning ready-to-code machines with in-built imaging and customizations, and support for custom networks. The existing automation investments will continue to be relevant and are expected to require only minor modifications when you transition. |
58 | | - |
59 | | -### Do I need to take any action before the transition? |
60 | | - |
61 | | -No action is required at this time. You're encouraged to explore Windows 365 and engage with your Microsoft account team to evaluate licensing options. If you're also interested in participating in the upcoming preview of the new developer features in Windows 365, please contact your Microsoft account team. |
62 | | - |
63 | | -### What is the transition timeline for existing customers? |
64 | | - |
65 | | -As new capabilities become available in Windows 365, Microsoft will provide migration guidance and timelines. |
66 | | - |
67 | | -### Will there be additional costs for using developer capabilities in Windows 365? |
68 | | - |
69 | | -No. Customers who plan to use developer capabilities in Windows 365 once they become available will receive them as part of their Windows 365 license with no additional cost expected. |
70 | | - |
71 | | -### How will my data and configurations be handled during migration? |
72 | | - |
73 | | -As new capabilities become available, Microsoft will release migration guidance, including tools and timelines. Stay engaged with your account team for updates. |
74 | | - |
75 | | -### How can I try out new developer features in Windows 365 before they're released? |
76 | | - |
77 | | -Previews will be available as features are integrated into Windows 365. Contact your Microsoft account team to express interest in joining the preview. |
| 52 | +### Will there be additional costs for using developer capabilities in Windows 365? |
| 53 | +No. Customers who plan to use developer capabilities in Windows 365 once they become available will receive them as part of their Windows 365 license. |
78 | 54 |
|
79 | 55 | ## Related content |
80 | 56 | - [Windows 365 integration with Microsoft Dev Box](https://aka.ms/WindowsSeptAnnouncements) |
81 | 57 | - [What is Windows 365?](/windows-365/overview) |
82 | | - |
0 commit comments