How to Create and Configure a Shared Mailbox in Microsoft 365

November 21, 2026

A shared mailbox gives a team a common address such as support@contoso.com or info@contoso.com. Users can read incoming mail, send replies from the shared address, and use the mailbox’s shared calendar without sharing a password.

The most common configuration mistake is granting only one permission. Full Access lets a user open and manage the mailbox, but it does not let the user send from it. For a normal team inbox, grant Full Access and Send As deliberately, then test both behaviors.

Before you begin

  • Permission: Use an account with the Exchange administrator role or the required delegated Exchange permissions.
  • Address: Decide the display name, alias, primary email address, and whether the address should be visible in the Global Address List.
  • Members: Identify the internal users who need access. Shared mailboxes are not a substitute for external guest access.
  • License: Shared mailboxes usually do not require a license. An Exchange Online Plan 2 license is required when the mailbox exceeds 50 GB, uses in-place archiving, or is placed on litigation hold.
  • Security: Do not distribute the mailbox password or use direct sign-in as a workaround. Assign access to individual user accounts and protect those accounts with MFA.

Create the shared mailbox

  1. Sign in to the Microsoft 365 admin center.
  2. Go to Teams & Groups > Shared mailboxes. Select Show all if the section is hidden.
  3. Select + Add a shared mailbox.
  4. Enter the mailbox name. Microsoft 365 uses this to suggest the email address; edit the address if required.
  5. Select Save changes.
  6. Wait a few minutes if the mailbox is not immediately ready.
  7. Under the mailbox’s next steps, select Add members to this mailbox, choose the users, select Add, and close the panel.

Grant the right permissions

Full Access

Full Access lets a delegate open the mailbox and read, create, change, and delete items. It does not grant permission to send mail from the shared address.

Send As

Send As makes an outgoing message appear to come directly from the shared mailbox. This is the usual choice for a support or information address where replies should look like they came from the team.

Send on Behalf

Send on Behalf displays the delegate and the shared mailbox, such as “Alex on behalf of Support.” Use it when that distinction is useful. If a user has both Send As and Send on Behalf, Exchange uses Send As.

Configure delegation in the Exchange admin center

  1. Open the Exchange admin center.
  2. Go to Recipients > Mailboxes and select the shared mailbox.
  3. Select Mailbox delegation or Manage mailbox delegation.
  4. Under Read and manage (Full Access), add the users who need to open and manage the mailbox.
  5. Under Send as, add the users who need to send as the shared address.
  6. Save the changes.
Minimum practical pattern: For a user who must read and reply from the mailbox, grant both Full Access and Send As. Grant only the minimum permissions needed for each person.

Understand automapping

With explicit individual Full Access permissions, Outlook usually adds the mailbox automatically after the user closes and restarts Outlook. This is called automapping. It does not work the same way when access is granted through a group.

If a user should have access without the mailbox appearing automatically, use Exchange Online PowerShell to remove and re-add Full Access with -AutoMapping $false. Make that change only when there is a clear profile-management reason; manual mailbox addition adds support overhead.

Connect-ExchangeOnline
Add-MailboxPermission -Identity "support@contoso.com" -User "alex@contoso.com" -AccessRights FullAccess -InheritanceType All -AutoMapping $false
Add-RecipientPermission -Identity "support@contoso.com" -Trustee "alex@contoso.com" -AccessRights SendAs

Use the current Exchange Online PowerShell module and verify the exact recipient identity before running commands. The command example is a pattern; replace the sample addresses with real identities and do not paste it unchanged into production.

Verify the mailbox

  1. Close and restart Outlook for a user with explicit Full Access. Confirm that the shared mailbox appears, or add it manually if your organization intentionally disabled automapping.
  2. Open the mailbox and confirm that the Inbox and shared calendar are visible.
  3. Send an internal test message from the shared address using the From field.
  4. Confirm that the recipient sees the shared address rather than the delegate’s personal address.
  5. Check Sent Items and the mailbox’s sent-message behavior according to your organization’s policy.
  6. Test a user who has access but not Send As. Confirm that the permission boundary behaves as intended.

Common errors and limitations

The user can open the mailbox but cannot send from it

Full Access does not include sending. Add Send As or Send on Behalf, depending on the required From behavior.

The mailbox does not appear in Outlook

Allow time for permission propagation, restart Outlook, and confirm that the user has explicit Full Access. Group-based access does not provide the same automapping behavior.

Send As does not work

Confirm that the mailbox is not hidden from address lists when using the Outlook desktop client. Verify the delegation entry in the Exchange admin center and allow time for changes to propagate.

The mailbox needs more storage or legal hold

Assign the required Exchange Online Plan 2 license when the mailbox exceeds 50 GB, uses in-place archiving, or is placed on litigation hold. Licensing does not remove the need for least-privilege access.

Security and lifecycle checklist

  • Use named user accounts and MFA. Never make users share the mailbox password.
  • Review members and delegation permissions quarterly and after staff changes.
  • Use Send As only for users who are authorized to represent the mailbox.
  • Document ownership, retention, and escalation for the mailbox.
  • Remove unused permissions before deleting or repurposing the address.

Related Guava Insights guides

Official documentation

Topics:
Read next
November 17, 2026

Microsoft 365 Business Basic vs Standard vs Premium vs E3 in Canada (2026): Which Plan Should You Buy?

A practical Canadian comparison of Microsoft 365 Business Basic, Standard, Premium, and E3, including verified November 2026 pricing, feature differences, user limits, hidden costs, and recommendations by business need.
November 17, 2026

How to Enable Self-Service Password Reset in Microsoft Entra ID

Enable Microsoft Entra self-service password reset safely with a pilot group, strong recovery methods, registration prompts, testing, and hybrid writeback guidance.