← All blogs

OneDrive for Business Problems and Solutions in 2026: A Field Guide for MSPs

Ask a service desk lead what Microsoft 365 app causes the most calls. OneDrive is usually the first answer.

It is not that the tool is terrible. It just lives right at the point where a person’s desktop and the cloud meet. So, you see all kinds of issues come through.

Odd file names
Older laptops that struggle
Slow or spotty Wi-Fi
Even a 12-year-old line of business app that users still rely on

It all gets blamed on OneDrive.

The "Sync Pending" Ticket That Never Really Means What It Says

Before you reset anything, check whether the problem is one user or the whole tenant. If three people report the same stuck upload inside an hour, it's a service issue, and touching endpoints just burns hours.

For a single user, work through it in this order:

Open the file in the browser first. If the newest version is sitting in OneDrive online, the cloud side is fine, and you're chasing a client-side blocker. Then look at the actual sync icon rather than guessing. A red circle means an error you can click into. A dash means the item isn't syncing at all, which points to a name, path, or file-type block.

Check free disk space and the tenant storage quota next. A user at 99% of their 1 TB allocation produces symptoms that look exactly like a broken client.

Then check the account. Wrong-account sync is a genuine time sink. The browser is signed in as one identity, Word is signed in as another, and the sync app is quietly running a third. This happens constantly on machines where someone once tested a personal account.

Only after all of that should you run %localappdata%\Microsoft\OneDrive\onedrive.exe /reset. The icon vanishes for a few minutes while the client rebuilds its state, and on a large library the re-scan can take a while, so don't start it five minutes before the user's meeting.

Microsoft's Support and Recovery Assistant handles a chunk of this automatically and is worth putting in your tech toolkit.

When Known Folder Move Goes Wrong, Users Think Their Files Are Gone

"All my Desktop files disappeared" is rarely a deletion. It's Known Folder Move finishing its job, moving Desktop, Documents and Pictures under the OneDrive root, and the user not recognising the new location.

The real trouble starts when folder redirection Group Policy is still live on the same machine. An old GPO pointing Documents at a file server, plus KFM pointing it at OneDrive, gives you two systems fighting over the same folder. Files bounce, shortcuts break, and you get duplicates.

Clean it up by retiring the redirection policy before you roll KFM out, not after. Then push KFM silently with the tenant ID so users never see a prompt they can decline. Machines with roaming profiles and folder redirection both switched on need the redirection removed first and profiles allowed to settle.

One more thing worth documenting in your runbook: after a wipe and reload, a user whose old machine still holds unsynced content will lose it. Confirm a green check across the whole tree before you collect the device.

Libraries That Are Simply Too Big

Microsoft's guidance has long been to stay under 300,000 items in total across everything a device syncs, and performance problems can start above that even when you aren't syncing all of it. That ceiling has now moved for some machines.

Since late April 2026, OneDrive sync on Windows supports up to 1 million items per sync instance per device, starting as a public preview.

The device has to meet real hardware requirements to get it: Windows 11 or Windows Server 2022, at least 16 GB of RAM with 32 GB recommended, an SSD, an Intel i5 or AMD Ryzen 5 class processor or better, the Insiders ring turned on, and it doesn't cover VDI. General availability is scheduled for later in the year.

Don't sell that as a fix to clients. The honest answer for a 600,000-item shared library on a fleet of 8 GB laptops is still restructuring: split the library, archive what hasn't been touched in five years, and stop syncing folders nobody opens.

Use shortcuts to shared libraries instead of full sync where people only need occasional access.

File Names And Paths Still Break Sync In Ways Users Never Guess

This one is unglamorous, and accounts for a big share of "it won't upload" tickets.

Characters that block sync: " * : < > ? / \ |. Leading and trailing spaces do it too. Certain names are rejected outright, including: .lock, CON, PRN, AUX, NUL, COM0 through COM9, LPT0 through LPT9, anything containing _vti_, desktop.ini, and any file starting with ~$.

Path length matters as well: the decoded path, including the file name, can't exceed 400 characters, and once files are on a Windows machine, each individual folder or file name is capped at 255 characters.

Legal firms, architects and anyone with a deep client-matter folder tree hit the path limit constantly. The practical fix is shortening folder names near the top of the tree, because every character there multiplies down the whole structure.

Before any file server to SharePoint or OneDrive migration, run a scan for bad names and long paths and fix them at source. Discovering 4,000 problem files during cutover weekend is a bad way to spend a Saturday.

Apps That Can't Live Inside a Synced Folder

Files On-Demand keeps laptops from filling up, and it's on by default. It also confuses software that expects a real file to be sitting on disk.

