Microsoft 365 Foundations

Microsoft 365 isn’t a single app — it’s an ecosystem. Once you understand how the pieces fit together, every other tool starts making sense.

Microsoft 365 is the name Microsoft uses for its suite of cloud-based productivity tools — the modern version of what used to be called Office. The brand change matters because it reflects a real shift: Microsoft 365 isn’t just Word and Excel anymore. It’s a connected platform that includes apps for documents, email, calendar, file storage, team collaboration, automation, and AI.

Most people meet Microsoft 365 through one or two apps — usually Outlook for email, or Word and Excel for documents — and never realise there’s a whole platform sitting behind them. That’s how organisations end up paying for tools nobody uses. Once you understand the ecosystem, you can pick the right tool for each job instead of forcing everything through email.

The simplest way to think about Microsoft 365 is in three layers. Storage — where your files live (OneDrive for personal files, SharePoint for shared files). Apps — where you create and edit (Word, Excel, PowerPoint, Outlook, OneNote). Collaboration — where you work with other people (Teams for chat and meetings, SharePoint for shared workspaces). Everything else builds on top of those three layers.

When you’ll use this

• When you’re new to Microsoft 365 and want a simple map of what each app does.
• When you keep getting told ‘just save it in SharePoint’ and have no idea what that means.
• When you’re deciding whether your organisation needs a new tool — chances are Microsoft 365 already does it.

How to do it

1. Go to office.com and sign in with your work or school account.
2. Open the App launcher (the waffle icon, top-left) to see every tool included in your licence.
3. Click All apps to see the full list — most people only see the top six.
4. Open OneDrive to find your personal files and recent activity.
5. Open SharePoint to see your team sites and shared libraries.
6. Open Teams to see your chats, channels, and meetings — this is where most live collaboration happens.

Best practices

• Treat Microsoft 365 as an ecosystem, not separate apps. The apps are designed to work together — links, mentions, and shared files connect them.
• Start with one home base for team files. Either SharePoint or Teams (which uses SharePoint underneath). Don’t fragment.
• Use links and permissions instead of attachments and copies. The minute you copy a file, you’ve created a version-control problem.
• Learn search, sharing, and version history early. These three skills save you from 90% of common Microsoft 365 problems.

Common mistakes

• Treating it like the old Office suite. If you’re only using Word and Outlook, you’re using maybe 5% of what your organisation is paying for.
• Saving everything to your desktop. Local files don’t sync, don’t share, and disappear when your laptop dies.
• Emailing files as attachments. Two minutes later, three different versions exist. Send a link instead.

↑ Back to top ↑ Back to list

You can use Microsoft 365 in three places — browser, desktop, and mobile — and the right one depends on what you’re doing.

Most people pick one way of using Microsoft 365 and stick to it forever — usually whichever way IT set them up on day one. That’s a problem, because each access method is genuinely better for different things. The browser is best for quick tasks and shared devices. The desktop apps are best for serious editing and offline work. The mobile apps are best for on-the-go access and approvals.

Knowing all three matters because Microsoft 365 syncs everything across them. You can start a document at your desk, edit it on the train from your phone, and finish it at home in your browser — and it’s the same file the whole time. No emailing yourself attachments, no version chaos.

The trick is that every method works the same way: sign in with your work or school account, and your files, settings, and recent activity follow you. If you ever switch devices and feel lost, it’s almost always because you signed into the wrong account (work vs personal) or because OneDrive hasn’t finished syncing yet.

When you’ll use this

• When you switch between devices (office, home, phone) and want consistent access.
• When your IT setup feels limiting — the desktop apps may be hidden behind installer permissions.
• When you need to work from a borrowed or non-work computer (browser is your friend).

How to do it

1. Browser: Go to office.com, sign in. Works from anywhere with internet.
2. Desktop apps: Install Word, Excel, PowerPoint from the Microsoft 365 portal. Use these for heavy editing and full feature access.
3. Mobile apps: Install Microsoft 365, Outlook, Teams, OneDrive, and SharePoint from your app store.
4. Sign into all three with the same account so files and settings sync.
5. Use Recent in any Microsoft 365 app to pick up where you left off, regardless of device.

Best practices

