4.2. Manage Microsoft 365 Workloads
💡 First Principle: Each workload has its own unit of collaboration — a mailbox in Exchange, a team and its channels in Teams, a site in SharePoint — and each unit has its own permission model. Copilot reads across all of them, so workload administration is now also AI administration: every permission you set decides what Copilot can surface.
Why care? Workload settings are where data actually lives and where most access mistakes happen: a shared mailbox granted to the wrong group, a team with a guest who shouldn't be there, a site shared with everyone. Several exam objectives in this section mention Copilot directly — meeting transcription policy and preparing SharePoint and OneDrive for Copilot — because those are the workload settings with the biggest AI consequences.
The mental model is a permission comparison per workload:
| Workload | Container | Who controls access | Key permission levels |
|---|---|---|---|
| Exchange | Mailbox | Admins | Full Access, Send As, Send on Behalf |
| Teams | Team and channels | Team owners, admins | Owner, member, guest; private and shared channel membership |
| SharePoint | Site | Site owners and admins | Owners (Full Control), Members (Edit), Visitors (Read) |
⚠️ Common Misconception: "Full Access to a shared mailbox lets you send from it" is wrong. Full Access lets a user open and read the mailbox; sending needs Send As or Send on Behalf as well.