Microsoft 365 Finally Makes Sense: How SharePoint, Teams, OneDrive and Copilot Work Together

You open the document in Teams. It is stored in SharePoint. You find it through OneDrive. Then you ask Copilot a question about it.

No wonder Microsoft 365 can feel confusing. You are often seeing different ways into connected information, alongside tools that hold different parts of the work. Choosing the right starting point makes a difference.

SharePoint gives shared content a home. Teams brings people and conversations together. OneDrive supports individual work and access to files. The Office apps help you create the deliverables. Copilot can help you work with the information available to it.

This is the map I wish more people were given before being told to “use Microsoft 365”. Here is what belongs where, which Copilot experience to start with, and how the pieces fit into a normal working day.

Why SharePoint matters so much in Microsoft 365

SharePoint is a foundation for shared documents, internal publishing and organisational knowledge. A team can use its libraries to manage project documents, its pages to explain a process and its lists to track structured information. Teams channels also rely on SharePoint for their files.

That does not mean every piece of Microsoft 365 lives in SharePoint. Email and calendars, Teams conversations and other services have their own storage and access arrangements. Microsoft 365 brings those sources into connected experiences, and Copilot can use authorised context where the product and licence support it.

The practical implication matters more than the architecture label: the project document needs a reliable home, the team needs to know where that home is, and the owner needs to keep it accurate. Copilot does not remove those jobs.

For the foundations, read what SharePoint is and how its sites, libraries, lists and pages work.

What each Microsoft 365 tool is for

You do not need to use every app in every process. Choose the smallest set that gives the work a clear home, an accountable owner and an understandable way to get it done.

The same document can appear in several apps

Opening a SharePoint file through Teams does not create another copy. Accessing a shared library through the OneDrive app does not turn its documents into your personal files. The interface you use and the underlying storage location are different things.

New files uploaded to Teams channels are stored in SharePoint. New uploads in one-to-one or group chats normally go to the uploader’s OneDrive. If you share an existing file’s link, it stays in its existing location. Private and shared channels have separate SharePoint sites from the parent team’s standard channels.

That is why “I put it in Teams” is not always a complete answer to “Where is the file?” Microsoft explains the details in its Teams file storage guidance.

Use the SharePoint vs OneDrive decision guide when choosing a long-term home.

Which Copilot should I use? Start with the job

A Copilot button is an entry point, not a promise that every experience has the same sources, tools or permissions. Start with the outcome and the information needed to produce it.

The labels and interface continue to change. Your organisation’s licences, policies and rollout determine which options you see. These are starting points for choosing a workflow, rather than six completely separate products with identical availability.

1. Copilot Chat: ask across the context available to you

Use Chat when you need to explore a question, summarise supplied information or pull together relevant context. Where licensed work-data access is available, it can use authorised work sources as well as content you provide. A basic chat experience is not automatically searching your whole organisation.

Check the sources shown in the answer. If the wrong project or an old document appears, specify the file or link you actually mean. Work-data access and controls depend on your licence and settings; Microsoft explains the differences between Copilot Chat experiences.

Using the project plan and these two updates, prepare a short status brief. Separate confirmed progress, blockers, decisions needed and missing information. Cite the source for each factual statement.

2. Copilot in the apps: stay close to the deliverable

If the job is improving a report, start with the report in Word. If it is analysing a workbook, start in Excel. If it is responding to an email thread, the relevant Outlook experience may be the useful starting point.

You are asking Copilot to help within the context of the work you have open. Supported actions differ across apps and licences. Check whether the result is a suggested answer, a draft or an actual edit to the file.

Rewrite this report section for a non-technical executive audience. Keep the facts, dates and caveats. Flag ambiguous statements instead of filling the gaps.

For more examples, see 20 practical Copilot use cases with prompts.

3. Copilot in SharePoint: work where shared content lives

This is useful when the task is centred on a SharePoint site or library: understanding content, drafting material or organising documents with supported actions.

For example, you might request a view using existing columns, or review suggested metadata columns through Create autofill columns. Check the proposed action and generated values before relying on them. A suggested status is not an approval decision.

Microsoft began general availability rollout on 30 September 2026. Everyday capabilities require an active Microsoft 365 Copilot licence. Advanced work and site-wide real-time Autofill can additionally require usage-based billing and Copilot Credits. See the current prerequisites and controls.

Using this library’s existing Business Area and Content Status columns, create a view of Current documents grouped by Business Area. Show the proposed filters so I can check them.

A prompt needs the columns and supported capability to exist. My document library clean-up walkthrough shows how to prepare the content and review the results.

4. Copilot Notebooks: bring a purposeful set of sources together

A notebook is useful when you want an ongoing workspace around selected materials: a project brief, research documents, meeting notes and working outputs. It helps you return to a defined collection rather than repeatedly rebuilding the context.

