How to set up and manage a shared mailbox in Outlook (2026), and where it stops

Shared mailbox vs distribution list vs Microsoft 365 group

Microsoft 365 offers three ways to put a team behind one address, and picking the wrong one is the most common mistake. Per Microsoft's comparison of group types (learn.microsoft.com, retrieved 23 September 2026):

• Shared mailbox: "used when multiple people need access to the same mailbox, such as a company information or support email address". A real mailbox with its own Inbox, Sent Items and calendar, opened alongside each member's own, which members can send as or on behalf of.
• Distribution group (distribution list): "used for sending notifications to a group of people". Mail is copied into every member's personal inbox: no central copy, no shared Sent folder, no way to see whether a colleague has already answered. Best for broadcasts such as "Everyone at Contoso".
• Microsoft 365 group: a collaboration workspace (group email plus shared files, calendar and Planner) that can include outside guests. Microsoft notes a shared mailbox cannot be migrated to a Microsoft 365 group, so choose deliberately.

For a customer-facing address (support@, info@, bookings@) the shared mailbox is the right default, and the rest of this guide assumes that choice.

Step 1: create the shared mailbox in the Microsoft 365 admin center

You need an Exchange admin role and a Microsoft 365 for business subscription that includes email (Microsoft notes that Microsoft 365 Apps for business does not; Business Standard does). Steps are from Microsoft's Create a shared mailbox article (learn.microsoft.com, retrieved 23 September 2026):

1. Sign in to the Microsoft 365 admin center. If you see "You don't have permission to access this page or perform this action", you are not an admin.
2. Go to Teams & Groups > Shared mailboxes (select Show all if Teams & Groups is hidden).
3. Select + Add a shared mailbox, enter a name (this sets the address, which you can edit), then Save changes.
4. Wait: Microsoft notes "it may take a few minutes before you can add members".

Licensing, in plain terms. Per Microsoft's About shared mailboxes page (learn.microsoft.com, retrieved 23 September 2026), "a shared mailbox can store up to 50 GB of data without assigning a license to it". A licence is needed only to go past 50 GB (Exchange Online Plan 2 raises the cap to 100 GB), to use in-place archiving, or to place the mailbox on litigation hold. The Exchange Online limits table (retrieved 23 September 2026) shows the same figure. Two more rules: each person who opens the mailbox needs their own licensed Exchange Online mailbox, and a shared mailbox supports a maximum of 25 users. Microsoft also warns that a full mailbox first stops sending, then stops receiving and bounces senders.

Step 2: add members and choose permissions

