Overview of Microsoft 365 Groups for administrators
Microsoft 365 Groups is the foundational membership service that drives all teamwork across Microsoft 365. With Microsoft 365 Groups, you can give a group of people access to a collection of collaboration resources for those people to share. These resources include:
- A shared Outlook inbox
- A shared calendar
- A SharePoint document library
- A Planner
- A OneNote notebook
- Power BI
- Yammer (if the group was created from Yammer)
- A Team (if the group was created from Teams)
- Roadmap (if you have Project for the web)
With a Microsoft 365 group, you don't have to manually assign permissions to each of these resources, because adding people to the group automatically gives them the permissions they need to the tools that the group provides.
Any user can create a group unless you limit group creation to a specific set of people. Note that if you limit group creation, users who cannot create groups will not be able to create SharePoint sites, Planners, or teams. These services require the people creating them to be able to create a group. Users can still participate in group activities, such as creating tasks in Planner or using Teams chat, provided they are a member of the group.
Groups have the following roles:
- Owners - Group owners can add or remove members and have unique permissions like the ability to delete conversations from the shared inbox or change different settings about the group. Group owners can rename the group, update the description or picture and more.
- Members - Members can access everything in the group, but can't change group settings. By default group members can invite guests to join your group, though you can control that setting.
- Guests - Group guests are members who are from outside your organization.
Only global admins, user admins, and groups admins can create and manage groups in the Microsoft 365 admin center. You can't be a delegated admin (for example, a consultant who is an admin on behalf of).
As an administrator, you can:
- Specify who can create groups
- Create a naming policy for groups in your organization
- Choose which domain to use when creating a group
- Manage guest access to groups
- Recover a deleted group (within 30 days of deletion)
If you prefer a more automated way to manage the lifecycle of your Microsoft 365 groups, you can use expiration policies to expire groups at a specific time interval. The group's owners will get an email 30, 15 and 1 day before the group expiration that allows them to easily renew the group if it's still needed. See: Microsoft 365 group Expiration Policy.
You can administer your groups from the Microsoft 365 admin center or by using PowerShell.
If you have a lot of users, such as in a large corporation or enterprise, you may have many users who create groups for various purposes. We highly recommend that you review Plan for governance in Microsoft 365 groups for best practices.
The following limits apply to Microsoft 365 Groups:
|Owners per group||100|
|Groups a user can create||250|
|Groups an admin can create||Up to default tenant limit of 500K|
|Number of members||More than 1,000, though only 1,000 can access the Group conversations concurrently.
Users might notice delays when accessing the calendar and conversations in very large groups in Outlook.
|Number of Groups a user can be a member of||1,000|
|File storage||1 Terabyte + 10 GB per subscribed user + any additional storage purchased. You can purchase an unlimited amount of additional storage.|
|Group Mailbox size||50 GB|
The default maximum number of Microsoft 365 groups that an organization can have is 500,000, but can be increased by request. For more information on Microsoft 365 Groups limits, see Microsoft 365 Groups - Admin help.
Managing your Microsoft 365 groups is more effective when you have actionable information about groups usage. The Microsoft 365 admin center has a reporting tool that can let you see things such as storage use, how many active groups you have and even how your users are using the groups. See: Microsoft 365 Reports in the admin center for more information.
You can create sensitivity labels that the users in your organization can set when they create an Microsoft 365 group. With sensitivity labels, you can configure:
- Privacy (public or private)
- External users access
- Unmanaged device access
For example, you can create a label called Highly Confidential and specify that any group created with this label will be private and not allow external users. When users in your organization select this label during group creation, the group will be set to private and group members will be not be allowed to add external users to the group.
If you are currently using classification labels, they will no longer be available to users who create groups once sensitivity labels are enabled.
For information about creating, managing, and using sensitivity labels, see Use sensitivity labels to protect content in Microsoft Teams, Microsoft 365 groups, and SharePoint sites.
Which Microsoft 365 plans include groups?
Any Microsoft 365 subscription that has Exchange Online and SharePoint Online will support groups. That includes the Business Essentials and Business Premium plans, and the Enterprise E1, E3 and E5 plans. The group takes on the licensing of the person who creates the group (also known as the "organizer" of the group). As long as the organizer has the proper license for whatever features you want the group to have, that license will convey to the group.
For more details about Microsoft 365 service families and plans, see Microsoft 365 plan options.
If you have an Exchange-only plan you can still get the shared inbox and shared calendar features of groups in Outlook but you won't get the document library, Planner or any of the other capabilities.
Microsoft 365 groups work with Azure Active Directory (AAD). The groups features you get depends on which Azure Active Directory subscription you have, and what license(s) is assigned to the organizer of the group.
For all the groups features, if you have an Azure AD Premium subscription, users can join the group whether or not they have an AAD P1 license assigned to them. Licensing isn't enforced. Periodically we will generate usage reports that tell you which users are missing a license, and need one assigned to them to be compliant with the licensing requirements. For example, let's say a user doesn't have a license and they are added to a group where the naming policy is enforced. The report will flag for you that they need a license.