Microsoft 365 Groups vs Teams vs SharePoint sites

Microsoft 365 Groups, Microsoft Teams, and SharePoint sites are three related concepts that confuse users — and many admins. They sound like different products, but they're tightly intertwined under the hood. Knowing the relationships saves a lot of explanation.

What each is, simply

• A Microsoft 365 Group is a logical grouping of people in Entra ID, with associated resources: a shared mailbox, a SharePoint site, a OneNote notebook, a Planner plan, and (optionally) a Teams team.
• A Microsoft Teams team is the Teams-app surface for chat, meetings, and channels. Every team has a Microsoft 365 Group behind it.
• A SharePoint site is the web-based document and content surface. Every Microsoft 365 Group has a SharePoint site behind it.

So creating a Team creates a Group, which creates a SharePoint site. Three things, one provisioning chain.

The relationships visualised

Microsoft 365 Group
├── Members and Owners (Entra ID)
├── Shared mailbox (Exchange)
├── SharePoint team site
│   ├── Document libraries
│   ├── Pages
│   └── Lists
├── OneNote notebook
├── Planner plan
└── (optional) Microsoft Teams team
    ├── Channels
    │   └── Files (live in the SharePoint site)
    ├── Chats
    └── Meetings

When you upload a file to a Teams channel, it goes into a folder in the SharePoint site. When you @mention a group in Outlook, you're mentioning the same group whose members are in the Teams team.

Where the confusion comes from

A few common misconceptions:

• "I'll create a SharePoint site for the project" — fine, but you might also want a Team for chat. Better: create a Team and let the SharePoint site provision automatically.
• "I'll create a Team, then a separate Group for email" — no, the Team already has a Group. The Group's email address is right there.
• "I want to share a folder, so I'll create a Team" — overkill for one-shot file sharing. Just share the folder from your OneDrive.
• "Why does my team have a SharePoint site I never created?" — because Teams provisioned it. It's how files work.

When you'd create each without the others

• Just a Microsoft 365 Group — for a distribution-list-style collaboration with a shared mailbox and SharePoint files, but no Teams. Less common now; usually people want Teams too.
• Just a SharePoint communication site — for broadcast intranet content where no group of people "owns" it as a collaborative space. Communication sites are not group-connected.
• Just a Microsoft 365 Group without a Team — happens when you create a group from Outlook or the admin center; you can add Teams later.

Governance

Because creating a Team creates a Group creates a SharePoint site, governance flows through the Group:

• Naming policies apply at Group creation, so they apply to Teams and SharePoint sites automatically.
• Expiration policies delete the Group, which deletes the Team and the SharePoint site.
• Sensitivity labels can be applied at the Group level, affecting the Team's external sharing, guest access, and the SharePoint site's controls.
• Members and owners are managed at the Group level; changes flow to all the connected resources.

When to teach this

For end users, the abstraction usually doesn't matter — they create a Team, they get chat and files, they're happy. For admins, governance, owners, and anyone troubleshooting "why does this site exist?" — the underlying Group-Team-Site model is essential vocabulary.

A practical rule: if you find yourself thinking about a SharePoint team site without thinking about its Group, you're missing half the picture.