# Microsoft Dev Box licensing and pricing: what you pay, what you need, and when Windows 365 is the better fit > Microsoft Dev Box bills Azure compute per hour and storage per month in addition to Windows Enterprise, Intune and Entra ID P1 licenses. What each developer needs, how auto-stop and hibernation shape the invoice, and when Windows 365 Enterprise or Azure Virtual Desktop fits better. Canonical: https://o365hq.com/blog/microsoft-dev-box-licensing-and-pricing-and-when-windows-365-fits-better Provider: IT Partner LLC — US Microsoft partner since 2006. Book: https://o365hq.com/book Published: 2026-11-09 · IT Partner Microsoft Dev Box gives each developer a ready-built Windows 11 workstation in Azure, managed through Intune. Unlike Windows 365, it is not a fixed monthly license: Dev Box is Azure consumption, with a compute meter that runs only while the machine is on and a storage meter that runs all month, and it assumes the developer already holds certain Microsoft 365 licenses. Here is what you need to own first, how the charge is built, and where Windows 365 Enterprise or Azure Virtual Desktop fits better. ## What Microsoft Dev Box is Dev Box is a managed Azure service for developer workstations. A developer signs in to the developer portal, picks a pool and gets a Windows 11 Enterprise virtual machine with the team's tools, repositories and SDKs already installed. The machine is Entra joined or hybrid joined, enrolled in Intune, and subject to the same compliance and Conditional Access policies as a laptop. Dev boxes range from eight virtual CPUs and 32 GB of memory to 32 virtual CPUs and 128 GB, with SSD storage from 256 GB to 2 TB, and each pool is pinned to one image, Microsoft-supplied or custom from an Azure Compute Gallery. A developer can hold more than one dev box, which is what the hourly billing is built for and what makes Dev Box harder to budget than a fixed Cloud PC if nobody turns the controls on. ## The licenses each developer needs before Azure is involved Dev Box does not include the Windows license or the management plane. Microsoft requires that each user is licensed for Windows 11 Enterprise or Windows 10 Enterprise, for Microsoft Intune, and for Microsoft Entra ID P1. Microsoft 365 E3, E5, F3, Business Premium and the A3 and A5 education suites all carry Windows Enterprise rights, Intune and Entra ID P1, so a developer on any of them is ready for Dev Box. The other way is standalone Windows Enterprise E3 or E5, Intune Plan 1 and Entra ID P1, which costs more per user than the suite. The tenant also needs an Azure subscription to hold the dev center, and either the Microsoft-hosted network or an Azure network connection to your own virtual network for access to internal source control. Our article on [Windows 365 Business against Enterprise](/blog/windows-365-business-vs-enterprise-licensing-prerequisites-resizing-and-what-happens-at-expiry) covers the same prerequisites, which Windows 365 Enterprise shares exactly. ## The Azure charge: compute per hour and storage per month The Dev Box charge itself is two Azure meters on your subscription. The compute meter is charged per hour while a dev box is running, at a rate that depends on the size. A stopped or hibernated dev box accrues no compute charge. Microsoft also applies a monthly cap per dev box: once a machine has run enough hours in a month to reach the cap, further hours that month are not charged. The storage meter is charged per month for the disk size in the dev box definition, running or not. An abandoned dev box nobody deleted after a project ended keeps paying it, which is why most governance work is finding and removing idle boxes. Data transfer, image storage and networking land on the same invoice. ## Auto-stop, hibernation and the monthly cap Because the compute meter is hourly, the schedule is the budget. Each pool can carry an auto-stop schedule, a time of day and time zone at which every dev box in the pool shuts down, with a grace-period notification. Hibernation is the more useful control for developers. A hibernated dev box stops the compute meter and restores open editors, terminals and debugger sessions on reconnect. On the images and sizes Microsoft lists as hibernation-capable, the auto-stop schedule can hibernate instead of shut down, and a hibernate-on-disconnect option sleeps a box after a period with no active session. The monthly cap is the backstop for the developer who needs an always-on machine. For everyone else, the gap between the cap and actual hours is where Dev Box earns its keep against a fixed-price Cloud PC. ## Dev center, projects and pools: where the cost decisions live The dev center is the root Azure resource; it holds the dev box definitions (image, compute size, storage size) and the network connections. Projects sit under it and map to teams or applications; a development lead can be delegated a project, and the project caps the number of dev boxes per developer, which stops one person accumulating six machines. Pools sit under projects and fix the definition, the network connection, the auto-stop or hibernation schedule, and whether developers get local administrator rights. A cost management view filtered to one project's tags shows what that team consumed in a month. ## Visual Studio subscriptions and Dev Box Visual Studio Enterprise and Visual Studio Professional standard subscriptions include use rights for Windows 11 Enterprise on Dev Box, so a subscriber does not need a separate Windows Enterprise license to satisfy that part of the requirement. Intune and Entra ID P1 are not part of a Visual Studio subscription and still come from the developer's Microsoft 365 suite. Check the Visual Studio subscription benefits page before planning around this, because the entitlement has changed since Dev Box reached general availability on 11 July 2023. ## Dev Box, Windows 365 Enterprise or Azure Virtual Desktop for developers Windows 365 Enterprise is a fixed monthly license per user for a Cloud PC of a chosen size, always provisioned, managed in Intune, with the same Windows Enterprise, Intune and Entra ID P1 prerequisites as Dev Box. Cloud PCs reach 16 virtual CPUs and 64 GB of memory with 1 TB of storage. It fits a developer who works a full day, every day, on one machine and wants a predictable license line, and it is the answer for the contractor and BYOD case our article on [Windows 365 Cloud PCs for contractors](/blog/windows-365-cloud-pc-for-contractors-and-byod-instead-of-shipping-laptops) covers. Dev Box fits uneven usage: contractors on three days a week, a developer who needs a 32 virtual CPU machine for one week of performance work, or anyone holding several environments at once. Azure Virtual Desktop is the build-it-yourself option: your own session hosts, images and host pools in your Azure subscription, with personal hosts for developers who need administrator rights and persistence. It offers the most control and demands the most administration, so for a development team it only makes sense where you already run AVD or need something neither managed service offers. Our guide to [Azure Virtual Desktop for a small business](/blog/azure-virtual-desktop-for-a-small-business-design-cost-and-licensing) and the [Windows 365 vs AVD comparison tool](/tools/windows-365-vs-avd) compare the fixed-license and consumption models; our [survey of every way to run Windows as a virtual machine](/blog/every-way-to-run-windows-as-a-virtual-machine-licensing-channels-pros-cons-and-cost) places all three. The rule for a 20 to 500 person organization: Windows 365 Enterprise for the steady full-time developer, Dev Box for the variable, multi-environment or contractor developer, and AVD only when a specific requirement rules the other two out. ## Which charges are Microsoft's and which are the customer's The Microsoft 365 suite or standalone Windows Enterprise, Intune and Entra ID P1 licenses, and any Visual Studio subscriptions, are per-user subscriptions bought through IT Partner at Microsoft's list price. Dev Box compute hours, storage months, image storage and data transfer are Azure consumption, metered by Microsoft and billed to your Azure subscription. Designing the dev center, projects, pools, images, network connection, Intune policies and schedules is the implementation work, delivered at a fixed price under [Microsoft Dev Box Implementation](/services/microsoft-dev-box-implementation), or under [Windows 365 Cloud PC Implementation](/services/windows-365-cloud-pc-implementation) where the fixed-license model fits better. Microsoft's license and consumption charges are always yours. ## Frequently asked questions ### Does Dev Box include a Windows license? No. Each user must be licensed for Windows 11 or Windows 10 Enterprise, Intune and Entra ID P1, typically through Microsoft 365 E3, E5, F3 or Business Premium, or through a Visual Studio Enterprise or Professional subscription for the Windows part. ### Am I charged while a dev box is stopped or hibernated? Compute is charged per hour only while the dev box is running. Storage is charged per month regardless of state. ### Is there a limit to how much one dev box can cost in a month? Microsoft applies a monthly cap on compute per dev box; after enough running hours, further hours that month are not charged. ### When is Windows 365 Enterprise a better choice than Dev Box? When the developer works full time on one machine, 16 virtual CPUs and 64 GB is enough, and a fixed monthly license is preferable to a variable Azure meter. ## Sources - Microsoft Learn, "What is Microsoft Dev Box?" (https://learn.microsoft.com/azure/dev-box/overview-what-is-microsoft-dev-box), consulted November 2026. - Microsoft Learn, "Key concepts for Microsoft Dev Box" (https://learn.microsoft.com/azure/dev-box/concept-dev-box-concepts), consulted November 2026. - Microsoft Learn, "Auto-stop schedules" (https://learn.microsoft.com/azure/dev-box/how-to-configure-stop-schedule) and "Hibernation in Microsoft Dev Box" (https://learn.microsoft.com/azure/dev-box/how-to-hibernate-your-dev-box), consulted November 2026. - Microsoft Azure, "Microsoft Dev Box pricing" (https://azure.microsoft.com/pricing/details/dev-box/), consulted November 2026. - Microsoft Learn, "Microsoft Dev Box for Visual Studio subscribers" (https://learn.microsoft.com/visualstudio/subscriptions/vs-dev-box), consulted November 2026. - Microsoft Learn, "Requirements for Windows 365 Enterprise" (https://learn.microsoft.com/windows-365/enterprise/requirements) and "What is Azure Virtual Desktop?" (https://learn.microsoft.com/azure/virtual-desktop/overview), consulted November 2026. ## Key takeaways - Dev Box requires each developer to hold Windows 11 or 10 Enterprise, Intune and Entra ID P1, which Microsoft 365 E3, E5, F3 and Business Premium all include; Dev Box itself adds no license. - The Azure charge is a compute meter per hour while running, with a monthly cap per dev box, plus a storage meter per month that runs whether the box is on or off. - Auto-stop schedules, hibernation and per-developer dev box limits on the project are the controls that keep the compute meter under the cap. - Windows 365 Enterprise fits the steady full-time developer on a fixed license; Dev Box fits variable, multi-environment or contractor usage; Azure Virtual Desktop is for requirements neither managed service meets. --- Send us your developer headcount, the Microsoft 365 plan they hold and whether any of them have Visual Studio subscriptions, and we will tell you which prerequisites you already own and whether Dev Box or Windows 365 Enterprise fits your team.