SharePoint vs OneDrive: what each is for
OneDrive is storage for one person's work files, tied to that person's account. SharePoint is storage and publishing for a team or the whole organization, where the content belongs to a site instead of an individual. Files in Microsoft Teams channels are stored in SharePoint, and files sent in private chats are stored in the sender's OneDrive.

The short version: who owns the file
The useful question is not which product has more features. It is who owns the file when the person who created it changes jobs.
A file in OneDrive belongs to one user account. A file in SharePoint belongs to a site, and the site belongs to a team or to the organization. Everything else follows from that: permissions, retention, what breaks when someone leaves, and what an administrator can control.
| OneDrive | SharePoint | |
|---|---|---|
| Owner | One user | A site (team or organization) |
| Intended for | Drafts, personal working files, ad hoc sharing | Team documents, published content, intranet |
| Permissions | Set by the user, file by file | Set at site and library level, usually through groups |
| Structure | Folders | Sites, libraries, metadata, lists, pages |
| Lifecycle | Tied to the user account | Independent of any one person |
| Storage | A per-user allowance set by the license | A pooled allowance for the whole organization |
On storage, Microsoft’s SharePoint service description states the pooled SharePoint allowance for most plans as 1 TB plus 10 GB per license purchased. Check the service description for your plan, because frontline plans differ.
What OneDrive is for
OneDrive is the replacement for the “My Documents” folder and the home drive on a file server. It syncs to the user’s devices and makes sharing a single file quick.
It is the right place for:
- Work in progress that is not ready for others
- Personal notes and working copies
- A quick share with one or two people on a short task
It is the wrong place for anything the business needs after the author leaves. Microsoft documents what happens when a user account is deleted: by default the user’s manager is given access, the OneDrive is retained for 30 days, and it then sits in a recycle bin for 93 days before removal. The retention period can be changed by an administrator, and retention policies take precedence. Unless someone moves the files in that window, a department’s working documents can disappear with one departure.
What SharePoint is used for
Microsoft describes SharePoint as a tool for creating websites, publishing content and storing files. Three uses cover most organizations.
Team document libraries
A library is where a team’s files live, with version history, permissions by group and optional metadata such as document type or client. Metadata is the part file servers never had. It lets people filter and search instead of digging through folders.
Intranet
This is where the search term “SharePoint intranet examples” usually leads. Common building blocks, described here as patterns:
- A home site with company news and links to the tools people use daily
- An HR site with policies, forms and onboarding material
- A department site per function, with its own news and document library
- A project or client site template that is created the same way every time
- A knowledge base built from pages, so that answers are found by search
Lists and process tracking
A SharePoint list is a simple table: requests, assets, contracts, with columns and views. Lists are the usual data source for approval flows, which is why SharePoint design and Power Automate design are best done together.
Getting the site structure, permissions model and metadata right before content is moved in is the core of SharePoint consulting. Reorganizing a live intranet later is far more work than designing it first.
Where Microsoft Teams files live
Teams does not store files. It displays files that live in SharePoint and OneDrive. Microsoft’s documentation on Teams and SharePoint integration sets out the rules.
| Where the file was shared | Where it is stored |
|---|---|
| Standard channel | The team’s SharePoint site, in a folder named after the channel |
| Private channel | A separate SharePoint site for that channel |
| Shared channel | A separate SharePoint site for that channel |
| One-to-one or group chat | The sender’s OneDrive, in the Microsoft Teams Chat Files folder |
Two consequences matter for administrators.
First, every team you create also creates a SharePoint site, and every private or shared channel creates another. An organization with hundreds of teams has hundreds of sites whether or not anyone planned them.
Second, a file dropped into a chat is a OneDrive file owned by the sender. If a working group runs a project entirely in a group chat, its documents are scattered across personal OneDrives. Move ongoing work into a channel so the files land in SharePoint.
Permissions and external sharing
How permissions differ
In OneDrive the user decides who sees each file. In SharePoint, access is normally granted to groups at the site level, and for Teams-connected sites the team membership is the site membership. Microsoft recommends managing access through Teams for those sites.
The engineering advice is to grant access at the site or library level and avoid breaking inheritance on single folders and files. Item-level exceptions are hard to audit, and they are the usual reason nobody can answer the question of who has access to a document.
External sharing levels
Microsoft’s SharePoint admin center offers four organization-level settings for SharePoint and OneDrive:
| Setting | What it allows |
|---|---|
| Anyone | Links that work without sign-in |
| New and existing guests | Sharing with people who sign in or verify by code |
| Existing guests | Sharing only with guests already in your directory |
| Only people in your organization | No external sharing |
Two documented rules shape the design. The OneDrive setting can be more restrictive than the SharePoint setting, but not more permissive. And each site has its own setting, which must be the same as or more restrictive than the organization’s.
Separating internal-only and externally shared information
Those rules give you a clean pattern: decide per site, not per file.
- Internal-only sites. Finance, HR, management and engineering sites are set to “Only people in your organization”. Nobody can share from them by accident.
- External collaboration sites. A site per client, partner or project is set to allow guests. Everything in it is assumed to be visible to that outside party.
- OneDrive. Set it at or below the level your organization accepts for ad hoc sharing. Many organizations restrict it more than SharePoint, so that external sharing happens only from sites built for it.
Add link expiry and view-only defaults for “Anyone” links if you allow them at all, and review guest accounts on a schedule. Sensitivity labels and data loss prevention policies add another layer, and belong in a wider Microsoft 365 consulting engagement that covers identity and compliance as well as files.
Where to store what: a checklist
- A document others depend on is in a SharePoint library, not in a personal OneDrive
- Each department and each long-running project has a site with a named owner
- Ongoing work happens in Teams channels, not in group chats
- Internal-only sites have external sharing turned off at the site level
- External collaboration happens in sites created for that purpose
- The offboarding procedure includes moving the leaver’s OneDrive files before the retention period ends
- The OneDrive sharing setting is equal to or stricter than the SharePoint setting, by decision and not by default
- Someone reviews guest accounts and “Anyone” links on a schedule
Moving from a file server
The same split applies when you leave a file server. Home drives map to OneDrive. Department shares map to SharePoint sites and libraries. The work is in the mapping: deciding which shares become which sites, cleaning up permissions that grew over years, and handling long paths and file types that do not move cleanly.
A Microsoft 365 migration should start with an inventory of shares and their real owners, then a pilot with one department, then waves. Copying a file server into one giant library reproduces every old problem in a new place.
What to do next
Pick one department and answer two questions: which of its important documents sit in personal OneDrives, and which of its sites can share externally today. The answers usually justify a redesign on their own.
We design site structure, permissions and sharing policy, and carry out the move, through our SharePoint consulting and Microsoft 365 migration services. Projects start at $25,000 at a fixed price per phase. Goldenroz is independent and is not a Microsoft partner or reseller. Ongoing tenant administration is available under managed IT services, a monthly retainer quoted after an assessment.