• Browser apps are great for editing, but desktop apps have advanced features. Things like advanced charts in Excel, full PowerPoint animations, and complex Word formatting need the desktop version.
• Stay signed in with the same account across devices. The ‘where did my file go?’ moment is almost always a sign-in problem.
• Keep AutoSave on when working from OneDrive or SharePoint. Otherwise your latest version might only be on one device.
• If you work offline, sync back before sharing. Otherwise people are reading an outdated version.

Common mistakes

• Using only the desktop app and never the browser. The browser is faster for quick tasks and works on any device.
• Mixing personal and work accounts on mobile. Microsoft 365 mobile apps support both, but most issues come from being signed into the wrong one.
• Forgetting to sign out on shared devices. Especially in coworking spaces or borrowed computers.

↑ Back to top ↑ Back to list

The waffle icon is your shortcut to every Microsoft 365 app. Use it once and you’ll never go back to bookmarks.

The App launcher — the small waffle icon (nine dots in a square) at the top-left of every Microsoft 365 web app — is one of those features that’s hidden in plain sight. Most people never click it. Once they do, they realise they’ve been opening browser bookmarks the long way around for years.

The launcher shows every Microsoft 365 app you have access to in your licence. Click any tile and that app opens in a new tab. There’s also a search bar so you can find apps you don’t see — useful for tools like Microsoft Lists, Forms, Stream, and Power Automate that often hide under All apps.

Most importantly, the App launcher is consistent across every Microsoft 365 web app. Whether you’re in Outlook, OneDrive, SharePoint, or Word Online, the launcher is in the same place — so once you learn it, you can switch apps in two clicks from anywhere.

When you’ll use this

• When you need to quickly jump between apps without opening new tabs or searching.
• When you can’t remember which app does what (the launcher is also a memory aid).
• When you want to discover apps you didn’t know you had access to.

How to do it

1. In any Microsoft 365 web app, click the waffle icon (top-left, nine dots).
2. The launcher panel opens showing your most-used apps.
3. Click any app tile to open it in a new tab.
4. Click All apps to see the full list of tools in your licence.
5. Use the search field to find a specific app by name.
6. (Where supported) Pin frequently-used apps so they always appear at the top.

Best practices

• Use the App launcher instead of hunting through browser bookmarks. It’s faster and always up to date.
• Pin your top apps so they stay at the top of the launcher.
• If an app is missing, check with IT. It might be unlicensed, hidden by policy, or rolled out later.
• Use the Microsoft 365 home page (office.com) as your default tab — Recent files plus the launcher in one place.

Common mistakes

• Using browser bookmarks for every app. Bookmarks go stale; the launcher always reflects what you actually have access to.
• Assuming you don’t have an app. Many tools are hidden behind All apps — search before assuming.

↑ Back to top ↑ Back to list

Your account is the key to everything in Microsoft 365. A few minutes of setup now saves you from real pain later.

Your Microsoft 365 account is more than just an email address — it’s the identity that unlocks every app, file, and permission you have at work. When something goes wrong (lost phone, password reset, unexpected sign-out), it’s almost always an account problem, not an app problem.

There are two parts of your account most people never touch: your profile and your security settings. The profile is what other people see when they hover over your name in Teams or Outlook — your photo, role, and contact details. The security settings are things like multi-factor authentication (MFA), recovery options, and active sessions on different devices. Both deserve five minutes of your attention.

MFA is non-negotiable in 2026. Most organisations now require it. The Microsoft Authenticator app on your phone is the easiest method — open it, approve, you’re in. If you’re still receiving SMS codes, you’re using the slowest and least secure option. Switching takes two minutes and you’ll thank yourself the next time you sign in from a new device.

When you’ll use this

• When you start a new job or get a new device.
• When IT tells you to set up MFA.
• When you spot a suspicious sign-in or unexpected MFA prompt.
• When your phone breaks and you suddenly can’t sign in anywhere.

How to do it

1. Click your profile picture (top-right corner of any Microsoft 365 app).
2. Select View account or My account.
3. Open Security info to see and update your MFA methods.
4. Add the Microsoft Authenticator app if you haven’t already.
5. Set a recovery phone and recovery email.
6. Open Profile to update your name, photo, role, and contact details.
7. Review Sign-in activity periodically — flag anything you don’t recognise.

