Microsoft’s Windows 365 update for the week of November 2, 2026 lists two Cloud PC management changes: new policy creation is being disabled in the public-preview legacy user settings experience, while the local administrator control for Cloud PC configurations is now generally available through Microsoft Intune.

For Windows 365 administrators, endpoint architects, and IT leaders, the signal is clear: legacy policy migration now needs an inventory, while local administrator access needs a deliberate privilege decision.

1. Legacy User Policy Creation Is Being Disabled

What changed: Microsoft says the User settings tab in Cloud PC Settings is being renamed User settings (legacy). As part of that transition, Microsoft is disabling the ability to create new policies through the public-preview legacy experience.

Existing policies can still be edited for a limited time and will continue to apply until their migration is complete, according to the Windows 365 update. Microsoft does not specify a final editing cutoff in the November entry.

This is not an immediate policy shutdown. It is the start of a migration window with an unspecified end date.

Why this matters: Your tenant can no longer treat User settings (legacy) as the destination for new policy work. Existing policies still provide continuity, but their temporary editability creates an operational deadline even though Microsoft has not attached a calendar date to it.

The practical risk is configuration drift. A legacy policy can remain active while your team begins managing equivalent settings elsewhere, so the migration needs documented ownership and a setting-by-setting record.

Admin action: Inventory every existing User settings (legacy) policy and record the settings it controls. Microsoft advises administrators to recreate each setting in the corresponding experience, so your migration plan should track the legacy setting, its replacement location, its intended users, and completion status.

Do not wait for a final editing cutoff before starting. The limited-time language is the deadline signal.

2. Local Administrator Control Reaches General Availability

What changed: Microsoft says the Enable local admin setting in Cloud PC configurations is now generally available in Intune. The setting allows IT administrators to grant users local administrator permissions on their Cloud PCs.

This is a production privilege control, not a preview-only configuration.

Why this matters: General availability gives your team a supported configuration path for users who require local administrator access. It also creates a governance obligation because the setting changes the user’s privilege level on the Cloud PC.

Availability should not become automatic assignment. The control addresses how access is granted; your organization must still decide who needs it.

Admin action: Evaluate Enable local admin against documented support, application, and operational requirements. Assign the Cloud PC configuration only where local administrator permissions are justified, and include those assignments in your regular access review process.

What Cloud PC Admins Should Do Next

  1. Act now: Inventory all User settings (legacy) policies, identify their settings, and assign an owner for each migration.

  2. Plan the transition: Recreate each legacy setting in Microsoft’s corresponding experience and track completion without assuming that legacy editing will remain available.

  3. Evaluate privileges: Review where Enable local admin is operationally necessary before assigning the Cloud PC configuration.

  4. Monitor the rollout: Watch for Microsoft to provide additional timing or enforcement details for the end of legacy policy editing.