Microsoft 365 Groups are one of the most powerful yet most misunderstood features of the Microsoft 365 platform. For UK businesses that have adopted Microsoft 365 — which now represents the vast majority of SMEs — Groups offer a way to organise team collaboration, streamline communication, and manage shared resources all in one place. Yet many organisations either ignore Groups entirely or create them haphazardly, resulting in a disorganised mess that undermines rather than enhances productivity.
This guide explains what Microsoft 365 Groups are, how they differ from other Microsoft 365 features like distribution lists and shared mailboxes, and provides a step-by-step approach to setting them up effectively for your business. Whether you are an IT administrator managing the Microsoft 365 tenant or a business owner trying to understand what your IT team is talking about, this guide will give you the knowledge you need.
Getting Groups right from the start saves enormous amounts of time and frustration. Organisations that plan their Groups structure before creating them report significantly better adoption rates and fewer support tickets related to collaboration confusion.
What Are Microsoft 365 Groups?
A Microsoft 365 Group is a membership service that provides a shared set of resources for a group of people. When you create a Group, it automatically provisions a shared mailbox and calendar in Outlook, a shared document library in SharePoint, a team notebook in OneNote, a planning board in Planner, and optionally a Microsoft Teams channel. The key advantage is that all of these resources are connected through a single membership — when you add someone to the Group, they automatically gain access to all of the associated resources. When you remove them, all access is revoked instantly.
This is fundamentally different from the old approach of manually managing separate permissions for each resource. In the pre-Groups world, giving a new team member access to the department's shared mailbox, SharePoint site, calendar, and Teams channel required four separate administrative actions. With Groups, it requires one.
One of the most common points of confusion is the difference between Groups, distribution lists, and shared mailboxes. A distribution list simply forwards email to a set of recipients — it has no shared resources. A shared mailbox is a dedicated mailbox that multiple people can access, but it does not include collaboration tools like SharePoint or Planner. A Microsoft 365 Group includes email functionality similar to both, plus all the collaboration resources mentioned above. For most UK businesses, Groups should replace traditional distribution lists and, in many cases, shared mailboxes as well. However, shared mailboxes remain useful for specific scenarios such as info@ or sales@ addresses where you need a permanent, user-independent mailbox.
Planning Your Groups Structure
Before creating a single Group, you need a plan. The biggest mistake organisations make is allowing anyone to create Groups without any governance, which quickly leads to sprawl — dozens or hundreds of Groups with overlapping purposes, inconsistent naming, and abandoned resources that consume storage and create security risks.
Define Your Group Categories
Start by identifying the categories of Groups your organisation needs. Common categories include departmental Groups (Finance, Marketing, Operations, HR), project Groups (Client Project Alpha, Website Redesign 2025), functional Groups (Management Team, Health and Safety Committee), and external collaboration Groups (for working with clients or partners). Each category may have different requirements for privacy, membership policies, and lifecycle management.
Establish a Naming Convention
A consistent naming convention is essential for keeping Groups organised and discoverable. A good naming convention includes a prefix that identifies the category (DEPT for departments, PROJ for projects, FUNC for functional groups), followed by a descriptive name. For example: DEPT-Finance, PROJ-WebsiteRedesign2025, FUNC-HealthSafety. Microsoft 365 allows administrators to enforce naming policies automatically, including required prefixes and blocked words, which prevents users from creating Groups with inappropriate or confusing names.
| Group Type | Naming Convention | Privacy | Typical Membership | Lifecycle |
|---|---|---|---|---|
| Department | DEPT-[Name] | Private | All department staff | Permanent |
| Project | PROJ-[Name]-[Year] | Private | Project team members | Project duration + 90 days |
| Functional | FUNC-[Name] | Private | Committee/team members | Reviewed annually |
| Company-Wide | ALL-[Name] | Public | All employees | Permanent |
| External | EXT-[Client/Partner]-[Purpose] | Private | Internal + external guests | Engagement duration |
Step-by-Step Group Creation
With your plan in place, you can begin creating Groups. While end users can create Groups through Outlook, Teams, or SharePoint, the initial set of organisational Groups should be created by an administrator to ensure they follow your governance policies.
Creating a Group via the Microsoft 365 Admin Centre
Log into the Microsoft 365 Admin Centre at admin.microsoft.com. Navigate to Teams and Groups, then Active Teams and Groups. Click Add a Group and select Microsoft 365 as the group type. Enter the Group name following your naming convention, add a description that clearly explains the Group's purpose, set the privacy level (Private means only members can see content, Public means anyone in the organisation can see and join), assign at least one owner (ideally two, for redundancy), and add the initial members. The Group will be created with all associated resources within a few minutes.
Configuring Group Settings
After creating a Group, configure its settings to match your governance requirements. Key settings include whether external senders can email the Group, whether members can send as or send on behalf of the Group, whether the Group appears in the global address list, and the welcome message that new members receive. For Groups that will be used with Microsoft Teams, you should also create or connect a Teams channel at this stage.
Well-Governed Groups
- Consistent naming makes Groups easy to find
- Clear ownership ensures accountability
- Privacy settings protect sensitive information
- Lifecycle policies prevent abandoned Groups
- New starters quickly find relevant Groups
- Storage and licensing costs under control
- Compliance and audit requirements met
Ungoverned Groups Sprawl
- Duplicate Groups for the same purpose
- Abandoned Groups with orphaned data
- Sensitive data in Public Groups
- No naming convention — impossible to search
- New starters confused about which Group to use
- Storage costs escalating unchecked
- GDPR compliance risks from unmanaged data
Governance and Lifecycle Management
Creating Groups is only the beginning. Ongoing governance is essential to prevent sprawl and maintain a clean, useful collaboration environment. Microsoft 365 provides several built-in tools for Groups governance.
Expiration policies automatically delete Groups that are not renewed by their owners after a defined period — typically 180 or 365 days. This prevents abandoned Groups from accumulating. Before a Group expires, owners receive multiple notifications giving them the chance to renew it. If they do not, the Group is soft-deleted and can be recovered for 30 days.
Creation policies allow you to restrict who can create Groups. Rather than allowing all users to create Groups freely, you can limit creation to a specific security group — typically IT administrators and department heads. This dramatically reduces sprawl without preventing legitimate Groups from being created.
Classification labels allow you to tag Groups with sensitivity levels such as General, Confidential, or Highly Confidential. These labels can trigger specific security settings, such as preventing external sharing for Groups classified as Highly Confidential. For UK organisations subject to GDPR, this classification is particularly important for managing personal data appropriately.
Integrating Groups with Microsoft Teams
For most UK businesses, Microsoft Teams is now the primary collaboration hub, and every Teams channel is backed by a Microsoft 365 Group. Understanding this relationship is essential for managing both effectively. When you create a new team in Microsoft Teams, it automatically creates an underlying Microsoft 365 Group. Conversely, you can Team-enable an existing Group, which adds Teams channels and chat capabilities to the existing shared resources.
The best practice for most organisations is to create Groups through the Admin Centre with proper governance, then Team-enable those Groups that need real-time collaboration capabilities. This ensures that every Group follows your naming convention and governance policies, regardless of whether it was initiated from Teams, Outlook, or SharePoint.
For day-to-day use, most staff will interact with Groups through Teams rather than directly through the Admin Centre. They will post messages in channels, share files through the Files tab (which is actually the Group's SharePoint document library), and schedule meetings through the Group calendar. Training your staff to understand this relationship — that Teams channels, SharePoint libraries, and Outlook Groups are all views of the same underlying Group — dramatically reduces confusion and support requests.
Need Help Setting Up Microsoft 365 Groups?
Cloudswitched provides expert Microsoft 365 administration and consultancy for businesses across the United Kingdom. From initial tenant configuration to Groups governance, Teams deployment, and ongoing management, we ensure your Microsoft 365 environment is structured for productivity and security. Get in touch to optimise your Microsoft 365 setup.
GET IN TOUCH
