☕ SharePoint Tip #3 — OneDrive for Business and the Teams connection
Good morning! Here is your 15-minute SharePoint tip for today.
Day 3 | Week 1 — Platform Foundations
OneDrive for Business: everyone’s personal SharePoint library
OneDrive for Business is not a separate product — it is literally a personal SharePoint document library assigned to every user in your organisation. When your users sync files to "OneDrive," they are syncing to SharePoint.
OneDrive vs SharePoint libraries — when to use which
| Scenario | Use OneDrive | Use SharePoint library |
|---|---|---|
| Working drafts only you need | ✅ | |
| Files your whole team needs | ✅ | |
| Personal notes and scratch files | ✅ | |
| Shared project documents | ✅ | |
| Files you’ll eventually share with the team | Start here, move to SP |
The rule of thumb: personal = OneDrive, shared = SharePoint.
The sync client explained
The OneDrive sync client (the cloud icon in your system tray) lets users sync both OneDrive AND SharePoint libraries to their local computer. Files appear in Windows Explorer exactly like a file server — but they are stored in the cloud.
Files On-Demand is a key feature: files show as placeholders on your hard drive (taking no space) until you open them — then they download on the fly. A blue cloud icon means online-only; a green tick means downloaded locally.
What happens when Teams is involved
When a Microsoft Teams team is created, SharePoint automatically creates a team site and a document library. When users click the Files tab in a Teams channel, they are looking directly at that SharePoint library. Any file uploaded in Teams is stored in SharePoint — there is no separate Teams storage.
Try it today (5 minutes)
Open Teams, go to any channel, and click the Files tab. Then click Open in SharePoint (top toolbar). You’ll land in the SharePoint document library that powers that Teams channel. This is the same library your IT team manages in the SharePoint Admin Center.
As a Product Owner
Users often don’t realise that Teams files ARE SharePoint files. This is powerful — it means permissions, versioning, metadata, and search all apply to Teams files too. Surfacing this connection helps users understand why governance matters: what they do in Teams affects the SharePoint layer underneath.
See you tomorrow at 6:00 AM with Tip #4 — The SharePoint Permissions Model!