New Microsoft 365 Group Creation Experience: What’s Changed and Why It Matters

Microsoft has rolled out a redesigned group creation experience in My Groups, giving group owners significantly more control during setup, without needing to involve an administrator after the fact.

It’s a small but meaningful change for organisations that rely on Microsoft 365 groups for collaboration, shared mailboxes, and team communication.

What’s new?

Previously, creating a Microsoft 365 group through My Groups was a fairly basic process. You’d set a name and description, and most of the useful configuration (email settings, security options, visibility controls) had to be done afterwards by an admin.

The updated experience lets group owners configure all of this at the point of creation:

• •Group usage guidelines, email alias, and sensitivity labels
• •Exchange settings such as welcome emails, subscribing members to conversations, and showing the group mailbox and calendar in Outlook
• •Controls for who can send email to the group, including hiding it from the global address list and allowing or blocking external senders
• •Enabling security group functionality when needed

This means groups are set up correctly from day one, rather than requiring follow-up configuration.

Why this matters more than it sounds

Group sprawl is one of the most common Microsoft 365 management headaches. Groups get created quickly, often with default settings that don’t match the organisation’s policies, and then they sit there, misconfigured, until someone notices.

Common issues I see in client environments include:

• •Groups open to external email by default when they shouldn’t be
• •Missing sensitivity labels, creating compliance gaps
• •Group mailboxes and calendars not visible in Outlook because settings weren’t configured
• •Members not subscribed to conversations, so messages go unseen

By giving group owners these controls upfront, Microsoft is reducing the gap between “group created” and “group properly configured.”

What this means for administrators

For IT administrators and managed service providers, this is a welcome change:

• •Fewer support tickets for post-creation group configuration
• •Better alignment with organisational policies from the start
• •Sensitivity labels and usage guidelines applied consistently
• •Less cleanup work during periodic reviews

It also reinforces the importance of having group creation policies, naming conventions, and sensitivity labels properly configured at the tenant level, because users will now see and interact with these settings directly.

Availability

This is a General Availability release, rolling out to all tenants. If you haven’t seen it yet, it should appear in your My Groups experience shortly.

A practical recommendation

If your organisation uses Microsoft 365 groups regularly, now is a good time to:

• •Review your group creation policies and naming conventions
• •Ensure sensitivity labels are published and available to users
• •Update any internal guidance or documentation for group owners
• •Check that usage guidelines are configured in your tenant

Getting these foundations right means the new self-service experience works in your favour, rather than giving users more rope to create misconfigured groups.