Microsoft 365 Groups is the membership and identity layer that connects the collaborative services in Microsoft 365. When a group is created, it provisions a shared set of resources across multiple Microsoft 365 services simultaneously: a SharePoint team site, a shared Outlook mailbox and calendar, a Microsoft Teams workspace, and a Planner board. All of these resources belong to the same group and share the same membership list.
Understanding Microsoft 365 Groups is essential for anyone managing a Microsoft 365 environment. Groups underpin how Teams channels work, how SharePoint team sites are created, how external collaboration is governed, and how licenses and permissions are managed at scale.
What a Microsoft 365 Group Actually Is
A Microsoft 365 Group is a membership object in Azure Active Directory (now called Microsoft Entra ID). It has a name, an email address, a list of members, a list of owners, and a set of associated resources.
The key distinction from a traditional distribution list or security group is what gets created alongside the group. When a Microsoft 365 Group is created, the following resources are provisioned automatically:
- SharePoint team site. A site collection connected to the group, with document libraries, lists, and pages available to all group members.
- Shared Outlook mailbox. A group email address that members can send to and receive from, with a shared inbox accessible to all members.
- Shared Outlook calendar. A calendar that all group members can view and edit, used for scheduling events that belong to the group.
- Microsoft Teams workspace. If Teams is enabled, a Teams team is associated with the group, giving members a channel-based communication space. The Teams files tab connects to the SharePoint document library.
- Planner board. A task board associated with the group, accessible from the Planner app and from within Teams.
- OneNote notebook. A shared notebook stored in the group's SharePoint site.
All of these resources are provisioned from a single group membership. Adding someone to the group gives them access to all of the connected resources at once. Removing them from the group revokes access to all of them.
How Microsoft 365 Groups Are Created
Groups are created through several entry points in Microsoft 365, and the entry point determines which resource appears most prominently to the creator.
Creating a team in Microsoft Teams creates a Microsoft 365 Group behind it. The Teams workspace is the visible surface; the group and its SharePoint site, shared mailbox, and Planner board are created automatically.
Creating a team site in SharePoint creates a Microsoft 365 Group behind it. The SharePoint site is the visible surface; the group's Teams workspace, shared mailbox, and Planner board are provisioned alongside it.
Creating a group in Outlook creates a Microsoft 365 Group with the shared mailbox as the visible surface. SharePoint, Teams, and Planner resources are provisioned alongside it.
Creating a plan in Planner creates a Microsoft 365 Group behind it. The Planner board is the visible surface.
This means that when users create a team, a team site, a group mailbox, or a plan, they are creating the same underlying object through different entry points. Each entry point provisions the same set of connected resources. This is a frequent source of confusion for administrators and users who do not realize that creating a team and creating a team site are the same operation at the group level.
Group Owners and Members
Every Microsoft 365 Group has at least one owner and one or more members. The distinction matters for administration.
Owners manage the group. They can add and remove members, change group settings, approve or reject membership requests if the group is configured for open membership, and delete the group. Owners receive notifications about group activity that members do not.
Members have access to all group resources. They can read and contribute to the SharePoint site, send and receive mail to the group address, add events to the shared calendar, and work in the Teams workspace. They cannot manage the group itself.
Best practice is to assign at least two owners to every group. A group with a single owner becomes unmanageable if that owner leaves the organization, because no one else has the administrative access to modify or clean up the group.
Group Types: Microsoft 365 Groups vs. Other Group Types
Microsoft 365 includes several group types. Understanding the differences prevents configuration errors.
Microsoft 365 Groups are the connected workspace groups described in this article. They provision SharePoint, Teams, Outlook, and Planner resources and are the right choice whenever collaboration is the goal.
Security groups are Microsoft Entra ID groups used for managing access to resources. They do not provision a SharePoint site, Teams workspace, or shared mailbox. Security groups are used for conditional access policies, application permissions, and license assignment.
Distribution lists (also called distribution groups) are email-only groups used for sending messages to a set of recipients. They do not provision any workspace resources and cannot be used for SharePoint permissions directly.
Mail-enabled security groups combine email delivery with security group functionality. They can be used for SharePoint permissions and can receive email, but they do not provision workspace resources like Microsoft 365 Groups do.
For SharePoint administrators, the relevant distinction is that only Microsoft 365 Groups provision a SharePoint team site automatically. Security groups can be added to SharePoint site permissions, but they do not create sites on their own.
Microsoft 365 Groups and SharePoint
The relationship between Microsoft 365 Groups and SharePoint team sites is direct and automatic. Every modern SharePoint team site is backed by a Microsoft 365 Group. The group's membership list is the site's membership list. Members of the group are site members. Owners of the group are site owners.
This integration has practical implications for SharePoint administrators:
Site creation creates a group. When a user creates a team site through SharePoint or Teams, a Microsoft 365 Group is created. If site creation is unrestricted, group creation is also unrestricted. Organizations that want to control group sprawl need to restrict site creation permissions.
Group deletion deletes the site. Deleting a Microsoft 365 Group deletes the connected SharePoint site along with all of its content. The deletion goes into a 30-day soft-delete period during which it can be restored, but the connection is permanent. Administrators who intend to delete only the group must first disconnect it from the site, which requires PowerShell.
Group membership drives site access. Because site access is derived from group membership, SharePoint site permissions for group-connected sites are managed through the group, not through the SharePoint site permissions interface. Changes made directly to the site's permission groups can create inconsistencies.
Guest access is controlled at the group level. Whether external users can be added to a group-connected site is governed by the group's guest settings, which can be overridden by tenant-level policies in the SharePoint Admin Center and Microsoft Entra ID.
Governance Considerations
Microsoft 365 Groups are powerful but create governance challenges when left unmanaged. The most common issues are group sprawl, orphaned groups, and uncontrolled external access.
Group sprawl. Because groups are created whenever a user creates a team, a team site, or a plan, the number of groups in a tenant grows quickly. Many of these groups represent completed projects or inactive teams that no one has cleaned up. The Microsoft 365 Admin Center provides tools to identify and act on inactive groups.
Orphaned groups. A group with no active owners cannot be managed by anyone except a Global Administrator. When the owner of a group leaves the organization, the group becomes effectively unmanaged. Policies that require a minimum number of owners and that reassign ownership when an owner's account is deactivated address this.
External access. Groups can be configured to allow guest members, which grants external users access to the group's SharePoint site, Teams workspace, and other resources. The default guest access settings in many tenants are more permissive than organizations realize. Reviewing and tightening guest access policies is one of the most impactful governance actions a SharePoint Administrator can take.
Expiration policies. Microsoft 365 supports group expiration policies that require group owners to actively renew groups at a defined interval. Groups that are not renewed are deleted. This is an effective mechanism for reducing sprawl, but it requires careful communication so that owners of active groups do not accidentally allow their groups to expire.
Naming policies. Microsoft Entra ID supports group naming policies that enforce a prefix or suffix on all group names. This helps administrators identify which department or function a group belongs to from its name, without having to look up each group individually.
Microsoft 365 Groups and Ultimate Forms
Ultimate Forms by Infowise builds on the SharePoint lists that sit inside group-connected team sites. When a department team or project group has a connected SharePoint site, the lists on that site can be extended with custom forms, automated actions, alerts, and print templates through Ultimate Forms.
Because Ultimate Forms runs inside the SharePoint tenant and reads from standard SharePoint group membership, process owners can configure form behavior and automation without stepping outside the Microsoft 365 environment. A group member who submits a request sees a form configured for their role. An owner who reviews the request sees the approver view. The group membership that Microsoft 365 Groups manages drives the form experience that Ultimate Forms delivers.
Summary
Microsoft 365 Groups are the identity and membership layer connecting SharePoint, Teams, Outlook, and Planner into a unified workspace. Every modern SharePoint team site is backed by a group. Every Teams team is backed by a group. Managing groups well is a prerequisite for managing the Microsoft 365 environment well.
For administrators, the governance priorities are preventing sprawl, ensuring every group has active owners, and controlling guest access to group resources.
For process owners and department managers, the practical implication is that the team or department's SharePoint site, Teams workspace, and shared calendar are all part of the same group. Access management is simpler than it appears because adding someone to the group gives them access to all of these resources at once.
For organizations building structured processes inside group-connected SharePoint sites, Ultimate Forms extends those lists with forms, automation, alerts, and reporting capabilities. Learn more at infowisesolutions.com.
Related reading:
- What Is SharePoint? A Complete Guide
- What Is a SharePoint Team Site and When Should You Use One?
- SharePoint Administrator: Roles and Responsibilities



