Skip to main content

Microsoft 365 Group

A Microsoft 365 Group is the membership service behind modern collaboration in Microsoft 365. Create one and it provisions a connected set of resources: a SharePoint team site, an Outlook mailbox and calendar, a Planner plan, and optionally a Microsoft Teams team. Add a person to the group once and they get access to all of it; remove them and it all goes away. Owners manage membership and settings, while members collaborate in everything the group owns.
Related Features
Audience Targeting, Microsoft Entra Groups, SharePoint Groups, Site Members, Site Owners, Team Site

Common Use Cases

  • Department workspaces: one group gives a department its team site, shared inbox, calendar, and Teams space with a single membership list
  • Project teams: spin up a complete collaboration bundle per project, then archive or delete it when the project ends
  • Microsoft Teams backbone: every team in Microsoft Teams is backed by a Microsoft 365 Group, so governing groups governs Teams too
  • Shared mailbox and calendar: committees and working groups get a common inbox and calendar in Outlook without separate mailbox setup
  • Cross-functional initiatives: pull people from several departments into one membership list that grants the same access everywhere
  • Self-service workspaces: users can create their own collaboration spaces, with naming and expiration policies keeping growth under control

Benefits

  • One membership, every tool: add a person once and they get the site, mailbox, calendar, plan, and team together
  • Permissions stay in sync: SharePoint, Teams, Planner, and Outlook all read the same owner and member lists
  • Faster onboarding and offboarding: joining or leaving a team is one membership change, not five separate permission edits
  • Less admin overhead: owners manage their own membership, so routine access requests never need to reach IT
  • Clean lifecycle: expiration policies and the 30-day restore window make groups easy to retire and recover
  • Guest collaboration: external partners can be added as guests and see exactly what the group shares, nothing more

How It Works

  • The group is the permission object: SharePoint, Outlook, Planner, and Teams all hang off the group and read the same owner and member lists, so membership stays in sync everywhere
  • One object, many entry points: creating a team in Teams, a group in Outlook, a plan in Planner, or a SharePoint team site all create the same underlying Microsoft 365 Group
  • Owners and members: owners manage membership, settings, and connected resources, while members collaborate in everything the group owns
  • Site permissions through the group: members land in the connected site’s Members group with Edit rights by default, so access is managed through the group, not person by person
  • Public or private: public groups let anyone in the organization join and see content, while private groups require owner approval; the setting can be changed after creation
  • Guest support: people outside the organization can be added as members, subject to tenant guest settings

Limits and Nuances

  • Bundle in, bundle out: creating a group always provisions the site, mailbox, calendar, and Planner plan whether you need them all or not, and deleting a group deletes them all together
  • 30-day recovery window: deleted groups are recoverable for 30 days, then permanently gone; the window cannot be extended
  • Membership ceilings: up to 100 owners (keep at least two so nothing is orphaned), and each user can create up to 250 groups and belong to up to 7,000
  • Govern sprawl with three levers: restrict who can create groups, enforce a naming policy (prefixes, suffixes, blocked words, which needs Entra ID P1), and turn on expiration so inactive groups are renewed or removed
  • All-or-nothing permissions: members get Edit rights across the whole connected site, so do not use one group for content with mixed audiences
  • Guest access planning: guests see what members see within the group, and tenant, group, and sensitivity label settings all control whether they can be added
  • Renaming quirk: renaming a group changes its display name but not the SharePoint site URL, so choose the initial name carefully
  • Not every site needs a group: communication sites are never group-connected, and tightly controlled intranet sites usually work better without one

Common Questions About Microsoft 365 Groups

What is a Microsoft 365 Group in plain English?

It is a membership list with superpowers. Create a Microsoft 365 Group and you get a connected bundle of tools – a SharePoint team site for files, an Outlook mailbox and calendar, a Planner plan for tasks, and optionally a Microsoft Teams team for chat. Add someone to the group once and they can use all of it; there is no separate permission setup per app.

What happens when you delete a Microsoft 365 Group?

Everything connected to the group goes with it – the SharePoint site and its documents, the mailbox and calendar, the Planner plan, and the Teams team. Deleted groups sit in a soft-deleted state for 30 days, during which an admin (or the group owner) can restore the group and all its content. After 30 days the deletion is permanent, and that window cannot be extended.

What is the difference between group owners and members?

Owners run the group: they add and remove people, change settings, manage the connected site and team, and approve join requests for private groups. Members use everything the group owns – editing files, posting in Teams, updating Planner tasks – but cannot change membership or settings. A group supports up to 100 owners; the practical rule is to keep at least two so nothing gets orphaned when someone leaves.

Is every SharePoint site connected to a Microsoft 365 Group?

No. Team sites created through self-service, Outlook, or Microsoft Teams are group-connected, but communication sites – the type used for intranet homepages and department news – are not. Standalone team sites without a group also exist. Group connection is the right fit for collaborative workspaces; for published intranet content with a small set of authors and a wide audience, a communication site without a group is usually the better model.

How do you control Microsoft 365 Group sprawl?

Three levers, all standard Microsoft 365 features. Restrict who can create groups to a designated security group so new workspaces go through a light request process. Apply a naming policy (prefixes, suffixes, blocked words) so groups are identifiable at a glance. And turn on the expiration policy so inactive groups are flagged for renewal and cleaned up automatically instead of lingering forever. Greg Zelfond recommends putting these in place before opening self-service creation.

Can people outside the organization be added to a Microsoft 365 Group?

Yes, as guests. Guest members can work in the group’s files, Teams channels, and Planner, subject to the tenant’s external sharing and guest access settings. Admins can allow or block guest access tenant-wide or for individual groups, and sensitivity labels can enforce it automatically. Plan this deliberately: guests see what members see within the group, so keep externally shared groups scoped to the content guests genuinely need.