Best practices

• Use the Microsoft Authenticator app, not SMS. It’s faster, works internationally, and survives SIM swap attacks.
• Keep your profile current. A real photo and clear role title makes you findable in chat and meetings.
• Never approve an MFA prompt you didn’t trigger. If you didn’t just try to sign in, deny it and report it to IT.
• Use strong, unique passwords. A password manager is worth its weight in gold.
• Sign out of devices you no longer use. Your account page shows where you’re currently signed in.

Common mistakes

• Storing your password in your email signature or a sticky note. Yes, this still happens.
• Using a personal email as your recovery email. If your work account is compromised, the attacker may go after your personal email next.
• Approving MFA prompts without checking the location. The Authenticator app shows where the sign-in attempt is coming from for a reason.

↑ Back to top ↑ Back to list

OneDrive is your personal cloud storage — your work files, your drafts, your work-in-progress. Think of it as your work computer, in the cloud.

OneDrive is the part of Microsoft 365 designed for your personal work files. Every Microsoft 365 user gets their own OneDrive — usually 1TB or more — and only you have access to what’s inside (unless you choose to share something).

The simplest way to think about it: OneDrive is for you. SharePoint is for your team. If you’re working on a draft, taking notes from a meeting, or building something nobody else needs to see yet, that belongs in OneDrive. The moment it becomes a team file — something other people contribute to or rely on — it should move to SharePoint or a Teams channel.

OneDrive shows up in three places: as a web app at onedrive.com, as a folder on your computer (synced via the OneDrive app), and as a mobile app. All three show the same files. Edit on any device and the changes appear everywhere — usually within seconds. This is why personal drafts in OneDrive are so much safer than files saved to your desktop, which only exist on one machine.

When you’ll use this

• When you’re managing your own work files and need secure cloud storage.
• When you need a draft or work-in-progress that other people don’t need to see yet.
• When you want files to follow you across devices automatically.
• When you need to share a single file with someone (one-off, low-stakes).

How to do it

1. Open OneDrive from the App launcher (or the OneDrive icon in your system tray).
2. Create folders for your work areas — keep it simple, no deep hierarchies.
3. Upload or create a file directly in OneDrive (web, desktop, or mobile).
4. Use Share (rather than emailing) to send a link to someone.
5. Use Version history if you ever need to roll back a change.
6. When a file becomes a team file, move it to a SharePoint library or Teams channel.

Best practices

• Keep personal drafts in OneDrive, but move shared work to SharePoint. The rule of thumb: if more than one person works on it, it doesn’t belong here.
• Always share files as links, not attachments. Links keep everyone on the same version with full history.
• Use version history instead of saving local ‘final’ copies. OneDrive remembers every version automatically.
• Review who you’ve shared with periodically. Old sharing links can pile up over time.
• Don’t use OneDrive as a backup. If you delete a file, the recycle bin holds it for ~30 days, then it’s gone.

Common mistakes

• Using OneDrive as a team file store. It’s not designed for shared ownership and IT usually deletes a leaver’s OneDrive after 30 days.
• Sharing the same file with dozens of people. If that many people need access, it should be a SharePoint library, not a personal OneDrive file.
• Letting OneDrive sync everything to your laptop. Use Files On-Demand so files only download when you actually open them.

↑ Back to top ↑ Back to list

SharePoint is where your team’s work actually lives — files, knowledge, processes, and structure. Get this right and everything else in Microsoft 365 starts working better.

SharePoint is the part of Microsoft 365 most people use daily without ever realising it. Every time you open a file from Teams, save a document for your team, or visit your intranet, you’re using SharePoint underneath. It’s the platform Microsoft built to store, organise, and share content at the team and organisation level — and it’s the foundation for almost everything Microsoft 365 does with documents and team content.

The simplest way to think about SharePoint is this: OneDrive is for you, SharePoint is for your team. When you need a place where files, information, and processes live for a group of people — a department, a project team, or the whole organisation — that place is a SharePoint site. Each site has document libraries (where files live), pages (where information lives), and lists (where structured data lives).

