Microsoft 365 makes it easy to create something with a name, an owner, a list of members, and sometimes an email address. That does not make those objects interchangeable.

A shared mailbox and a distribution list can both use support@company.com, but only one holds the messages it receives. A Microsoft 365 Group and a security group can both control membership, but only one creates a collaboration workspace. A mail-enabled security group can send mail to its members and grant access to a resource, but combining those jobs is not automatically an advantage.

The cleanest way to choose is to stop with the names for a moment and ask what the object actually needs to do:

  • Hold mail for one person.
  • Hold mail for several people to work from.
  • Deliver one message to many inboxes.
  • Give a team a shared workspace.
  • Grant access, assign licenses, or target policy.
  • Grant access and receive email for the same membership.

Those are six different jobs, and Microsoft 365 has a different object for each one.

The decision table

Need Use Stores mail? Grants access? Creates shared resources?
One person’s inbox, calendar, and contacts User mailbox Yes No No
One inbox that several people manage Shared mailbox Yes No Shared calendar
One message delivered to many people Distribution list No No No
Mail, files, calendar, and planning for a team Microsoft 365 Group Yes Yes Yes
Access, licensing, application, or policy targeting Security group No Yes No
Access plus email to the same members Mail-enabled security group No Yes No

The most useful dividing line is storage. A mailbox keeps a copy of what it receives. A distribution list or mail-enabled security group only expands the address and delivers a copy to its members. If someone asks where the history will live, that distinction usually settles half the conversation.

User mailbox: one person, one identity

A user mailbox belongs to one person and is tied to that person’s sign-in. It provides their personal inbox, calendar, and contacts, and it requires an Exchange Online license.

Other people can be delegated access, but delegation does not change the mailbox’s purpose. It is still that user’s mailbox. Full Access lets a delegate open and manage its contents; Send As or Send on Behalf controls whether the delegate can send from it. Those are separate permissions, which matters when someone can open a mailbox but gets an error when trying to reply.

The offboarding order matters here. If the address and history need to remain, convert the mailbox to shared before removing the Exchange license. Keep the account that anchors the mailbox, block sign-in, and confirm whether the resulting shared mailbox still meets the licensing limits.

Shared mailbox: one inbox, several operators

A shared mailbox is for an address such as support@company.com or info@company.com where several people need to read and reply from the same body of mail.

It has a real inbox and calendar. Delegates work through their own licensed accounts, and external users cannot be given delegate access. The mailbox is also not intended for direct sign-in, so its associated account should remain blocked.

The permissions solve different parts of the job:

  • Full Access opens the mailbox and lets the delegate manage items.
  • Send As makes a reply appear to come directly from the shared address.
  • Send on Behalf shows that the delegate sent the message on behalf of the shared address.

Full Access alone does not include either send permission.

A shared mailbox can hold up to 50 GB without its own license. More than 50 GB requires Exchange Online Plan 2. Archive and hold scenarios also have licensing requirements, so “shared mailboxes are free” is too broad to use as a design rule. The delegates need licensed Exchange Online mailboxes either way.

Distribution list: one message, many inboxes

A distribution list does not have an inbox behind it. Send one message to all-staff@company.com, and Exchange delivers that message to the members. The list itself stores nothing and gives nobody a shared place to work.

That makes it the right tool for announcements, notifications, and other fan-out mail. It can accept mail from external senders if an administrator allows it, and delivery restrictions or moderation can control who is allowed to use it.

There is also a dynamic distribution group. Instead of maintaining a static member list, Exchange evaluates recipient attributes when a message is sent. That is useful for targets such as everyone in a department or location, but it is an Exchange mail-flow object—not the same thing as a dynamically populated security group in Microsoft Entra ID.

Use a distribution list when delivery is the whole job. If the team needs a searchable shared history, shared calendar, files, or Planner, the request has already outgrown it.

Microsoft 365 Group: one membership, several services

A Microsoft 365 Group is a collaboration boundary. One membership list can drive a group mailbox and calendar, a SharePoint site, Planner, OneNote, and other connected services. Microsoft Teams uses a Microsoft 365 Group for membership, whether a new group is created with the team or an eligible existing group is connected to it.

This is the choice when the people are meant to work together, not merely receive the same message. It can support guests, and its membership can be static or dynamically managed in Entra ID.

The extra services are also the reason not to create one for every email alias. A project team may need the workspace. A printer-alert address probably does not. Creating a Microsoft 365 Group means creating and eventually governing the resources attached to it, not just adding another entry to the address book.

Security group: access without an inbox

A security group answers a different question: who should have access?

Use it to grant permissions to resources, assign licenses, target Intune applications, or scope policy. It does not have an email address. Security groups can contain users or devices and can use dynamic membership rules in Entra ID.

This is normally the cleanest administrative object when the job is access, licensing, application deployment, or policy targeting. Its name should describe the entitlement or scope it controls—SG-Intune-Pilot tells the next administrator much more than New Group 7.

A cloud security group cannot simply be mail-enabled later. If the same membership genuinely needs both permissions and email, that requirement should be identified before the group is created.

Mail-enabled security group: two jobs, one membership

A mail-enabled security group is a security principal with an email address. It can grant access to a resource and distribute a message to the same members.

That combination is occasionally exactly right. A finance group might both control access to a resource and receive finance notifications. It should still be a deliberate choice, because the object crosses two administrative boundaries: permissions depend on it, and people can send mail to it.

Mail-enabled security groups are created and managed in Exchange. They are visible but read-only through the Microsoft Graph groups API, cannot use dynamic membership in Entra ID, and cannot contain devices. If the real requirement is only Intune targeting or group-based licensing, a plain security group is simpler. If the real requirement is only mail delivery, use a distribution list.

The question that prevents most wrong turns

Before creating any of these objects, finish this sentence:

This object exists so that ________.

If the answer contains two unrelated jobs, pause. Sometimes a combined object is correct, but sometimes the design is hiding two different requirements behind one convenient member list.

The quick rule is straightforward:

  • One person: user mailbox.
  • One team working from one inbox: shared mailbox.
  • One message sent to many people: distribution list.
  • One team collaborating across mail, files, and planning: Microsoft 365 Group.
  • Access, licenses, applications, or policy: security group.
  • Access and email for the same members: mail-enabled security group.

The admin centers make all six objects look close enough to confuse. Their behavior is not close at all. Choose the job first, then create the object.

The one-page reference

The side-by-side version, including key features, examples, and administrative notes, is in the knowledge base:

→ Microsoft 365 Recipient and Group Types — part of my MSP Microsoft 365 knowledge base on GitHub.

Licensing and service behavior change over time. Confirm current Microsoft guidance before using storage limits or licensing details in a client design or quote.

Primary references