LevelUpWith

Explore / Microsoft 365 Support Pro: OneDrive and SharePoint / Lesson 1

Lesson 1: OneDrive, SharePoint and Teams Files on One Page

Learn what the user sees in OneDrive, SharePoint and Teams, what sits behind each view (sites, document libraries, the sync client and the tenant), and that this course is independent of Microsoft and does not reproduce its documentation.

Free to read, no account needed. Part of Microsoft 365 Support Pro: OneDrive and SharePoint.

By the end of this level you'll be able to

  • Draw a one-page map that links a user's OneDrive, a SharePoint site library and a Teams channel's Files tab to the storage behind each
  • Explain to a user in plain language why the same file can show up in File Explorer, the browser and Teams
  • State which parts of the service support can change for one user and which are set for the whole tenant

Why start with a map

Most files tickets sound different and turn out the same: "my file vanished from Teams", "Explorer shows a red cross", "my colleague can't open the link". The fix nearly always starts with one question: where does this file really live? If you can answer that within a minute, you know which screen to open, who owns the content and whose settings apply.

This level gives you that map. Before we start, a note: this course is independent. It has no link to Microsoft and no endorsement from Microsoft, and it does not reproduce Microsoft's documentation. Product names belong to their owners. Admin screens change, so every detail here was checked against Microsoft's public documentation as of November 2026. Check it again when your console looks different.

Three windows, one storage system

A user sees three places for files. Behind all three is SharePoint in Microsoft 365.

WHAT THE USER SEES                 WHAT SITS BEHIND IT
-----------------------------      ----------------------------------------------
OneDrive ("My files")          ->  A personal SharePoint site owned by one user
                                   https://contoso-my.sharepoint.com/personal/anna_contoso_com

SharePoint site ("Finance")    ->  A SharePoint site with one or more document libraries
                                   https://contoso.sharepoint.com/sites/Finance

Teams > channel > Files tab    ->  Standard channel: a FOLDER in the team's parent site's
                                     default library (Documents / "Shared Documents")
                                   Private or shared channel: that channel's OWN site

Teams 1:1 or group chat file   ->  The SENDER's OneDrive, folder "Microsoft Teams Chat Files",
                                   shared only with the people in the chat

File Explorer / Finder         ->  The OneDrive sync client, which keeps a local copy of
                                   any of the above in step with the cloud

An analogy for help desk staff: SharePoint is the file server. A site is a share, a document library is a top-level folder on that share, and the sync client is a mapped drive that also works offline. Teams and the OneDrive web app don't store anything. They are front ends that open the same share.

Walkthrough: read the URL first

The quickest read-only check you have is the address bar. Ask the user to open the file in the browser, or to choose Open in SharePoint from the Teams Files tab, and read the URL to you.

# Case 1: a personal OneDrive
https://contoso-my.sharepoint.com/personal/anna_smith_contoso_com/Documents/Budget.xlsx
#                 ^^^ "-my" host = OneDrive   ^^^ the owner's sign-in name, with . and @ turned into _
# -> Anna owns it. If Anna leaves, this file's fate follows her OneDrive.

# Case 2: a team's standard channel
https://contoso.sharepoint.com/sites/Marketing/Shared%20Documents/Launch/Plan.docx
#                              ^^^ parent site  ^^^ default library ^^^ folder = channel "Launch"
# -> Belongs to the team, not to a person. Team owners and members reach it.

# Case 3: a private channel
https://contoso.sharepoint.com/sites/Marketing-CompeteAnalysis/Shared%20Documents/...
#                              ^^^ a separate channel site, named after team + channel
# -> Only members of that channel reach it, even if they are owners of the parent team.

Gotcha: a user says "I put it in Teams" but they dropped it into a chat. That file is in their own OneDrive, not the team site. Delete their account and the file goes with it. Always ask: "Was it a channel or a chat?"

Gotcha: the OneDrive URL is usually created the first time the user opens OneDrive, unless it was pre-provisioned. A new starter with "no OneDrive" may simply not have opened it yet.

Explaining it to a user

Users find it strange that the same file shows up in three places. A script that works:

"There's only one copy of your file, and it's stored online in SharePoint.
 Teams, the browser and File Explorer are three different windows onto that copy.
 Change it in one window and the others pick up the change once it syncs.
 That's why deleting it in Explorer also deletes it for the team."

The last sentence is the one that saves tickets. A synced folder is not a backup. It is a live two-way link.