This is also the reason SharePoint feels confusing to so many users: people meet it through Teams or through a shared link and never see the underlying structure. They get told ‘save it to SharePoint’ without ever being shown what SharePoint actually is. Once you understand it as the team-level storage and information layer for Microsoft 365, the rest of the platform makes a lot more sense.

Why this matters

SharePoint isn’t just a file store. It’s the platform that holds your team’s information together — and the platform Copilot reads from when it answers questions about your work. Three things make it different from regular file storage:

1. It’s structured. Files in SharePoint can be tagged with metadata (department, document type, status, owner) so they can be found by attribute, not just by where they sit in a folder. This is why SharePoint scales when shared drives don’t.

2. It’s connected. Every Microsoft Team has a SharePoint site behind it. Every channel has a folder in that site. Every shared file in Teams chat ends up here. SharePoint is the spine of team collaboration in Microsoft 365 — which is why a messy SharePoint creates a messy Teams.

3. It’s governed. Permissions, retention, ownership, and approval workflows are all built in. You can lock down what people see, manage how long files are kept, and route documents through review — without buying anything extra.

Key terms

Site

A SharePoint site is the home of a team or topic — like a contained workspace with files, pages, and lists. Most organisations have a site per team, department, or major project. Every Microsoft Team has a SharePoint site behind it, automatically.

Document Library

The place inside a site where files live. Think of it like a folder, but smarter — libraries can hold metadata, multiple views, version history, approvals, and permissions. A site can have many libraries.

List

A structured collection of items — like a spreadsheet, but smarter. Lists are perfect for trackers, registers, requests, or any data that has consistent fields.

Page

A web page inside the site. This is where intranets, news posts, team home pages, and policy hubs live.

Hub site

A site that connects multiple related sites together with shared navigation, branding, and search. Used by larger organisations to organise sites by department or function.

When you’ll use this

• Every time you open a file from a Teams channel — that file lives in SharePoint.
• When your team needs a shared place for ongoing files, policies, or reference material.
• When you want to find the latest version of a document — instead of three ‘FINAL_v2’ copies in different inboxes.
• When you need to share files with the right people without losing control of who has access.
• When you want your work to be findable by Copilot, search, or future colleagues.

How to do it

1. Open the App launcher (the waffle icon, top-left of any Microsoft 365 app) and select SharePoint.
2. You’ll land on the SharePoint home — this shows sites you follow and sites you visit often.
3. Use the search bar at the top to find a site, a person, or a file across all of SharePoint.
4. Click any site tile to open it — every team site has a navigation bar showing libraries, pages, and lists.
5. Once inside, open Documents (or whichever library you need) to access shared files.
6. Optional: select Sync in a library to make it appear in File Explorer or Finder, just like a local folder.

Best practices

• Use SharePoint as your team’s source of truth, not your inbox. If a file is shared and ongoing, it belongs in SharePoint — not in chat, not in email attachments, not in someone’s OneDrive.
• Prefer links over copies. Every time you copy a file, you create a version-control problem. SharePoint links keep everyone on the same version, with full history.
• Don’t fight the structure. Use libraries, metadata, and views the way they’re designed. Building deep folder hierarchies inside SharePoint is the most common mistake — and the one that creates the most pain later.
• Treat permissions as a design decision. Most ‘I can’t see this file’ problems come from permissions that were never planned. Decide early who owns each site and who can edit, comment, or just view.
• Name things in plain English. If a new starter can’t understand it on day one, the name has failed. ‘Documents,’ ‘Files,’ and ‘Stuff’ are not site or library names.

Common mistakes

• Treating SharePoint like a network drive. Deep folder structures, files with names like ‘Final_v3_REVIEWED,’ and one giant library called ‘Documents’ — this is the #1 cause of ‘SharePoint is awful.’ It’s not awful. It’s been forced to behave like a 1998 file server.
• Storing team files in personal OneDrive. When that person leaves, the files go with them. Team work belongs in SharePoint where ownership is shared.
• Adding sites for every project. Site sprawl is real. Most teams need one solid site, not ten half-finished ones.
• Ignoring metadata. Folders are not a filing system. Metadata is. Once a library has more than ~500 files, folders will fail you. Metadata won’t.

↑ Back to top ↑ Back to list

