MC1430530: OneDrive Adds Admin Control to Exclude Specific Folders from Syncing

📢 Official Microsoft Message Center Announcement

[What and Why:]

Microsoft is introducing a new OneDrive capability that allows organizations to exclude specific folders from syncing to OneDrive. This helps ensure machine-specific or development-related folders—such as PowerShell modules, Visual Studio configuration folders, and node_modules—remain local to the device instead of being uploaded to the cloud.

This enhancement improves manageability and storage efficiency by giving administrators granular control over which folders can be synchronized. It supports enterprise-ready management scenarios by helping organizations prevent unnecessary or device-specific content from consuming cloud storage while maintaining a consistent OneDrive experience for users.

This message is associated with Roadmap ID 567470.

[Rollout Schedule:]

• General Availability (Worldwide): We will begin rolling out in mid-August 2026 and expect to complete by late August 2026.

[Impact on Your Organization:]

Who is affected:

• Organizations using OneDrive for Windows and Mac
• OneDrive administrators managing sync policies
• Users storing development or machine-specific folders within OneDrive-managed locations

Platforms/Services:

• OneDrive for Windows
• OneDrive for Mac
• OneDrive Sync Client
• Group Policy

What will happen:

• The feature is OFF by default.
• No changes occur unless administrators configure exclusion rules.
• Administrators can define folder names or path patterns that should not sync to OneDrive.
• Folders matching configured rules remain on the local device and are not uploaded to OneDrive.
• Contents of excluded folders are also excluded from synchronization.
• Existing folders already synchronized before a rule is applied continue syncing until the user moves them out of OneDrive and then back into a synchronized location.
• Local files moved into an excluded folder after policy enforcement will remain local and will be excluded from syncing to OneDrive cloud storage. Moving files that are already syncing into an excluded folder is currently not supported.
• OneDrive must be restarted after policy changes for updated rules to take effect.
• Common use cases include excluding:
  • node_modules
  • PowerShell module directories
  • Visual Studio configuration folders
  • Other machine-specific development tooling folders

[Action Required/Recommendations:]

Action Required: Only if you plan to use this feature.

Recommended checklist:

• Review whether your organization has local-only folders that should be excluded from OneDrive synchronization.
• Evaluate development, scripting, or application configuration folders that generate unnecessary cloud storage consumption.
• Plan and implement folder exclusion rules using the new Group Policy settings when they become available.
• Test exclusion rules with a pilot group before broad deployment.
• Restart OneDrive after deploying or modifying exclusion policies to ensure policy enforcement.
• Update internal user guidance explaining which folders will remain local-only.
• Inform help desk and support personnel about the new behavior and expected user experience.
• Document any excluded folders within your organization’s endpoint management standards.

If you do not intend to use the feature:

• No action is required.
• Sync behavior remains unchanged unless exclusion policies are configured.

Learn more: IT Admins – Use OneDrive policies to control sync settings | Microsoft Learn (will be updated before rollout)

[Compliance Considerations:]

Source: Microsoft Message Center • Analysed by MWPro

Latest Posts