Identify the core features and objects of Microsoft 365 services
Exchange, SharePoint, and Teams Objects
Choose the correct collaboration object and workload admin surface for email, content, and teamwork scenarios.
What you need to know
- A mailbox stores and receives email; a distribution group distributes messages to members.
- A SharePoint site contains libraries; a library contains folders and files.
- A team is a collaboration boundary, channels organize conversations and work, and Teams policies control user capabilities.
Objects and administrative surfaces
- Mailboxes and distribution groups — Exchange admin center.
- Sites — SharePoint admin center; libraries, folders, sharing, and many permissions — the SharePoint site experience.
- Teams, channels, and Teams policies — Teams admin center, with some membership managed in Teams or through the connected Microsoft 365 group.
How it works
- Teams-connected sites store channel files in SharePoint. A new channel is not a replacement for a mailbox or distribution group.
- SharePoint permission inheritance normally flows from site to library, folder, and item until unique permissions are introduced.
When to use it
- Use a distribution group for email-only broadcast, a team for persistent collaboration, and a SharePoint library for managed document storage.
- Use a workload-specific admin center when the task concerns that workload’s objects or policies.
Security and governance implications
- Prefer group-based permissions and default Owners, Members, and Visitors roles over many direct item grants.
- Private and shared Teams channels have distinct membership and associated SharePoint storage considerations.
Troubleshooting signals
- Trace the object hierarchy and membership first: group/team, site, library, folder, then file.
- Check the workload policy and the user’s effective membership rather than assuming tenant settings are the cause.
Exam traps
- A distribution group delivers email but does not provide a shared workspace.
- A library is inside a site; it is not a tenant-level object equivalent to a site.
Key takeaways
- Email → Exchange; documents → SharePoint; collaboration and meetings → Teams.
- Choose the smallest correct object without confusing storage, messaging, and access boundaries.
Related objectives
- D1.1.c
- D1.1.d
- D1.1.e
- D1.1.f