Things that should not live in a synced OneDrive folder: QuickBooks company files, Access database back ends shared by more than one person, Sage data directories, Outlook PST files, CAD and Revit project files that multiple people open at once, and video project scratch folders.

These formats hold file locks or write constantly, and the sync engine either fights them or produces conflict copies with a device name tacked on the end.

Rather than switching Files On-Demand off for a whole tenant, mark specific folders as "Always keep on this device" for the users who need them and move genuinely shared databases to a proper host: a hosted server, the vendor's own cloud product, or a small Azure VM.

A Deletion Behaviour Change Your Clients Should Hear About

Here's a change that will quietly alter how recovery works on client machines. Microsoft announced in April that the sync client would stop handling cloud-initiated deletions by dropping the local copy into the workstation Recycle Bin.

Instead, the client just removes the local copy, with the updated sync app rolling out from early May through late May 2026.

What that means at the service desk: the local Recycle Bin stops being a safety net for files someone deleted from the web or from another device. Recovery moves to the OneDrive recycle bin and File Restore.

Update your ticket notes and your client-facing "how to get my file back" article, because the old advice now sends people to an empty bin.

Default sharing settings are built for convenience, and three years later a client has thousands of live "Anyone with the link" URLs, a handful of them pointing at payroll.

Set the default link type to people inside the organisation. Put an expiry on anonymous links, seven to thirty days depending on how the client works. Switch view-only links to block downloads where that fits.

Then review external sharing tenant-wide and per-site rather than leaving it wide open, and pair it with sensitivity labels for anything the client is regulated on.

For MSPs, the win is turning this into a standing quarterly review item instead of a panic response to a client's insurance questionnaire.

Storage, Licences And The Data That Disappears Quietly

Most Microsoft 365 Business and Enterprise plans include 1 TB of OneDrive storage per licensed user, with larger allocations available on some enterprise plans by request. Two things bite MSPs here.

First, a user who hits their quota stops syncing, and the error message doesn't say "you're full" in words most people read.

Second, and more serious: OneDrive data is tied to the licence. Pull a licence to save money on a departed staff member, and the clock starts.

When a user is deleted, their OneDrive is kept for the number of days set in the SharePoint admin centre, which defaults to 30. After that, it sits in a deleted state for 93 days, and only an admin can bring it back.

Build an offboarding checklist that grabs the data first: hand access to the manager, move what's needed to a SharePoint site, then remove the licence. Doing it in the other order is how a client loses three years of a salesperson's files.

"OneDrive Is Our Backup" Is The Most Expensive Myth In The Stack

Microsoft runs the platform. The client owns the data. Version history and recycle bins are convenience features with a clock attached, not backup.

Work and school recycle bins hold deleted items for 93 days. File Restore rolls a whole OneDrive back to a point within the last 30 days, which is genuinely good for a ransomware event caught quickly.

Document libraries keep 500 versions by default. None of that helps with a deletion discovered four months later, a retention policy someone changed, or a departing employee who cleaned house before handing in the laptop.

Third-party Microsoft 365 backup belongs in your standard stack, priced in from day one. Sell it as part of the base offering rather than an upsell, because the conversation you don't want is explaining after the fact why the files aren't coming back.

Set up alerts too. A mass-deletion alert policy catches the ransomware pattern early enough for Files Restore to actually work.

Personal Accounts Syncing Company Data

On unmanaged endpoints, users sign into personal OneDrive and start dragging work files into it. Turn on the policy that stops personal account sync, and use the setting that allows sync only for your client's tenant ID.

Add sync restrictions so only managed, joined devices can sync at all, and block file types that have no business leaving the tenant.

Making This Repeatable Across Every Tenant You Run

One-off fixes don't scale across 40 clients.

Build a standard OneDrive baseline and push it through Intune or Group Policy on every new tenant: silent account configuration, silent Known Folder Move with the tenant ID, Files On-Demand on, a download threshold so huge libraries don't auto-fill small SSDs, personal sync blocked, tenant allow-list set, and upload rate limited on sites with thin connections.

Then watch it. The sync health view in the Microsoft 365 Apps admin centre shows you which devices are erroring before the user calls, which turns a reactive queue into a scheduled task.

Document the standard, apply it at setup, review it quarterly. That's the difference between OneDrive being a recurring cost centre and being something clients never think about.

Where MSP Depot Comes In

MSP Depot works with service providers who need the products behind this kind of delivery: backup for Microsoft 365, endpoint management, and the tooling that makes a standard build stick across every client.

If you're rebuilding your Microsoft 365 stack this year, start with the gaps above, because they're the ones that generate tickets and the ones clients notice.