Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
A Windows 365 Cloud PC reprovision wipes the user’s current Cloud PC and automatically deploys a new one using the current provisioning policy. The user is signed off, and all existing data, apps, and customizations are deleted. When the process finishes, the user receives a new Cloud PC, often with a new device name.
Reprovisioning is generally performed deliberately by administrators. The primary reasons for initiating a reprovision action include: resolving significant issues that can't be fixed through less disruptive means, such as if a Cloud PC is malfunctioning, corrupted, or if a previous provisioning attempt failed. Additionally, reprovisioning is necessary when major changes must be applied—such as switching to a new provisioning policy configuration with a different base image—so the Cloud PC can be rebuilt with the updated configuration.
Reprovisioning is a disruptive action, so administrators should be aware of its impact. Before proceeding, it's common practice for administrators to notify the user and ensure that any critical data is backed up to prevent permanent loss. During the reprovisioning process, the Cloud PC will be unavailable to the user. Due to these significant implications, organizations often reserve reprovisioning for special circumstances or as a last resort.
To Reprovision a Cloud PC, it must have a status of Failed or Provisioned in the Windows 365 provisioning node.
For information on when to use the Reprovision action, see Reprovisioning.
For Windows 365 Flex Cloud PCs in shared mode, you can bulk reprovision all the Cloud PCs in a provisioning policy. Admins can also select the percentage of Cloud PCs that are available for users to connect without being affected by the reprovisioning process.
Reprovision a Cloud PC
- Sign in to the Microsoft Intune admin center, select Devices > All Devices > choose a Cloud PC device > Reprovision.
- In the Reprovision box, select Yes. The reprovision process will begin.
- After the new Cloud PC is created, Windows 365 sends access information to the new user.
The table below outlines various Cloud PC management actions, indicating whether each causes a reprovision action and the key impact on user data and availability:
| Action | Triggers Reprovision? | Impact on Data & Availability |
|---|---|---|
| Admin Reprovision | Yes - Deletes entire Cloud PC and builds a new one. | All user data, apps, settings erased; Cloud PC inaccessible during rebuild. New device is provisioned per current policy. |
| End User Reset | Yes – Reinstalls OS; deletes data & settings (except for Cloud Apps and Windows 365 Flex in shared mode). | All personal files, apps, settings wiped; Cloud PC down during reset (~30+ min). User receives fresh Windows on same Cloud PC. |
| Bulk Reprovision (Windows 365 Flex in shared mode) | Yes – Deletes multiple Cloud PCs and reprovisions them. | All data on targeted Cloud PCs is wiped. Admins can schedule and stagger reprovision so some Cloud PCs remain usable. Account for downtime for each reprovisioned device. |
| Moving Cloud PC (Region/Network) | No – existing Cloud PC moved intact. | No data loss (same Cloud PC persists), but the device is offline during the move. Previous restore points in old region are cleared; new restore points begin in new region. |
| Resizing (License Upgrade/Downgrade) | No – Resize modifies resources on the existing Cloud PC. | No data or app loss – user/disk data kept intact. User disconnected briefly for hardware update. Currently not supported for GPU Cloud PCs. |
| Provisioning Policy Edits | No – Changing policy settings doesn’t auto-reprovision. | No immediate effect on existing Cloud PCs. Changes to the network, image, region, or single sign-on (SSO) affect only new or reprovisioned Cloud PCs. Reprovisioning is required to update existing Cloud PCs with the new network or image. For region or SSO changes, admins must apply the current configuration. |
| Point-in-Time Restore | No – Restores state to the same Cloud PC. | No new Cloud PC – resets current Cloud PC’s state to previous snapshot. Data/app changes made after the restore point are lost, but earlier data is retained. Cloud PC down briefly during restore. |
| Restart / Shut Down | No – Standard reboot/power off. | No data loss – Cloud PC simply reboots. Minimal downtime (similar to a normal PC restart). |
| Rename / Change Settings | No – Metadata changes only. | No impact on OS or user data. Cloud PC remains online (except user must re-login if their account type is changed). |
In summary, only deliberate “wipe and rebuild” actions – like Reprovision or Reset, cause a Cloud PC to be completely reprovisioned. Other management tasks (moving, resizing, restarting, restoring, etc.) do not require reprovisioning and preserve the user’s Cloud PC environment. Careful use of these tools, combined with user education and robust backup practices, will help prevent unwanted data loss and downtime for Windows 365 Cloud PC users and admins.
Next steps
For more information, see Provisioning.