New AutoPilot Windows 11 build, OneDrive fails to create folder

Question

We are working towards a new build process using AutoPilot. Our devices are fully built by Autopiot and InTune. There is a set of required applications, one of which is OneDrive (business).

For a device I build with the same OS version and same version of OneDrive I have no issue authenticatign to oneDrive and starting the synchronisation. With the new autoPilot built device, I receive the error "Sorry, OneDrive cna't add your folder right now".

I have read various forum articles suggesting I delete the cache from appdata, and various other performative moves that made no difference.

Answer 1

The solution was to remove the restriction on requiring domain membership to authenticate to the OneDrive service.

Answer 2

What stands out here is that the issue only occurs on the Autopilot-built device, not on a manually built device with the same OS and OneDrive version.

That usually points to a provisioning / identity timing issue, not a OneDrive version problem.

In Autopilot scenarios, there are a few additional moving parts:

Azure AD / Entra join timing

Primary Refresh Token (PRT) availability

Intune policy application order

Known Folder Move (KFM) policies

SilentAccountConfig behavior

The error “OneDrive can’t add your folder right now” commonly occurs when OneDrive starts before the user’s Entra identity and PRT are fully established.

A few things I would check:
Confirm the device identity state

On the affected machine, run:

dsregcmd /status
Verify:

AzureAdJoined = YES

DomainJoined (if hybrid)

AzureAdPrt = YES

If AzureAdPrt is NO, OneDrive authentication may fail during initial provisioning.

Check when OneDrive is being installed

If OneDrive is being installed in device context during ESP, it may launch before the user sign-in process fully completes.

Compare:

• Device context vs user context install
• Whether SilentAccountConfig is enabled via Intune policy

Review Known Folder Move Policies

If you are enforcing Known Folder Move via Intune:

Confirm the user is licensed correctly

Confirm the policy is not applying before the account is fully authenticated

Review OneDrive admin center sync health

KFM applying before token availability can produce this exact behavior.

Test Post-Provisioning Behavior

After Autopilot completes and the device sits for a few minutes, try:

Signing out and back in

Running dsregcmd /status again

Manually launching OneDrive

If it works after identity settles, that confirms timing rather than corruption.

If the manually built device works with identical versions, that strongly suggests the difference is in Autopilot provisioning order or identity readiness — not cache corruption.

https://learn.microsoft.com/sharepoint/use-silent-account-configuration

https://learn.microsoft.com/entra/identity/devices/concept-primary-refresh-token
https://learn.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot
https://learn.microsoft.com/sharepoint/redirect-known-folders