Cloud storage for remote teams: OneDrive, SharePoint, and what goes where

When every employee was in the office, storing files on a shared drive made sense. Everyone was on the same network, the file server was in the closet down the hall, and if someone needed access to something, they either had it or they asked the person next to them. Remote work broke that model quietly. A file on a laptop in Seattle is not a file the team in Boston can open. A file on the office file server is a file the remote team can reach only through a VPN that half of them hate using. Files are usually the migration that remote workers feel most, but they are one piece of a larger sequence – see cloud migration for remote teams for the full priority order when remote access is the migration driver.

Microsoft 365 solves this through two tools that look similar but do different jobs: OneDrive and SharePoint. Used well, they give a remote team cloud-first file storage that is faster than the old file server, more resilient than local drives, and coherent for how distributed work actually happens. Used poorly, they recreate every problem of a traditional file server plus a few new ones specific to the cloud.

This guide covers what each tool is for in a remote-work context, how to decide where specific kinds of files should live, what to do about the laptop-only files that still exist on most teams, and the Teams-SharePoint relationship that confuses everyone.

The quick mental model

Stripped to essentials:

• OneDrive is your personal cloud drive. Files you are working on individually, drafts, personal work notes, things you have not shared with anyone yet.
• SharePoint is the team’s shared drive. Files the business owns, content the team collaborates on, anything that needs to survive the individual employee who created it.
• Teams files are SharePoint files with a Teams interface in front of them. When you upload a file to a Teams channel, it goes to that team’s SharePoint site.

If you already use OneDrive vs SharePoint well in your business, most of this guide will be a refresher. If you are in the phase where nobody knows where anything is and half the important files are on one person’s laptop, keep reading.

For the more detailed platform comparison, see OneDrive vs SharePoint. The focus of this guide is the remote-team-specific implications.

Why remote teams care about this more than on-site teams

On-site, local storage problems resolve themselves socially. The laptop dies, the employee walks over to IT, someone helps them recover the files from whatever half-backup existed. If a file is only on one person’s machine, the team notices when that person goes on vacation and someone has to chase them down.

Remote removes the social resolution layer. When the laptop dies in Seattle, nobody notices until a missed deadline three days later. When the only copy of a critical spreadsheet is on a personal OneDrive that belonged to an employee who just left, there is no easy way to recover it. The edge cases that were annoying in-office become real incidents when the team is distributed.

This pushes remote teams toward cloud-first storage whether they planned for it or not. The question becomes: do you end up there deliberately, with a sensible structure, or accidentally, with files scattered across a dozen places nobody tracks?

Where each file type should live

A practical taxonomy:

OneDrive for personal and in-progress work

• Draft documents you are not ready to share
• Personal work files (meeting notes, personal to-do lists, reference material for your own role)
• Scratch space for research, writing, or analysis that may become shared later
• Personal backups of files the team does not need to see

A reasonable rule: if you are the only person who should see this file, it goes in OneDrive. If it becomes something the team needs, move it (not copy it) to SharePoint.

SharePoint for shared team content

• Documentation and standards that apply to the team
• Client files, project folders, and deliverables
• Templates and shared resources
• Records and archives
• Anything owned by the business rather than by an individual

A reasonable rule: if the file would still need to exist if you left tomorrow, it belongs in SharePoint.

Teams for conversational work

• Files being discussed in a current thread
• Drafts being reviewed by a channel
• Quick uploads during a meeting

Teams files are SharePoint files under the hood – every Teams channel creates a folder in the backing SharePoint site. The Teams interface is just a more conversational way to access them.

Email attachments still exist, but should not

The old pattern of sending files as email attachments creates version-hell: someone sends a doc, three people edit it and send back edits, merging is manual, nobody knows which copy is current.

The modern pattern: put the file in SharePoint or OneDrive, send a link instead of the file. Everyone edits the one canonical version, co-authoring works automatically, and there is one answer to “which copy is current.”

The laptop-only file problem

The biggest cloud storage issue for remote teams is not choosing between OneDrive and SharePoint. It is the files that live only on someone’s local drive and have never been synced anywhere.

This happens for predictable reasons:

• The employee saves to Desktop or Documents out of habit
• They are working on something sensitive and “will upload it when it is done”
• They dragged files in from an external drive and never moved them to the cloud
• Their OneDrive sync has been broken for weeks and they have not noticed
• A legacy application saves files to a local folder by default

When the laptop dies, the local hard drive gets encrypted by ransomware, or the employee leaves, those files are either lost or stranded. Your business does not know what was there.

Known folder move (KFM) is the fix