Teams is your collaboration hub — chat, meetings, calls, and team files in one place. But it’s also a SharePoint site in disguise.

Microsoft Teams is the place most people now do their daily work. Chat replaces a lot of internal email. Channels replace a lot of meetings. Meetings replace a lot of phone calls. Files in channels replace a lot of attachment-passing. For many organisations, Teams is the workspace and everything else orbits around it.

But here’s the thing: Teams is built on SharePoint. Every Microsoft Team has a SharePoint site behind it. Every channel has a folder in that site. Every file you upload to a channel ends up in SharePoint. Once you understand this, you stop being surprised by why your Teams files behave the way they do — they’re just SharePoint files dressed up with a chat interface.

This matters because most ‘Teams is broken’ moments are actually SharePoint or permissions issues showing up in a chat-shaped wrapper. When you understand that channels are SharePoint folders and chat files live in OneDrive, the whole thing starts to make sense.

Key terms

Team

A workspace for a group of people. Each Team has its own SharePoint site, channels, members, and settings.

Channel

A topic-based section inside a Team. Each channel has its own chat, files folder, and tabs. Use channels to keep work organised by topic, not by person.

Chat

Direct messages between you and one or more people. Chat files go to OneDrive (yours or theirs). Channel files go to SharePoint.

Tab

Anything pinned to the top of a channel — a file, page, app, or website. Useful for surfacing the most important resources.

Meeting

A scheduled or instant call with audio, video, screen sharing, and chat. Meetings can be tied to a channel (where the chat persists) or scheduled standalone.

When you’ll use this

• When your team collaborates daily and you want chat plus meetings plus files together.
• When you want to replace internal email for everyday back-and-forth.
• When you need a shared workspace for an ongoing project or department.
• When you need to host meetings that can be recorded, captioned, or transcribed.

How to do it

1. Open Teams (web at teams.microsoft.com, desktop, or mobile) and sign in.
2. Use Chat for quick 1:1 messages and small groups.
3. Use Teams in the left navigation to see your Teams (workspaces) and Channels (topics).
4. Open the Files tab in any channel to access the shared SharePoint folder.
5. Use Calendar to schedule meetings or join scheduled ones.
6. Use Activity (top-left bell icon) to see mentions, replies, and notifications in one place.

Best practices

• Use Teams for conversation; store the work in the SharePoint library behind it. Don’t let important files stay buried in chat.
• Create channels for ongoing topics, not for people. ‘Marketing Campaigns’ is a good channel. ‘Sarah’s Stuff’ is not.
• Don’t share important files only in chat. Surface them in the channel Files tab so they’re findable later.
• Keep meeting notes and decisions in the same Team. Reduces context switching and keeps history together.
• Use @mentions intentionally. Mentioning everyone for everything trains people to ignore notifications.

Common mistakes

• Using chat as a filing system. Chat files go to OneDrive and disappear when people leave. Channel files go to SharePoint and stay.
• Creating a Team for every project. Team sprawl is real. Most projects work better as a channel inside an existing Team.
• Ignoring channels you don’t visit often. Hide them rather than letting them pile up unread.

↑ Back to top ↑ Back to list

Outlook is for email and calendar. In a Teams-first world, that’s actually a more important job than it used to be.

Outlook is the Microsoft 365 app for email, calendar, and contacts. For decades it was the centre of work — every conversation, every meeting, every file passed through email. That’s changing. Internal chat moved to Teams. Internal files moved to SharePoint. What’s left for email is the stuff that belongs there: formal communication, external correspondence, scheduling, and anything that needs a clear paper trail.

This is actually good news. When email isn’t trying to do everything, it gets much easier to manage. The inbox becomes a place for things that genuinely require attention, not a graveyard of CCs and replied-to-all chains. The calendar becomes a real tool for managing time, not just a list of recurring meetings nobody actually needs.

Outlook also exists in three places like the rest of Microsoft 365: outlook.com (browser), the desktop app, and the mobile app. The mobile app is particularly good — schedule meetings, RSVP to invites, and respond to short emails from your phone in a fraction of the time desktop email takes.

When you’ll use this

• When you need formal or external communication.
• When you need to schedule meetings or check availability.
• When you need a documented paper trail (decisions, approvals, requests).
• When you’re working with people outside your organisation who don’t have Teams.