Reference types and limits depend on the plan. Check what is included, whether the sources are current, and whether a research feature is bringing in external information. Do not assume every notebook action uses only your original files.

Across the sources in this notebook, identify agreed requirements, conflicting statements and unanswered questions. Cite the relevant source for each point. Do not resolve a conflict by guessing.

Microsoft’s comparison of Loop, Copilot Pages and Notebooks helps separate collaborative working content from a source-focused AI workspace.

5. Agents: make the purpose and boundaries explicit

An agent is useful when a focused business need will come up repeatedly. An onboarding helper, for example, needs agreed source material, clear instructions, a defined audience and somebody responsible for maintaining it.

“Answer questions about HR” is a broad ambition. “Help staff find the current leave procedure, cite it and direct unresolved questions to the People team” is a more useful scope.

Different agent types support different knowledge sources and actions. Access to an agent and access to the underlying information are separate things to review. An agent is not a way to bypass permissions or turn an old policy into an authoritative answer.

Microsoft has announced changes to SharePoint agent creation beginning in mid-November 2026, including the transition to Copilot Agent Builder. Check the current transition guidance before following an older setup tutorial.

6. Cowork: delegate a task with several steps

Cowork is for work that needs more than a short answer: examining sources, developing an output and working through a sequence of supported actions. Give it a specific outcome and clear boundaries.

Microsoft’s prerequisites include an active Microsoft 365 Copilot licence, Cowork availability and usage-based billing enabled. Confirm those conditions with your organisation rather than assuming a visible Copilot chat box includes Cowork. See Microsoft’s Cowork getting-started guide.

Prepare a draft project update using these approved sources. First show your plan and identify missing information. Draft the report and a covering email for my review. Ask before sending, sharing or changing source files.

Delegation still needs review. Check the output, sources, proposed changes and any actions requiring approval. A completed sequence is not the same as a correct business decision.

A normal working example: prepare the project update

Here is how the pieces can work together without making six copies of the same report.

• Start with the source: keep the agreed project plan and deliverables in the project’s SharePoint library.
• Collect the context: review the relevant Teams discussion and available meeting transcript, plus the latest approved updates.
• Choose the Copilot entry point: use Chat for a brief, a Notebook for a recurring source collection, or supported multistep work for a larger draft task.
• Create the deliverable: draft and refine the update in Word, using the specified sources.
• Review: check figures, dates, decisions and citations with the responsible people.
• Save the agreed copy: keep the team-owned document in the appropriate SharePoint library and use version history.
• Communicate: share its link in Teams or Outlook, with appropriate access.
• Track the work: record actions in the agreed Planner plan or other task system; confirm owners and deadlines.

Those tools have different roles. The meeting is where the discussion happens. The task system tracks the action. The library holds the maintained document. Copilot helps you work across the relevant information; it does not replace those responsibilities.

What makes this work—and what breaks it

The connected experience is only useful when the information behind it is understandable and appropriately accessible.

• One agreed working copy: avoid competing versions in chat attachments, email and personal folders.
• Useful metadata: describe documents so people can recognise and filter them.
• Named owners: somebody must decide what is current and maintain it.
• Appropriate access: review oversharing rather than assuming AI creates the permission problem.
• Verification: use citations and source checks for important answers.

SharePoint permissions are one part of the wider access model. Copilot respects the access controls of the sources it uses; clear organisation makes those sources easier to manage, but does not guarantee a correct answer.

For the underlying design, read how SharePoint hubs, sites and libraries fit together and eight practical ways to organise documents.

Common questions

Is all Microsoft 365 information stored in SharePoint?
No. SharePoint is central to shared content and Teams channel files, but other Microsoft 365 services hold other kinds of information. Connected access does not mean one storage location.

Does a Microsoft 365 subscription include every Copilot feature?
No. Access varies by subscription, Copilot licence, organisation settings and the experience. Some advanced capabilities also require usage-based billing.

Should I start every task in Copilot Chat?
No. Start where the relevant context and action are available: in a document for document work, in SharePoint for a library task, or in a suitable cross-source experience for a broader question.

Will a Copilot answer automatically become an approved document?
No. Review it, follow the organisation’s approval process and save the agreed result in the right place.

Start with one connected workflow

You do not need another list of every Microsoft product. Choose one piece of work, identify its sources and owner, then decide where Copilot can help.

If your project update needs three people to explain which file is current, start with the files. If the sources are reliable but preparing the brief takes hours, try a focused Copilot workflow.

The tools become much easier to understand when each one has a job.

SharePoint, simply sorted.

Sources and availability

• Microsoft Copilot overview and licensing distinctions
• What information Copilot uses
• Copilot Chat inside Microsoft 365 apps
• Create autofill columns in SharePoint

Feature details checked 7 November 2026. This article focuses on work and school Microsoft 365 environments. Product names, interfaces, licensing and availability can change.