About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
After moving applications to a hosting provider, put files where the things that use them are. Files opened by hosted applications, or reached through mapped drives and network paths, suit a file server alongside the hosted servers. Documents that people edit, share and open across several devices suit SharePoint and OneDrive, within Microsoft's documented limits for the OneDrive sync app and for SharePoint libraries. Leaving files on the office NAS keeps them close to staff but far from hosted applications. Before choosing, measure how many files you have, the largest ones, and which applications reach files by path.
Why it matters
A file location that worked when everything sat in one office can become slow or fragile once applications move. An application on a hosted server reading templates from a NAS in the office sends every read across the internet link. Staff syncing hundreds of thousands of files to every laptop can hit sync limits. The choice affects speed, reliability and how backups are done.
How it works
A file server alongside the hosted servers
A Windows file server at the host shares folders over SMB. Microsoft describes SMB as allowing "an application (or the user of an application) can access files or other resources at a remote server, allowing applications to read, create, and update files on the remote server". Hosted applications reach it over the provider's local network. Mapped drives and network paths keep working once updated. Staff in the office or at home reach it through the same private connection or remote desktop they use for the applications.
SharePoint and OneDrive
Files live in Microsoft 365 and sync to devices or open in a browser. Microsoft documents limits, and the ones below are for the OneDrive sync app; SharePoint has its own limits for libraries viewed on the web, listed on the same page. On sync volume, Microsoft recommends "syncing no more than a total of 300,000 items across your cloud storage" for optimum performance. A public preview raises this to 1,000,000 items per sync instance per device on Windows and macOS, but only for devices that meet its requirements, including the OneDrive Insider programme, and Microsoft states that "This preview doesn't support virtual desktop infrastructure (VDI) environments." Plan on 300,000 as the general figure.
Where staff work in hosted remote desktop sessions, OneDrive sync inside those sessions has its own requirements. Microsoft states that "All non-persistent VDI environments require the latest version of FSLogix and a per-machine installation of the OneDrive sync app." Ask your provider how its remote desktop servers are set up before relying on sync there. On file names, some names are not allowed, including ".lock, CON, PRN, AUX, NUL" and others listed on the page. On mail archives: "Outlook .PST files are supported, but the sync app syncs them less frequently than other file types to reduce network traffic." The page also notes that path length limits depend on the app, and that "Different apps and Office versions have different limits."
The office NAS
Keeping the NAS avoids a migration, and staff in the office get local speed. But hosted applications and remote staff reach it over the office internet link, and its protection depends on the office: power, backup and physical security. A NAS can still play a part, for example holding large files used only on site, as long as it has its own off-site backup and someone is responsible for its updates. Treat it as one of the locations to plan, not as the default because it is already there.
What to choose and why
Measure first
- Total file count and size, and the largest folders.
- Largest individual files and file types, such as video, CAD drawings or mail archives.
- Applications that open files by network path, and the paths they use.
- Folders shared with outside parties.
- Who works away from the office, and on what devices.
A decision table
| If the files are… | Consider | Watch for |
|---|---|---|
| Opened by hosted applications or reached by path | File server at the host | Updating mapped drives and paths; backup at the host |
| Documents edited and shared across devices and with outsiders | SharePoint and OneDrive | Sync volume, file names, path lengths; sync requirements in hosted remote desktop sessions |
| Large media used only in the office | Office NAS, with an off-site backup | Remote access speed; office power and backup |
| Mixed | A combination, with each folder assigned one home | Avoid the same files in two places |
The table is editorial guidance.
One home per folder
Mixed designs work when each folder has exactly one authoritative location. Copying the same files to two places invites conflicting versions.
Illustrative example
A 30-person engineering firm moves its project database to a host. Its drawing templates are read by the hosted application, so they move to a file server at the host. Project documents shared with clients move to SharePoint. Large site photos and video, used mostly in the office, stay on the NAS with a nightly off-site backup. The example is illustrative.
Read next
Related articles you may want next.
- Backup & RecoveryOneDrive Known Folder Move protects files, but it is not the whole backupUnderstand which files OneDrive Known Folder Move protects, how recovery windows differ and what endpoint recovery still needs.Read article
- Backup & RecoveryRestoring a file server: bringing back the shares and settings, not just the filesRecover Windows file-server service beyond its files: share definitions, permissions, SMB settings, names and client acceptance checks.Read article
- HostingUNC paths and file-share dependencies for hosted Windows line-of-business appsWhat fails in hosted Windows LOB applications when SMB shares, DFS namespaces or drive mappings change—and how to map runtime dependencies before routine moves.Read article
Risks and limits
- Databases need special care. Database files opened by desktop applications should not sit on sync services or slow links; see the article on splitting an application between office and cloud.
- Backup differs by location. SharePoint retention is not the same as a tested backup; confirm how each location is protected.
- Migrations change paths. Update shortcuts, mapped drives and application settings together.
- Limits change. Recheck Microsoft's page before deciding.
- Related reading. Our published articles UNC paths and file-share dependencies for hosted Windows line-of-business apps, OneDrive Known Folder Move protects files, but it is not the whole backup and Restoring a file server: bringing back the shares and settings, not just the files go further; our companion article on where remote staff should save files covers the day-to-day habit.
Sources
Opened 15 November 2026; both Microsoft pages and the published articles reopened 16 November 2026.
- Microsoft Support: Restrictions and limitations in OneDrive and SharePoint, no date shown on the page (page metadata: 21 October 2026).
- Microsoft Learn: What is SMB file sharing for Windows?, page shows last updated 27 November 2025 (page metadata: modified 12 October 2026).
Related service: Cloud hosting.
Learning notes
- Put files near the things that use them.
- Hosted applications reading files by path suit a file server at the host.
- Microsoft recommends syncing no more than 300,000 items; a 1,000,000-item preview has requirements and excludes VDI.
- OneDrive sync in non-persistent remote desktop sessions needs the latest FSLogix and a per-machine sync app.
- Some file names are blocked in OneDrive and SharePoint; PST files sync less often.
- Give each folder one authoritative home.
This article was originally published on .