How to do it

1. Open Outlook (web, desktop, or mobile) and sign in.
2. Use Focused Inbox (if enabled) to separate priority email from notifications.
3. Set up rules for predictable email patterns (newsletters, alerts, automated reports).
4. Use Calendar to schedule meetings — pick a clear title, add agenda in the body.
5. Attach files using OneDrive links instead of copies whenever possible.
6. Use Search (top of the inbox) to find emails, attachments, and meeting threads quickly.

Best practices

• Use email for formal, external, or auditable communication. Use Teams for internal back-and-forth.
• Attach as OneDrive links to avoid version chaos. Especially when sending to multiple recipients.
• Keep your inbox tidy with light-touch rules. Heavy automation hides important emails.
• Use clear subject lines. Future-you, searching for an email in 6 months, will thank you.
• Block focus time in your calendar. If it’s not blocked, it gets booked.

Common mistakes

• Using email for fast back-and-forth. If a thread has 15 replies in 2 hours, it should have been a Teams chat or a 10-minute call.
• Sending attachments instead of links. Two minutes later, multiple versions exist.
• Letting your inbox become your task list. Use Microsoft To Do or Planner for actual tasks; let email be email.

↑ Back to top ↑ Back to list

Word, Excel, PowerPoint, OneNote — the apps everyone knows. They’ve quietly become the most powerful collaboration tools in Microsoft 365.

The Office apps — Word, Excel, PowerPoint, OneNote — are the ones almost everyone has used. What’s changed in the last decade is what these apps can do once they’re connected to OneDrive or SharePoint. Co-authoring, real-time editing, comments, version history, sharing — features that used to require Google Docs are now built into every Office app, as long as the file is in the cloud.

This is the single biggest shift most people miss. A Word document saved on your desktop is just a file. The same Word document saved to OneDrive or SharePoint is a collaborative workspace where multiple people can edit at once, leave comments, track changes, and roll back to any earlier version. Same app, completely different experience.

AutoSave is the feature that ties this together. When AutoSave is on (visible in the top-left corner of every Office app), changes save continuously to the cloud as you type. No more ‘I forgot to save and lost three hours of work.’ No more emailing yourself the latest version. The file in OneDrive is always the latest, and you can recover earlier versions from version history any time.

When you’ll use this

• When you create documents, spreadsheets, or presentations.
• When more than one person needs to edit the same file.
• When you want a record of who changed what (and when).
• When you need to share content for review without losing control of versions.

How to do it

1. Open a file in Word, Excel, PowerPoint, or OneNote — from OneDrive or SharePoint.
2. Confirm AutoSave is on (top-left corner of the window — should say AutoSave: On).
3. Click Share to invite others (with edit or comment access) and co-author the file.
4. Use Comments for feedback — they show in a side pane and can be replied to.
5. Use Track Changes (Word) for formal review where every edit needs to be visible.
6. Use Version History (File menu) to see and restore earlier versions.

Best practices

• Save to OneDrive or SharePoint first. Local files miss out on every collaboration feature.
• Use comments for feedback, not edits. Comments preserve the original author’s voice; edits change it.
• Use track changes when governance requires it. Policies, contracts, and procedures benefit from visible review.
• Avoid major formatting changes while others are editing. Pick a quiet moment for that.
• If a file is a long-term tracker, consider Lists instead of Excel. Lists scale better for shared, ongoing data.

Common mistakes

• Working in a downloaded copy and then emailing it back. The original file in SharePoint is still the source of truth — your edits won’t appear there.
• Saving multiple ‘Final’ versions. Use version history. The cloud remembers everything.
• Ignoring AutoSave warnings. If it says AutoSave is off, the file is local — and your changes aren’t going anywhere shared.

↑ Back to top ↑ Back to list

These three apps are the heart of file collaboration in Microsoft 365. The single most useful skill you can learn is knowing which one to use when.

If there’s one decision that fixes more Microsoft 365 problems than any other, it’s this: where should this file live? Pick wrong and you create version chaos, broken sharing, and ‘where did the file go?’ moments. Pick right and Microsoft 365 quietly does its job in the background.

