Skip to content
PreviewCommunity+Infrastructure

Windows 365 Cloud PCs

Manage Cloud PCs and their provisioning policies next to your host pools.

Atlas AVD manages Windows 365 alongside Azure Virtual Desktop. See every Cloud PC with its user, status, connectivity, policy and service plan, then restart, reprovision or resize it from the same console. Create provisioning policies with the image, region, join type and naming template you want, assign them to Entra groups, and check who in those groups still needs a Windows 365 license.

Preview. Windows 365 Cloud PCs is available in Atlas AVD today and is marked Preview in the console while it is finished. An administrator can switch preview features off for a tenant.

Atlas AVD screenshot. All names, metrics and values are demo data.

The problem Windows 365 Cloud PCs solves

Plenty of organizations that run Azure Virtual Desktop also have Windows 365 Cloud PCs: a dedicated desktop for a developer, a shared pool for shift workers, a few staff who wanted a PC of their own. Those Cloud PCs live in the Intune admin center, with their own provisioning policies, licensing and habits, so the team looking after the host pools works in two consoles.

The most common Windows 365 ticket is also the hardest to diagnose: a user was added to the right group and no Cloud PC ever appeared. Windows 365 provisions a Cloud PC only when the user is in a group a provisioning policy targets and also holds a Windows 365 license. Miss the license and nothing happens, with no error anywhere.

Key capabilities

Every Cloud PC with its user, status, connectivity, provisioning policy and service plan, with search
Cloud PC detail: image, region, OS version, disk encryption, last sign-in result and failed connectivity checks
Restart, reprovision or resize a Cloud PC, or end its grace period
Create, edit and delete provisioning policies: image, region, Entra or hybrid join, naming template and single sign-on
Assign provisioning policies to Entra groups
License readiness: group members who do not yet have a Windows 365 license

How Windows 365 Cloud PCs works

  1. 1Connect your tenant through Microsoft Graph
  2. 2Create a provisioning policy and assign it to Entra groups
  3. 3Licensed members of those groups receive Cloud PCs
  4. 4Manage each Cloud PC from the inventory

What the Cloud PC pages show

Windows 365 sits in the sidebar under Workspace with two pages: Cloud PCs and Provisioning Policies. The Cloud PCs page reads the tenant's Cloud PCs live from Microsoft Graph and lists each one with its Assigned User, Service Plan, Provisioning Policy, Status and Connectivity. The Total Cloud PCs, Provisioned, Available and Needs Attention cards double as filters. Needs Attention gathers Cloud PCs that failed, are in their grace period, provisioned with warnings, or have a connection that is unavailable or showing a warning.

Click a Cloud PC for its detail page: service plan and SKU family, operating system, region, provisioning type, image, disk encryption, last sign-in result, managed device name and Microsoft Entra device ID. The Connection Health card lists any failed health checks, and a Cloud PC in its grace period shows the date it will be deprovisioned.

The actions menu offers Restart, Reprovision, Resize and, only during the grace period, End Grace Period. Reprovision rebuilds the Cloud PC from its policy and erases everything stored on it, so it asks first. Resize lists the tenant's other sizes with how many free licenses each has and disables any size with none, because a Cloud PC's size comes from the license its user holds. Windows 365 carries out each action in the background, so the new status shows on a later refresh.

Provisioning policies, groups and licenses

On Provisioning Policies, New Policy asks for the Policy Name, the image ID and whether it is a gallery or custom image, the Provisioning Type (Dedicated or Shared, fixed once the policy exists), the Join Type (Microsoft Entra joined or Hybrid Microsoft Entra joined), an Azure network connection or a region, a Cloud PC Naming Template and Single Sign-On. Atlas catches the combinations Windows 365 would reject before it sends them: a hybrid join needs an Azure network connection, and an Entra join needs a region or a network connection, not both.

Assign Groups chooses the Microsoft Entra groups that receive Cloud PCs from a policy. Windows 365 has no per-Cloud-PC assignment, so Assign Users & Groups on a Cloud PC opens its policy's groups and says the change affects every Cloud PC that policy provisions. Saving with no groups warns first, because unassigning a policy starts the seven-day grace period on every Cloud PC it provisioned.

The same dialog shows License Readiness: for each assigned group, how many members it has and which of them hold no Windows 365 license, with disabled accounts marked. Those members will not receive a Cloud PC, and this is where you find out before they call. Every policy change and Cloud PC action is written to the audit log.

How to set up Windows 365 Cloud PCs

  1. 1Make sure the Atlas app registration has admin consent for the CloudPC.ReadWrite.All Microsoft Graph permission.
  2. 2Open Windows 365 → Cloud PCs in the Workspace section of the sidebar. If it is missing, switch Windows 365 on under Settings → Preview Features.
  3. 3Go to Provisioning Policies, click New Policy and set the image, provisioning type, join type, region or network connection and naming template.
  4. 4Choose Assign Groups on the policy, add the Microsoft Entra groups and check License Readiness before you save.
  5. 5Back on Cloud PCs, use Needs Attention to catch any that failed to provision.

Windows 365 Cloud PCs: frequently asked questions

Why did a user in the assigned group not get a Cloud PC?

Almost always because they hold no Windows 365 license. Group membership alone grants nothing. Open Assign Groups on the policy and License Readiness lists, group by group, the members who have no license and will not receive a Cloud PC.

Does Atlas keep a copy of my Cloud PCs?

No. The Cloud PC and policy lists are read from Microsoft Graph when you open them, with a cache of a minute or two at most, and every action goes straight to Windows 365. Nothing about your Cloud PCs is stored in the Atlas database.

Can I resize a Cloud PC to any size?

Only to a size the tenant has a free Windows 365 license for, because the license sets the vCPU, RAM and storage. The Resize dialog shows free licenses per size and disables sizes with none. The Cloud PC restarts during the resize.

Who can manage Cloud PCs in Atlas?

Administrators and operators can create and assign policies and restart, reprovision or resize Cloud PCs. Security administrators and auditors see the same pages read-only. The feature has no plan gate, so it works on every plan, including Community.

Does Windows 365 management work in GCC High?

Not yet. Atlas supports it for commercial and GCC tenants. Its Cloud PC actions are not yet validated in GCC High, so there the pages say so and point you to the Intune admin center.

Why is Windows 365 missing from my sidebar?

It is a Preview feature that can be switched off for a tenant under Settings → Preview Features. It is also hidden for roles without Cloud PC access, and on deployments set up to manage Azure Virtual Desktop only, without Microsoft 365.

What Microsoft Graph permissions does it need?

CloudPC.ReadWrite.All for Cloud PCs and policies. Group.Read.All shows group names instead of object IDs, and Organization.Read.All lets Atlas count free licenses. Without the last two, the pages still work and say what is missing.

Available on

Community plan and above

Windows 365 Cloud PCs is included in every Community subscription.