Windows 10 and 11 support a Group Policy or Intune-managed setting called Known Folder Move, which redirects Desktop, Documents, and Pictures to OneDrive automatically. Every file the user saves to those folders syncs to OneDrive in the background. If the laptop dies, a new laptop signs into the same account and the files appear within minutes.

On macOS, OneDrive has a similar feature (Folder Backup) that covers the Desktop and Documents folders.

Both should be enabled on every company device. Without them, “the cloud storage strategy” is really just “the storage strategy for the files employees remember to upload manually.”

What KFM does not cover

• Files saved to folders outside the known-folder set (downloads, custom folders, other drives)
• Files on external drives or USB sticks
• Files on personal devices under BYOD (MAM policies cover business apps, not arbitrary file locations)
• Files that are cached in an application but not saved (email attachments opened directly, unsaved documents)

The remaining gap is covered by a mix of user training, sensible default save locations, and occasional audits. It does not go to zero, but it gets significantly smaller.

What happens when a laptop dies

With KFM and cloud-first storage in place, a laptop failure is a minor inconvenience. The employee’s replacement device syncs OneDrive on first sign-in and they are back to work within a few hours.

Without those, a laptop failure is a potential loss of work product, lost time to reconstruct, and a reminder that “backups” are not the same as “cloud sync” (they are both useful, and they serve different purposes).

This is part of what makes remote offboarding tractable too. When the employee leaves, their OneDrive files are in the cloud, recoverable by the manager, wipeable remotely. Nothing is stranded on the laptop.

The Teams and SharePoint relationship

A source of confusion for almost everyone: “Where did my Teams file go? Is it in SharePoint now? Is it different from the Teams file?”

The actual structure

Every Microsoft 365 Team has a backing SharePoint site. Every channel in that team has a folder in that SharePoint site. When you upload a file to a channel, it goes into that folder.

So the file exists in exactly one place – SharePoint. Teams gives you a different way to access it, with message threads, co-editing, and notifications attached. The file is not duplicated; it is the same file, surfaced through multiple interfaces.

Private channels are different

Private channels in Teams create their own separate SharePoint site (not just a folder). This is by design – private channels have different permissions than their parent team, and SharePoint handles that cleanly by isolating the storage.

If you rely heavily on private channels, your SharePoint site list will be longer than you expect, because each private channel spawns its own site.

Standard channels share a site; private channels do not

This has a practical consequence: moving files between channels in the same team is straightforward (same SharePoint site, just different folders). Moving files between a private channel and a standard channel, or between two private channels, requires a copy operation across SharePoint sites.

What this means for where to put what

• Persistent team content: SharePoint document libraries, referenced in Teams channels where appropriate
• Conversational files: Teams channels directly
• Private project work with restricted access: private channels (or a separate SharePoint site)
• Company-wide policies, templates, reference material: a central SharePoint site accessible to everyone, separate from Teams

Permissions in a remote context

On the office network, permissions were often loose – everyone could see most of the file server because setting up proper permissions was tedious and nobody had time. Remote work tightens this, because file sharing happens over the internet and sloppy permissions become external-sharing problems.

Least privilege by default

Grant access to what people need, not to everything. For each SharePoint site, think about who should have access and assign based on groups, not individuals.

Group-based permissions, not user-based

Create security groups or Microsoft 365 groups for each team/project, assign permissions to the group, add users to groups as needed. When someone joins or leaves, you update the group membership, not the permissions on dozens of sites.

External sharing policies

SharePoint can be configured to allow or block sharing with external users (clients, vendors, contractors) at the tenant level, per-site, and per-file. Decide your policy and configure it explicitly:

• Tenant default: blocked or restricted to authenticated users
• Specific sites that need external collaboration: allowed with authentication
• Public “anyone with the link” sharing: almost never the right default

For most SMBs, the right baseline is “authenticated external users only” – people can share files externally, but the external user has to sign in (with their own email, typically), which creates an audit trail and allows access revocation.

Link expiration

External share links should expire. 30, 60, or 90 days is a reasonable window depending on the work. Perpetual public links get forwarded, indexed, and persist for years after they are needed.

Audit logs

Every access to sensitive SharePoint files should be logged. Microsoft 365 audit logs are retained (default 90 days, configurable up to 10 years in higher tiers) and searchable. When something goes wrong, the log is what lets you answer “who saw this file, when, and from where.”

Common remote cloud storage mistakes

Everything in one SharePoint site

A single site with hundreds of document libraries, used by everyone, no meaningful permissions – this reproduces the old “everyone sees everything on the file server” problem in the cloud. Break it up into multiple sites with appropriate scope.