The good news is the rule is simple. OneDrive is for you. SharePoint is for shared, structured team content. Teams is for conversation and collaboration around that content. If you can answer the question ‘who needs this file?’ you can answer where to save it.

What confuses people is that Teams files live in SharePoint behind the scenes. When you upload a file to a Teams channel, it’s stored in the SharePoint site that powers that Team — same file, different front door. Knowing this helps when something looks weird in Teams; the answer is usually to check the underlying SharePoint library.

Why this matters

Choosing the wrong location creates predictable problems:

Team files in OneDrive. The file owner leaves the organisation, IT deletes their OneDrive after 30 days, and the team’s history goes with it. This is one of the most common reasons companies lose institutional knowledge.

Personal drafts in a shared Team. Now everyone sees your half-baked work-in-progress, including the version where you wrote ‘this is a stupid idea’ as a placeholder.

Files emailed back and forth. Within an hour, multiple versions exist and nobody knows which is the real one.

Get this right at the start and you avoid all three.

Key terms

OneDrive

Your personal cloud storage. Like your work computer, but in the cloud and accessible from anywhere. Use for: drafts, personal work, 1:1 sharing.

SharePoint

Team-level shared storage with structure (libraries, metadata, permissions). Use for: team files, policies, processes, anything more than one person depends on.

Teams

The conversation and meeting layer. Files in a Teams channel are stored in SharePoint behind the scenes. Use for: chat, meetings, project workspaces.

When you’ll use this

• Every time you create or save a new file (the question becomes a habit).
• When migrating from a network drive or shared folder.
• When onboarding a new team member who needs to learn ‘where stuff lives.’
• When fixing a SharePoint mess (start by sorting what belongs where).

How to do it

1. Ask: Is this file just for me? If yes — OneDrive.
2. Ask: Is this for an ongoing team or department? If yes — SharePoint or Teams.
3. Ask: Are we actively collaborating on it with chat and meetings? If yes — a Teams channel (which puts the file in SharePoint anyway).
4. Ask: Is this for a specific project with a clear end date? If yes — a Teams channel or a project-specific SharePoint library.
5. When in doubt: SharePoint is almost always safer than OneDrive for anything not strictly personal.
6. Move files from OneDrive to SharePoint when they become team-critical (don’t wait for someone to leave).

Best practices

• Decide ‘personal vs shared’ before you create the file. It’s much easier than moving it later.
• Teams files live in SharePoint — knowing this helps you troubleshoot. If a Teams file is misbehaving, the fix is usually in the SharePoint library.
• Use consistent naming for Teams and libraries. So people can navigate quickly without thinking.
• Don’t use chat as a filing system. Chat files go to OneDrive and disappear when people leave. Channel files go to SharePoint and stay.
• Move files out of OneDrive when they become team-critical. Don’t wait until someone leaves.

Common mistakes

• Storing the team’s most important file in someone’s personal OneDrive. When that person changes roles or leaves, the file goes with them.
• Creating a SharePoint site for every project. Most projects fit better as a channel in an existing Team.
• Sending a file as an attachment to a chat message. Send a SharePoint link instead — same result, version-safe.

↑ Back to top ↑ Back to list

Knowing when to use chat vs email is one of the highest-leverage skills in modern Microsoft 365. Get this right and you save hours every week.

Most communication problems at work come from picking the wrong channel. A quick question becomes a 12-person email thread. A formal decision becomes a chat message that nobody can find later. A cross-team announcement gets buried in everyone’s CC list. Each channel — chat, email, channels, meetings — has a job, and the trick is knowing which job is which.

The rule of thumb: chat for fast back-and-forth, email for formal or external communication, channels for work that needs visibility, meetings for things that genuinely need a meeting. Each replaces the others in specific situations — chat replaces a lot of internal email, channels replace a lot of meetings, meetings replace a lot of phone calls.

The reason this matters more in 2026 than it did five years ago is that AI tools (including Copilot) work much better when communication is in the right place. A decision captured in a channel post is searchable forever. The same decision buried in a private chat is invisible. Choose the channel like future-you, or future-Copilot, will thank you.

When you’ll use this

• When you’re about to send an email to people inside your organisation (could it be a chat instead?).
• When you’re about to open a chat (does this need a paper trail? Should it be an email?).
• When deciding whether to send a message or schedule a meeting.
• When making decisions that the team will need to refer back to later.