From the same article: under Next steps, select Add members to this mailbox, then Add members, tick the people, select Add and close. Later, edit the roster under Teams & groups > Shared mailboxes > the mailbox > Edit under Members (per Microsoft's Configure shared mailbox settings article, retrieved 23 September 2026).

Microsoft documents three permissions, and the first on its own is not enough to reply:

• Full Access lets a user open the mailbox and act as its owner, but Microsoft is explicit that they "can't send email from the shared mailbox unless they also have Send As or Send on Behalf permission".
• Send As makes the reply look as if the mailbox sent it: the customer sees "Contoso Support".
• Send on Behalf shows both names: "John on behalf of Reception Building 32".

Individual permissions live under Manage mailbox permissions on the mailbox's admin center page (Add permissions or Remove permissions per member). Microsoft's mailbox permissions article (retrieved 23 September 2026) adds the caveat that trips most people: "it can take up to 60 minutes for the changes to propagate through the system and be in effect".

Step 3: open the shared mailbox in Outlook

With automapping on (Microsoft says it is "on by default"), the mailbox appears in each member's Outlook after they close and restart it. One catch: if access was granted through a security group rather than to named people, automapping does not work and members must add it manually. Steps are from Microsoft's Open and use a shared mailbox in Outlook (support.microsoft.com, retrieved 23 September 2026) unless noted.

In new Outlook for Windows

1. Close and restart new Outlook. The mailbox should appear in the Folder pane on its own.
2. If not, select Mail, right-click your account name, and select Add shared folder or mailbox.
3. Type the address (for example info@contoso.com) and confirm. Microsoft notes that if you were added only recently, "it may take a few minutes before the shared mailbox appears".

In classic Outlook for Windows

1. Close and restart Outlook; the mailbox should appear.
2. To add it manually, select File > Account Settings > Account Settings.
3. On the Email tab, select your account, then Change > More Settings > Advanced > Add.
4. Type the shared mailbox address, then OK > OK > Next > Finish > Close.

In Outlook on the web

Per Microsoft's Outlook on the web article (support.microsoft.com, retrieved 23 September 2026), either pin it: right-click Folders in the left navigation, select Add shared folder or mailbox and enter the address; or open it in its own window: select your name on the navigation bar, choose Open another mailbox, type the address and select Open.

On iPhone and Android

Per Microsoft's Outlook mobile article (support.microsoft.com, retrieved 23 September 2026): sign in to your own account in Outlook for iOS or Android, tap Add Account in the left navigation pane, then Add a Shared Mailbox, and pick the account that holds the permission if you have several. Microsoft notes this only works when both mailboxes are in Exchange Online. To remove it, go to Settings > Accounts, tap the shared mailbox and select Delete Account.

Step 4: send as, or on behalf of, the shared mailbox

Replies to mail that arrived in the shared mailbox usually default to its address. For a new message, pick the sender yourself:

• New Outlook: New > Mail, then on the Options tab select Show From and change the From field to the shared address.
• Classic Outlook: New Email, then Options > From, and change From to the shared address.
• Outlook on the web: in a new message, select the more actions icon, choose Show From, right-click the default address, select Remove and type the shared address. It is offered in the From drop-down from then on.

One default that surprises teams, per Microsoft's configuration article: "messages sent from the shared mailbox aren't saved to the Sent Items folder of the shared mailbox. Instead, they are saved to the Sent Items folder of the person who sent the message." To let everyone see replies, an admin selects Edit under Sent items on the mailbox's admin center page.

Automatic replies on a shared mailbox

The switch is in the admin center, not Outlook. Per Microsoft's configuration article (retrieved 23 September 2026): Teams & groups > Shared mailboxes > the mailbox > Edit under Automatic replies, tick Send automatic replies to senders inside this organization, enter text for people inside and outside your organisation, and Save. Microsoft notes "you can't add images, only text", and the panel has no schedule and no conditions. Our Outlook automatic replies guide covers this alongside rule-based replies, and our auto-reply email guide covers what a holding message should say.

Common shared mailbox problems

The shared mailbox is not showing in Outlook

Almost always timing or permission scope. Microsoft says it can take a few minutes after you are added for the mailbox to appear, and up to 60 minutes for permission changes to propagate. Restart Outlook; if it is still missing after an hour, add it manually per Step 3 (the only route if access came via a security group). If the mailbox is hidden from the global address list, Microsoft notes new members cannot add it until it is shown again (Edit under Show in global address list).

"You do not have the permission to send the message on behalf of the specified user"

Per Microsoft's About shared mailboxes page, this appears right after a mailbox is created or a member added, during a replication delay: "It goes away in about an hour". If it persists, check the member has Send As or Send on Behalf, not just Full Access, and that the mailbox is not hidden from address lists, which Microsoft says breaks both permissions in the Outlook desktop client.

Connection failures, duplicates, or mail that has stopped

Too many members (Microsoft caps it at 25 and warns of exactly these symptoms) or a full mailbox. Trim the roster, clear space, or assign an Exchange Online Plan 2 licence to lift the cap to 100 GB.

Where a shared mailbox stops for customer email

For a small team handling a trickle of enquiries, the set-up above is genuinely enough. Once a customer-facing address gets busy, the design choices that make a shared mailbox simple become the problem:

• No ownership. There is no way to assign an email to a person inside Outlook. Two people answer the same customer; nobody answers the one everyone assumed a colleague had.
• No status. Read or unread is the only state. "Waiting on the customer" and "done" look identical, so teams invent folder systems that drift the moment someone is on holiday.
• No reply tracking. Because sent mail defaults to the sender's own Sent Items, the mailbox does not reliably show what has been answered, let alone when.
• Everyone sees everything. Membership is all or nothing: no per-person slice, and Microsoft notes you cannot stop a member deleting messages.
• No answer automation. The only built-in automation is a text-only auto-reply and forwarding. The thirty identical "what are your opening hours" emails each week still need a human to type.

The traditional fix is to migrate to a helpdesk or email ticketing system, at the cost of moving customer conversations out of the tool everyone already knows. Our shared inbox software guide compares that route.

The AI layer: what InReply adds on top of a shared mailbox

InReply (our product, so weigh accordingly) takes a different route: keep the Microsoft 365 mailbox exactly as it is and add an AI email agent on top. You connect the mailbox your team already uses via OAuth, so there is no migration, no add-in and no new address to publish. From there:

• Classification. Every inbound email is sorted by what it is (a question, a booking, a complaint, an invoice), so the team sees a triaged list rather than a wall of unread.
• Grounded drafts, or auto-send. Replies are written only from knowledge you upload (FAQs, PDFs, CSVs, documents or a linked website) organised into playbooks. On every plan it starts in Ghost Mode: drafts are saved in Outlook for a person to review and send. When a playbook has earned your trust, switch it to Autopilot and it sends on its own, with human-like delays, business-hours awareness and a confidence threshold it must clear.
• Action items for the rest. Anything the knowledge base cannot answer is raised to a human as a draft or a tracked, assignable action item in the team workspace: the ownership and status layer the shared mailbox lacks.
• Per-person access. Team members get their own logins with access set per inbox.

Honest limits: it is a paid tool (plans from £39 a month for one inbox, 14-day free trial, no card required; see pricing), it needs a knowledge base worth answering from, and it is not a helpdesk: no ticket numbers, no SLA timers, no reporting dashboards. Our guide to AI email assistants for Outlook compares the wider field.

Shared mailbox alone vs with InReply vs a helpdesk

The short version: shared mailbox alone for a small team with light volume; shared mailbox plus InReply when you want routine questions answered and the rest assigned without leaving Outlook; a helpdesk when you need ticket numbers, SLAs and reporting badly enough to move house.