As of November 5, 2026, Microsoft’s Windows 365 update page lists two Cloud PC changes: optional auto-deprovisioning for Windows 365 Reserve has entered public preview, and support for Azure AD joined Cloud PCs is now generally available.
For Windows 365 administrators, endpoint architects, and IT leaders, the signal is clear: Reserve capacity now has an optional reclamation control, while joined Cloud PC support has moved beyond preview.
1. Reserve Cloud PC Auto-Deprovisioning Enters Preview
What changed: Microsoft says administrators can optionally configure Windows 365 Reserve to deprovision Cloud PCs that have been provisioned but not actively connected to. The administrator defines the threshold.
The setting is available in public preview and is disabled by default. Administrators control it through the Cloud PC configuration settings for Windows 365 in Microsoft Intune, where it can be scoped to selected Microsoft Entra ID user groups and updated at any time.
Microsoft positions the feature as a way to maximize the value of the 10-day entitlement associated with a Reserve Cloud PC. Any remaining access days are preserved after deprovisioning, but the Cloud PC must be reprovisioned before it can be used again.
Why this matters: This is not a transparent session timeout. It is a lifecycle action that introduces a reprovisioning step in exchange for preserving unused Reserve access days.
The configuration gives IT direct control over that tradeoff. A threshold that is too aggressive could create unnecessary reprovisioning work, while leaving the feature disabled may reduce the value your organization receives from the Reserve entitlement.
Admin action: Identify the Microsoft Entra ID groups that could benefit from the setting, then test the complete deprovisioning and reprovisioning workflow before assigning it broadly. Document who can initiate reprovisioning and how affected users should request renewed access.
2. Azure AD Joined Cloud PC Support Reaches GA
What changed: Microsoft now lists support for Azure AD joined Cloud PCs as generally available. The update uses the former Azure AD name for the identity service now called Microsoft Entra ID.
This is a production lifecycle milestone, not an instruction to change every Cloud PC deployment.
Why this matters: General availability gives administrators a clearer basis for evaluating the join model in production planning. It does not eliminate the need to validate your tenant’s identity, provisioning, security, application-access, and recovery requirements.
Admin action: Review whether existing Cloud PC architecture decisions were influenced by the earlier availability status. If so, reassess those decisions against your current operational requirements rather than treating general availability as an automatic migration trigger.
What Cloud PC Admins Should Do Next
Inventory current Reserve usage. Identify the users and Microsoft Entra ID groups associated with Reserve Cloud PC access.
Evaluate the preview with limited scope. Select a controlled group, configure an appropriate threshold, and observe the full auto-deprovisioning workflow.
Document reprovisioning ownership. Define who restores a deprovisioned Reserve Cloud PC and how users request that action.
Validate the GA join scenario. Compare Azure AD joined Cloud PC support with your current identity and provisioning design before making configuration changes.
Until next time, happy administrating!