One massive team in Teams

A “Company” team with 50 channels is unwieldy to navigate, hard to permission, and generates too much notification noise. Separate teams for separate work areas. Set up Teams thoughtfully rather than letting it grow organically.

Storing business-critical files in individual OneDrives

OneDrives are tied to a specific user. When that user leaves, their OneDrive becomes a retention problem rather than a usable resource. Business-critical files belong in SharePoint from the start.

Disabling OneDrive because “we do not need personal cloud”

Wrong. Even if you do not want personal-use files in OneDrive, you want OneDrive active so Known Folder Move redirects local saves to the cloud. Disabling OneDrive means every local-save is stranded on the device.

Relying on Teams chat file sharing for anything permanent

Files shared via Teams chat (not channels – chat messages specifically) go to the sender’s OneDrive, in a “Microsoft Teams Chat Files” folder. This is the wrong place for anything the business should retain. Use channels (which go to SharePoint) for persistent files.

Not configuring external sharing explicitly

“We have not thought about external sharing” is effectively “anyone with a link can share anything externally.” Decide the policy and configure it.

Assuming Microsoft is backing up your files

Microsoft 365 has retention policies, not backups. Retention rules preserve files during the retention window, which is typically short and can be defeated by a compromised admin account. Proper Microsoft 365 backup is a separate service you subscribe to, either from a dedicated vendor or as part of a managed backup service.

No retention policy for leaving employees

When an employee leaves, their OneDrive is retained for 30 days by default, then deleted. If no one grabs the files in that window, they are gone. Build the “copy or assign the departing employee’s OneDrive files” step into your remote offboarding process.

Moving off an old file server to the cloud

Most SMBs with a remote or hybrid workforce are either past or in the middle of the file-server-to-SharePoint transition. A few observations for how to do it well:

Do not migrate the mess

The folder structure on the old file server is probably 15 years of accumulated cruft. Files nobody has touched in a decade, folders named “temp” that are actually permanent, duplicate copies from three reorganizations ago. Copying all of that into SharePoint moves the mess without fixing it.

Take the migration as an opportunity to clean up. Archive what is not needed. Reorganize around how the business works now, not how it worked when the server was set up. Every file that survives the migration should have a purpose.

Migrate in phases

Not everything moves at once. A typical sequence is:

1. Least-accessed archives first (practice on low-stakes content)
2. Team-specific content (each team’s files to their SharePoint site or Teams channel)
3. Company-wide content last (once patterns are established)

The file server to SharePoint migration article covers the operational side of this in more detail.

Keep the old server around as read-only for a while

Do not decommission the file server the day after migration. Keep it mounted as read-only for a few months so anyone who forgot to migrate something can still reach the original. Schedule the actual decommission, and stick to it.

Train on the new structure

A migration without training produces frustration. Give users a short (30-minute) session on where content lives now, how to find things, how to share, and how the folder structure maps to what they were doing before. Record it for future reference.

How cloud storage fits into broader remote IT

Cloud storage is one part of remote and hybrid team IT, which overlaps with endpoint management (KFM is delivered through Intune), M365 licensing (OneDrive/SharePoint capacity scales with plan), and security posture (external sharing, conditional access, DLP policies).

The reason it matters enough to treat as its own topic is that it is the foundation everything else sits on. Identity without files accessible is useless. Devices without a good storage story lose work. Teams and collaboration depend on files being in findable, consistent places.

A business that gets cloud storage right – sensible structure, known folder move enabled, proper permissions, regular audits – tends to do well on most of the adjacent disciplines. A business that gets it wrong struggles with everything from onboarding (new hires cannot find anything) to offboarding (files stranded with the former employee) to compliance (we have to find every copy of X and we cannot).

How Sequentur handles cloud storage for clients

For clients on our managed IT support for remote and hybrid teams using Microsoft 365, cloud storage runs as part of the ongoing service. Known Folder Move is enabled across managed devices via Intune, OneDrive and SharePoint structures are configured during onboarding and refined as the business evolves, external sharing policies are set to the client’s risk tolerance, and audit logs are reviewed periodically for anomalies.

For clients still on a traditional file server, migrating to SharePoint and OneDrive is scoped as a project – inventory, cleanup, structure design, phased migration, user training, and decommissioning the old server. Once the migration is complete and the environment is stable, the ongoing operation moves into managed IT.

If your cloud storage today is a mix of “files on laptops, files on the old file server, files in personal OneDrives nobody can see, and some stuff in Teams somewhere,” schedule a call and we will walk through what a coherent remote-first storage setup looks like for your team.