Has anyone run into OneDrive Known Folder Move failing on newly provisioned Intune-managed devices running Windows 11 24H2 or 25H2? Our existing policy has worked reliably for years, and Intune shows that the OneDrive settings are being assigned. The expected registry values are also present, so the policy appears to be reaching the devices. However, the Desktop, Documents, and other known-folder options remain disabled in the OneDrive interface, and users can toggle them manually. This is happening across new builds, which makes me wonder whether there is a recent Windows or OneDrive issue rather than a configuration problem.
3 Answers
I haven’t reproduced this on our Entra-joined, Intune-managed Windows 11 25H2 devices. A newly configured laptop on build 26200 applied the Known Folder Move settings correctly. It may be worth comparing the exact OneDrive policy options, including automatic sign-in and the tenant-specific settings, rather than relying only on the registry values.
The behavior may be specific to the newer Windows or OneDrive versions rather than Intune delivery. Since the policy values are present but the client does not enforce them, I’d compare the installed OneDrive version and build behavior on a known-good 23H2 device before opening a support case. A side-by-side test should help determine whether this is a client regression or an enrollment/configuration timing issue.
One possible workaround is clearing the Microsoft identity token cache. Close OneDrive, Office, and other Microsoft applications, remove the contents of C:UsersAppDataLocalPackagesMicrosoft.AAD.BrokerPlugin_cw5n1h2txyewy, then reopen OneDrive and an Office app so the authentication tokens are refreshed.
That’s worth testing, although these are freshly provisioned devices, so it’s odd that a stale-token problem would affect them.
That’s what makes this confusing—the same settings have worked for years, and the registry confirms they’re arriving. The OneDrive UI still shows all the toggles disabled, though.