Skip to content
TrustList
News

OneDrive stops syncing new node_modules folders by default from 14 December 2026

Editorial

By TrustList Editorial

Microsoft Message Center post MC1558030: OneDrive for Windows and Mac will exclude newly created node_modules folders from sync from 14 December 2026, with an admin policy to switch the exclusion off.

About OneDrive stops syncing new node_modules folders by default from 14 December 2026

OneDrive stops syncing new node_modules folders by default from 14 December 2026

17 November 2026: Microsoft has told Microsoft 365 administrators that the OneDrive sync app for Windows and Mac will, by default, stop syncing newly created folders named node_modules. The post, numbered MC1558030, is tagged as a major change with an act-by date of 14 December 2026.

Not yet independently verified. We read the Message Center post through a public archive mirror (mc.merill.net), not the Microsoft 365 admin centre itself, which needs a sign-in. The mirror shows the post as published on 17 November 2026. We did not test the new behaviour or the policy that turns it off. We will update this when it can be confirmed, and remove this note.

What will change

Beginning on 14 December 2026, the sync app will exclude new folders named exactly node_modules, whatever the capitalisation. The excluded folders stay on the device and are not uploaded, so they will not be available through OneDrive on the web or on other devices. Users get no prompt. The post says the change extends OneDrive's existing default exclusion list, which already covers .db-wal files, a change announced in a separate post, MC1457838, on 5 October 2026.

Microsoft gives the reason as performance. JavaScript and Node.js projects can create tens of thousands of small dependency files in node_modules, and the post says excluding them should improve sync performance and cut storage and bandwidth use. Developers can rebuild these folders with their package manager.

Which OneDrive users will notice the exclusion

The post says the change affects users with work or school accounts who create node_modules folders in OneDrive-synced locations, including the Desktop and Documents folders managed through Known Folder Move. It applies to OneDrive for Windows and OneDrive for Mac. Folders that are already syncing continue to sync, and OneDrive will not remove existing content from the cloud or from devices.

Timing

General availability is worldwide. The rollout begins on 14 December 2026 and, according to the post, is expected to finish by mid-January 2027, so some users will see the new behaviour later than others.

Controlling the default

Administrators who need these folders to keep syncing can use the existing OneDrive sync policies to turn off the default exclusion list. The post links to Microsoft Learn pages on configuring the sync app for Mac and on using OneDrive policies to control sync settings. It says to configure the appropriate policies before 14 December 2026 if your organisation needs node_modules to sync.

What an administrator should do

First decide whether you want the new default. For most teams the answer is yes: a dependency folder that can be rebuilt does not need cloud storage, and leaving it out reduces upload queues on developer laptops. If that is your view, no action is required.

If a project depends on node_modules being present on other machines, for example a shared workspace that is not rebuilt from a lockfile, decide whether to change the workflow or the policy. Rebuilding from the lockfile is usually the safer habit, because it makes the build repeatable.

Whichever way you go, update your helpdesk and developer guidance, as Microsoft recommends. Tell developers who keep code projects in OneDrive-synced locations that new node_modules folders will stay local, that a second computer needs its own install step, and that a missing folder on the web is expected rather than a sync fault. Check which teams use Desktop or Documents redirection for code, because they are the most likely to notice, and prepare a short answer for the first support calls after rollout begins.

Finally, review the policy settings in a pilot group before 14 December, so that your exceptions are tested and documented.

Related on TrustList:

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in

Tigris says its product, S3-compatible API, zero-egress pricing and team stay the same. Dropbox will use it to start DBX Agent Cloud, storage for companies building AI applications, with filesystem and content-processing features next.