"Can we have a shared email address for the support team?" sounds like a simple request, but Microsoft 365 offers three different ways to do it. Choosing the wrong one leads to confused users, missing emails and unnecessary licence costs.
The short answer
- Shared mailbox — a team needs to read and reply from one address, such as
support@oraccounts@, with sent items kept in one place. - Distribution list — you just want to broadcast email to a group of people, such as
all-staff@. - Microsoft 365 Group — a team needs a shared inbox plus a calendar, file storage and planning tools, or you plan to use Microsoft Teams.
Side-by-side comparison
| Shared mailbox | Distribution list | Microsoft 365 Group | |
|---|---|---|---|
| Where email lands | One shared inbox | Each member's own inbox | Group conversations (members can also subscribe) |
| Reply as the shared address | Yes, with Send As | No | Yes, with Send As permission |
| Shared sent items | Yes | No | Yes, in group conversations |
| Shared calendar | Yes | No | Yes |
| File storage | No | No | SharePoint site |
| Works with Teams | No | No | Yes |
| Licence required | No, up to 50 GB | No | No (members need their own licences) |
Connect to Exchange Online PowerShell
You can create all three in the Microsoft 365 admin center, but PowerShell is faster and repeatable. Install the module once, then connect:
Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser
Connect-ExchangeOnline -UserPrincipalName admin@example.comCreate a shared mailbox
New-Mailbox -Shared -Name "Support" -DisplayName "Support" -Alias support `
-PrimarySmtpAddress support@example.comGive a user Full Access (open the mailbox) and Send As (send from its address):
Add-MailboxPermission -Identity support -User alex@example.com -AccessRights FullAccess -InheritanceType All
Add-RecipientPermission -Identity support -Trustee alex@example.com -AccessRights SendAs -Confirm:$falseWith Full Access, the mailbox appears automatically in Outlook for that user, usually within an hour.
Create a distribution list
New-DistributionGroup -Name "All Sales" -Alias allsales `
-PrimarySmtpAddress allsales@example.com -Members alex@example.com, sam@example.comAdd or remove members later:
Add-DistributionGroupMember -Identity allsales -Member jordan@example.com
Remove-DistributionGroupMember -Identity allsales -Member sam@example.com -Confirm:$falseBy default, a new distribution list only accepts email from inside your organisation. To accept external email:
Set-DistributionGroup -Identity allsales -RequireSenderAuthenticationEnabled $falseCreate a Microsoft 365 Group
New-UnifiedGroup -DisplayName "Project Apollo" -Alias apollo -AccessType Private
Add-UnifiedGroupLinks -Identity apollo -LinkType Members -Links alex@example.com, sam@example.comThe group gets a mailbox, a calendar, a SharePoint site and a Planner plan. You can add a team in Microsoft Teams to it later without losing anything.
Common mistakes
- Using a licensed user account as a "shared" mailbox and giving everyone the password. This breaks accountability and MFA. Convert it to a shared mailbox instead.
- Using a distribution list for a support desk. Every member gets a copy, nobody knows who replied, and replies come from personal addresses.
- Creating a Microsoft 365 Group when only email is needed. It also creates a SharePoint site and other resources that someone will need to govern.
Which one should you choose?
Start with the question "Does the team need to reply as one address?" If yes, use a shared mailbox — or a Microsoft 365 Group if they also need shared files or Teams. If people only need to receive the same message, a distribution list is the simplest choice.