In Explorer, the sync client shows each file's state. With Files On-Demand, a blue cloud means online-only: the file takes up no local disk space and can't be opened offline. A user who is on a train with a folder full of cloud icons isn't looking at a fault. Those files were never downloaded. Later levels cover each sync icon in detail.

What you can change for one user, and what is set for everyone

Some settings live on a user, a device or a single site. Others are tenant-wide policy that you read and explain but do not change. One rule matters most here: a site's sharing setting can never be more permissive than the organisation-level setting. A site can be as strict as the organisation setting or stricter, never looser.

USUALLY CHANGEABLE FOR ONE USER / SITE         SET FOR THE WHOLE TENANT (read, explain, escalate)
--------------------------------------         ---------------------------------------------------
Sync client on their PC (install, sign-in,     Organisation-level external sharing ceiling
  which libraries they sync)
Their membership of a team or site             Default OneDrive storage for new users
Storage for one specific OneDrive or site      (1 TB on most plans; admins can raise it,
  (within what the plan allows)                 depending on plan and licence count)
A site's own sharing level, at or below        Default sharing link type for the tenant
  the tenant ceiling

Best practice: when a user says "sharing is blocked", don't start by changing anything. Check whether the block comes from the site or from the tenant. If it comes from the tenant, your job is to explain the policy and, if the business case is real, escalate. Policy design is not first or second line work.

Trade-off: you will be tempted to add a user straight to a Teams-connected site in SharePoint to save time. It works on a parent site, but Teams is the recommended place to manage that membership. On private and shared channel sites you can't do it at all, because their permissions come from the channel.

Key takeaways

  • OneDrive, SharePoint and Teams all store files in SharePoint sites. Teams and the OneDrive app are front ends.
  • A standard channel is a folder in the team's parent site library. Private and shared channels each have their own site.
  • Chat files live in the sender's OneDrive under Microsoft Teams Chat Files.
  • The URL tells you the owner: -my.sharepoint.com/personal/... is a person's OneDrive, and /sites/... is a shared site.
  • The sync client mirrors the cloud copy. A blue cloud means online-only, and the file can't be opened offline.
  • Site sharing can be as strict as the tenant or stricter, never looser. Read tenant policy, explain it, and escalate it. Don't redesign it.
  • This course is independent of Microsoft and does not reproduce its documentation.

A 6-question knowledge check follows this lesson in the app, free and without an account.

More like this

  • Microsoft 365 Support Pro: Copilot for End Users

    Learn to work out which Copilot a user actually has, and to fix the everyday Copilot tickets: missing buttons, licence and sign-in problems, files Copilot can'…

    Course · Microsoft · Suite Support Pro: Configure and Fix · Expert · 36 levels · 4 free · Professionally curated by levelupwith.com

  • Microsoft 365 Support Pro: Teams Meetings and Chat

    Resolve the Microsoft Teams faults users actually raise, including sign-in and cache problems, audio, video and screen sharing, guest access, missing recording…

    Course · Microsoft · Suite Support Pro: Configure and Fix · Expert · 44 levels · 4 free · Professionally curated by levelupwith.com

  • Microsoft Azure Fundamentals (AZ-900) Exam Prep

    Learn to pick the cloud model, service type or Azure service that fits a scenario and explain why the alternatives do not, across every skill in the 20 July 20…

    Exam prep · AZ-900 · Cloud & Compute · Capable · 17 levels · 4 free · Professionally curated by levelupwith.com

  • Microsoft Azure Administrator (AZ-104) Exam Prep

    Work through every bullet of the AZ-104 skills measured as of April 17, 2026, learning each task in the Azure portal, Azure CLI, PowerShell, and ARM templates…

    Exam prep · AZ-104 · Cloud & Compute · Expert · 60 levels · 4 free · Professionally curated by levelupwith.com

  • Support Pro: Helping Users Move to Microsoft 365

    Help users get through a move from Google Workspace to Microsoft 365, from the week before cutover to the first tickets afterwards. You will learn what moves a…

    Course · Microsoft · Suite Support Pro: Configure and Fix · Expert · 40 levels · 4 free · Professionally curated by levelupwith.com

  • Microsoft 365 Support Pro: Exchange Online and Outlook

    Use the Exchange admin centre and read-only PowerShell checks to set up shared mailboxes, delegation, calendars and rooms. Then work through Outlook faults, me…

    Course · Microsoft · Suite Support Pro: Configure and Fix · Expert · 40 levels · 4 free · Professionally curated by levelupwith.com