How to do it

1. Quick question, fast answer: Teams chat (1:1 or small group).
2. Ongoing team work, multiple contributors: Teams channel post.
3. Formal communication or external recipients: Outlook email.
4. Sharing a file: Send a SharePoint or OneDrive link, regardless of channel.
5. Decision that needs to be findable later: Channel post (or email if external) — never private chat.
6. If a thread has 10+ replies: Move it to a meeting or a channel post with a clear summary.

Best practices

• Choose channels over private chat for work that needs visibility. Private chats die when people leave; channel posts persist.
• Avoid CC storms. Use @mentions and clear action requests instead of copying everyone.
• Summarise decisions in one place. A channel post, meeting notes, or an email — but only one place.
• Use subject lines and message titles that future-you can search for. ‘RE: stuff’ is searchable for nothing.
• Don’t reply-all to internal announcements with ‘thanks’ or ‘congrats’. Reactions exist for a reason.

Common mistakes

• Burying a decision in a private chat. Six months later, nobody can find it and you have to make the decision again.
• Using email for ongoing back-and-forth. Twenty replies in a day means you should have used chat or scheduled a 15-minute call.
• Forwarding a chat to email to ‘document it.’ Save the decision in a channel post or a SharePoint page instead.

↑ Back to top ↑ Back to list

A practical cheat sheet matching common tasks to the right Microsoft 365 app. Once you’ve internalised this, the right tool for each job becomes automatic.

Knowing what each Microsoft 365 app does is one thing. Knowing which app to reach for in any given moment is another. This is the muscle memory that separates someone who ‘uses Microsoft 365’ from someone who’s actually fluent in it. The good news: most everyday tasks have a clear best-fit app, and once you’ve made the choice three times it becomes automatic.

The pattern is always the same. Identify the task. Pick the app designed for that task. Save the file in the right place. Share with the right permission. Build small habits around this and most of the friction in your work day disappears.

Below is the practical cheat sheet — task on the left, best app on the right, with the rationale. Print this out, save it in your OneNote, share it with your team. It’s the single most useful page in Microsoft 365 training.

Key terms

Email someone formally

Outlook — has the formal record, calendar integration, and external recipient support.

Quick question to a colleague

Teams chat — fast, less formal, easier than email for back-and-forth.

Share a draft for review

OneDrive (yours) → share link via Teams or Outlook.

Store team policies

SharePoint document library — structured, searchable, governed.

Run a meeting

Teams meeting — recording, captions, screen share, notes.

Take meeting notes

OneNote (informal) or Loop (collaborative) or Word (formal).

Track a list of items

Microsoft Lists — better than Excel for shared, ongoing tracking.

Build a quick form

Microsoft Forms — questionnaires, surveys, RSVPs.

Automate a repetitive task

Power Automate — once you set it up, it runs forever.

Manage personal tasks

Microsoft To Do — your task list, synced across devices.

Manage team tasks

Planner — visual, shared, assignable.

Build a team workspace

Teams (which creates a SharePoint site behind the scenes).

Publish team news

SharePoint News — looks great, surfaces in Teams and email.

Quickly explain something visually

Loop component — embeds live in chat or email.

When you’ll use this

• Daily — every time you start a new task or piece of work.
• When training new team members on ‘how we work here.’
• When auditing how you use Microsoft 365 (you’ll find duplications).
• When deciding whether to add a new tool — chances are Microsoft 365 already does it.

Best practices

• Match the tool to the job. Resist the urge to do everything in email or Excel.
• Store content where it belongs from the start. Moving files later is harder than it looks.
• Use links, not attachments — every time. Even if it’s just one person.
• Build simple habits. Search first. Link, don’t attach. One source of truth.
• Don’t reinvent processes that already exist. If your team has a way of doing things, learn it before changing it.

Common mistakes

• Defaulting to email for everything. Email is good at some things and terrible at others. Use the right tool.
• Storing data in Excel that should be in Lists. Excel is for analysis. Lists is for ongoing trackers.
• Using Word for things Loop or Lists do better. Trackers, registers, checklists, structured data.

↑ Back to top ↑ Back to list