Windows 365 Legacy User Settings Retirement Gets a Longer Runway

Microsoft delayed the Windows 365 User settings retirement. Here is the new timeline and how to move to Cloud PC configurations.

INTUNE

11/4/20262 min read

worm's-eye view photography of concrete building
worm's-eye view photography of concrete building

If your tenant still relies on Windows 365 User settings policies, Microsoft has just given you more time, but not a reason to ignore the change. The company has pushed back the retirement of the legacy User settings experience in the Intune admin center, and the new timeline (message center item MC1528019) replaces the original plan from MC1418556, which called for these policies to stop applying in January 2027.

Here is what the updated message center post says. Existing User settings policies will remain in place and continue to apply until they are migrated, either by you or by Microsoft. Early November 2026 brings general availability of Enable local admin in Cloud PC configurations. In mid-November the User settings tab is renamed User settings (legacy) and grayed out: you can no longer create new legacy policies, but existing ones stay editable and in-product banners nudge you toward the transition. In early December existing legacy policies become read-only while still applying. Microsoft then plans to auto-migrate remaining eligible policies between April and June 2027, with confirmed dates to follow in a later communication. Community coverage on November 3 reported the rollout starting the week of November 2, so the exact date in your tenant may differ; check the message center for your own timing.

The affected settings cover local admin access, user-initiated Cloud PC reset and restore, restore-point frequency, and disaster recovery. They do not move as one block. According to the message center post, Enable local admin, restore-point frequency, Cross-Region Disaster Recovery and Disaster Recovery Plus map to Cloud PC configurations, while the options for letting users reset their Cloud PCs or initiate the restore service map to Windows App settings. Where policies overlap, the higher-ranked policy wins for each setting, unconfigured values do not take part in conflict resolution, and auto-migrated policies receive the lowest rank. That means anything you build yourself will take precedence over what Microsoft migrates later.

A practical approach is to start with an inventory. Export or document every existing User settings policy, including each configured setting and its assignments, then map each one to its replacement policy type. Recreate the configurations in Cloud PC configurations and Windows App settings as they become available in your tenant, review assignments and ranking, and test the result on a pilot group. For the recovery settings, double-check restore-point frequency and the backup region, and keep the values unchanged so you do not lose existing backups. Once you have validated the new policies, delete the legacy ones to avoid duplicates; any that remain will still be migrated later, but at lower priority.

Finally, tell your helpdesk what is changing and update your runbooks, since the admin experience, and where people look for these options, is about to shift. Microsoft rates the admin impact as medium and the user impact as low, but a quiet inventory now is much cheaper than a surprise auto-migration in mid-2027. Because the dates have already moved once and sources differ slightly on timing, treat the details above as a snapshot and verify them against the current message center posts and Microsoft Learn documentation before you plan your migration window.

Connect

Stay updated with latest Microsoft blog news

© 2025. All rights reserved.