SUPPORTED TENANTPILOT TASK · Fictional examples · Updated October 2026
When a shared mailbox makes sense
Use a shared mailbox where several colleagues need to read and respond to messages sent to one address. Its purpose differs from a distribution list, which forwards copies into individual inboxes. A shared mailbox can also have its own calendar.
Before you create it
- Choose an appropriate name and address that belongs to your organisation.
- Agree who will have access and whether they should send as the mailbox.
- Check the current Microsoft licensing rules for shared mailboxes, especially mailbox size, archive or hold requirements.
Create one in the Microsoft 365 admin centre
- Sign in as an administrator with the required permissions.
- Open Teams & groups → Shared mailboxes (the navigation may vary).
- Choose Add a shared mailbox, provide the name and email address, then save.
- Add approved members and set Full Access or Send As as appropriate.
- Test receiving and sending mail with an authorised test account.
PowerShell example
In an authorised Exchange Online PowerShell session, an example for a new shared mailbox is:
New-Mailbox -Shared -Name "Enquiries" -DisplayName "Enquiries" -PrimarySmtpAddress "[email protected]"Creating the mailbox does not itself grant colleagues access. Permission assignment is a separate step; review the permissions guide.
Where TenantPilot fits
TenantPilot includes a Create shared mailbox task. It can help an authorised staff member run the supported change while reviewing the details first. More complex migration or compliance work should remain with your IT team.
Further reading and official guidance
Microsoft services and interfaces can change. Check the linked official guidance before making changes in a live organisation.
Prefer guided Microsoft 365 administration?
TenantPilot provides guided tasks for suitable day-to-day administration on Windows, while complementing your existing IT support partner.
See TenantPilot in Microsoft Store ↗Always follow your organisation’s permissions, privacy and IT support procedures.