OneDrive Admin Checklist: Known Folder Move creates duplicate folders for department pilots

When you run Known Folder Move for a department pilot, you may see duplicate Desktop, Documents, or Pictures folders appear in users’ OneDrive. This happens when the Known Folder Move policy is applied to a user who already has those folders redirected to OneDrive from a previous manual setup or a different policy. This article explains the exact cause of duplicate folders during KFM pilot deployments, provides a step-by-step checklist to prevent and resolve duplicates, and covers related failure patterns that affect pilot groups.

Why Known Folder Move Creates Duplicate Folders During Pilots

Known Folder Move redirects the Desktop, Documents, and Pictures folders from the local user profile to OneDrive. When the policy runs on a device where one or more of those folders are already synced to OneDrive through a manual move or a previous KFM policy, the sync client creates a new OneDrive folder with the same name. For example, if a user manually moved their Documents folder to OneDrive last month and the pilot policy runs today, the user ends up with both Documents and Documents 1 in OneDrive.

The root cause is that OneDrive detects the existing folder as a conflict because the original folder was not moved by the current policy. The sync client does not merge the two. Instead, it creates a duplicate to avoid data loss. This behavior is by design but causes confusion for pilot users and extra cleanup work for admins.

Why Pilots Are Especially Vulnerable

In a pilot deployment, you are testing the policy on a subset of users. Those users may have already configured OneDrive folder backup manually as part of their daily work. When the pilot KFM policy is applied, it attempts to move the known folders again. The sync client sees that the folder already exists in OneDrive and appends a number to the new folder name. The result is a duplicate folder that contains only the files that were present at the moment the policy ran, not the complete folder contents.

Checklist to Prevent and Resolve Duplicate Folders in a KFM Pilot

1. Audit current folder protection before the pilot
   Use the OneDrive admin center or a PowerShell script to check which users in the pilot group already have known folders redirected to OneDrive. Run Get-OneDriveKnownFolderMoveStatus for each user. Exclude users with existing redirection from the pilot policy or reset their folder protection before applying the policy.
2. Create a dedicated pilot security group
   Create a security group in Microsoft Entra ID that contains only the pilot users who do not have existing folder redirection. Apply the KFM policy to this group only. Do not use an organizational unit or a dynamic group that includes users with varied folder states.
3. Set the KFM policy to gradual rollout
   In the OneDrive admin center, go to Sync > Known Folder Move. Under Rollout, select Gradual rollout and set a start date. This gives you time to monitor the first few users and catch duplicates before the entire pilot group is affected.
4. Disable the user prompt for folder protection
   In the Group Policy Object for OneDrive, enable the setting Silently move Windows known folders to OneDrive. Set Prompt user to protect to Disabled. When users are prompted, they may manually move a folder before the policy runs, which creates the duplicate condition.
5. Deploy the policy to a single test user first
   Add one user to the pilot security group. Wait 24 hours. Check the user’s OneDrive for any duplicate folders. If duplicates appear, remove the user from the group, reset their folder protection, and re-add them after verifying the folder state.
6. Use the OneDrive Sync client report to detect duplicates
   After the pilot policy is applied to the test group, run the OneDrive Sync client health report in the Microsoft 365 admin center. Look for users with the status Duplicate folder detected. This report shows which users have duplicate folders and the folder names.
7. Resolve duplicates by merging the folders
   If duplicates are found, sign in to the affected user’s device. Open OneDrive in File Explorer. Right-click the duplicate folder and select Copy. Navigate to the original folder and paste the contents. After the files are merged, delete the duplicate folder. The user’s files will sync normally after the merge.
8. Reset folder protection for users who had duplicates
   After merging the folders, run StopKnownFolderMove in PowerShell to reset the user’s known folder state. Then reapply the policy through the security group. The sync client will now move the merged folder without creating a duplicate.

If Known Folder Move Still Creates Duplicate Folders After the Checklist

User had a previous manual folder move that was not detected

The audit script may miss users who moved their folders using a third-party tool or a different account. To check manually, open the user’s OneDrive in a browser and look for folder names ending in a number, such as Documents 1. If found, use the merge and reset steps above.

The policy was applied to a device that was offline

If a device is offline when the KFM policy is applied, the sync client may not receive the policy correctly. When the device comes online, it processes the policy and may create duplicates. To prevent this, use the Defer setting in the OneDrive admin center to delay policy enforcement on devices that have been offline for more than 14 days.

User has multiple OneDrive accounts on the same device

If a user has both a personal Microsoft account and a work or school account signed into OneDrive, the KFM policy for the work account may conflict with the personal account’s folder redirection. Remove the personal account from OneDrive before applying the pilot policy.

Known Folder Move Pilot vs Full Deployment: Key Differences

Item	Pilot Deployment	Full Deployment
User group size	5 to 50 users	500 or more users
Policy rollout	Gradual rollout with manual monitoring	Automatic rollout with health reports
Folder state audit	Required before each user is added	Run once for the entire organization
Duplicate folder risk	High due to existing manual redirections	Low if the pre-deployment audit is thorough
Cleanup approach	Manual merge per user	Automated PowerShell script for bulk merge

Now you can run a Known Folder Move pilot without creating duplicate folders by auditing folder states, using a dedicated security group, and deploying gradually. Next, review the OneDrive Sync client health report weekly during the pilot to catch any duplicates early. An advanced tip: use the Get-OneDriveKnownFolderMoveStatus cmdlet with the -IncludeDuplicates parameter to list all users who have duplicate folders before you run the pilot policy.