3.1.5. Windows 365 Cloud PCs
💡 First Principle: A Cloud PC moves Windows from the desk into a Microsoft datacenter, so provisioning becomes a policy decision instead of a hardware one. You describe what each Cloud PC should be — license type, how it joins, which network it uses, which image it starts from — and Windows 365 builds one for every user who matches. Change the description and only new Cloud PCs see it, because the settings are applied at build time.
License types. Windows 365 Frontline was renamed Windows 365 Flex in the week of May 4, 2026; licensing and capabilities didn't change, so older questions may still say "Frontline". Flex comes in two modes:
| Windows 365 Enterprise | Windows 365 Flex — Dedicated | Windows 365 Flex — Shared | |
|---|---|---|---|
| What one license gives | A Cloud PC for the licensed user (users without a license aren't provisioned) | Up to 3 Cloud PCs used nonconcurrently, each for a single user, with 1 concurrent session | 1 Cloud PC shared nonconcurrently by a group |
| Deletes user data at sign-out | No | No | Yes, unless User Experience Sync is on |
| Removing a user or group | — | Removed user's Cloud PC enters a grace period | Removing the group deprovisions its Cloud PCs immediately, with no grace period |
| Power behavior | — | Powers off after sign-off (stays on 2 hours); intelligent prestart about 30 minutes before usual connect time | — |
| Windows Autopatch in provisioning policy | Available | Available | Not available |
| User settings policies | Apply | Apply | Don't apply |
| App-only experience (Cloud Apps) | No | No | Yes |
Worked example: a call center has 30 agents across three non-overlapping shifts of 10. With Flex Dedicated, 10 licenses give up to 10 × 3 = 30 personal Cloud PCs, of which 10 can be in use at once — exactly one shift.
Windows 365 Reserve gives a user up to 10 days of Cloud PC access a year for device loss or outages, and Windows 365 Business (capped at 300 users) has no provisioning policies. Windows 365 Enterprise requires each user to be licensed for Windows Enterprise, Microsoft Intune and Microsoft Entra ID P1.
Provisioning policies (Devices > Provision Cloud PCs > Provisioning policies) carry the build instructions:
- License type: Enterprise, Windows 365 Flex (Dedicated or Shared) or Reserve.
- Join type and network: Microsoft Entra join can use a Microsoft-hosted network or an Azure network connection. Hybrid Microsoft Entra join always requires an Azure network connection.
- Image and configuration: a gallery or custom image, language and region, and optionally a name template.
- Additional services: Windows Autopatch, Autopilot device preparation and, for Flex Shared, User Experience Sync.
- Assignments: Entra user security groups or Microsoft 365 Groups; nested groups aren't supported.
The Cloud PC name template is 5–15 characters with a prefix of at most 10, and %RAND:Y% is required with Y of at least 5; %USERNAME:X% is optional on Enterprise and Flex Dedicated. CPC-%USERNAME:4%-%RAND:5% produces 4 + 4 + 1 + 5 = 14 characters, which fits.
Automatic mode connects 3.1.1 to Windows 365. Attaching a device preparation policy installs device-targeted apps (up to 25) and scripts (up to 10) before the user signs in, while the Cloud PC shows the status Preparing. It reached general availability on May 11, 2026 for Enterprise, Flex Dedicated, Flex Shared and Cloud Apps. If preparation times out, provisioning continues; whether users can connect depends on Prevent users from connecting to Cloud PC upon installation failure or time-out — checked marks the Cloud PC Failed, unchecked marks it Provisioned with warnings.
Azure network connections (ANCs) connect Cloud PCs to your own virtual network, as Entra join or hybrid Entra join types. A new ANC can't be assigned until its first health check succeeds, and from April 2026 a blocked required endpoint is an Error that blocks new provisioning. ANC settings apply only at provisioning, so changing one doesn't touch existing Cloud PCs — you reprovision, which is destructive.
Images. A custom image must be a Windows 10 or 11 Enterprise, Generation 2, generalized, single-session image with no recovery partition that has never been joined or enrolled, uploaded from a managed image or an Azure Compute Gallery. A tenant can hold 20. Existing Cloud PCs pick up a new image only when reprovisioned.
User settings (Devices > Cloud PC Settings > User settings) control local admin rights, user-initiated reset and restore points. Short-term restore points can be taken every 4, 6, 12, 16 or 24 hours with 10 kept — at 12 hours that covers the last five days. If a user gets several user-settings policies, the most recently created one wins. Intune adds the Cloud PC Administrator and Cloud PC Reader roles alongside the Entra Windows 365 Administrator role.
⚠️ Exam Trap: A provisioning policy that uses hybrid Microsoft Entra join can't use the Microsoft-hosted network. Hybrid join always needs an Azure network connection with line of sight to a domain controller, so "use the Microsoft-hosted network" is wrong for any scenario that needs on-premises domain membership.
Reflection Question: You edit an Azure network connection to point at a new subnet, but existing Cloud PCs still use the old one. Why, what must you do to move them, and what does that action cost the users?