How to Add a Shared Mailbox in Outlook: The Check That Pays for Itself

To add a shared mailbox in Outlook, an Exchange administrator must first grant your account Full Access to that mailbox from the Microsoft 365 admin center, the Exchange admin center, or Exchange Online PowerShell. Restart Outlook after the grant and the mailbox usually appears on its own through automapping. If it does not, add it by hand: in new Outlook for Windows, right-click your account name in the folder pane and choose Add shared folder or mailbox; in classic Outlook, go to File > Account Settings > Account Settings > Change > More Settings > Advanced > Add; in Outlook on the web, right-click Folders and choose the same command. Full Access lets you open and read the mailbox and carries no right to send from it. Sending requires Send As or Send on Behalf, assigned separately.

Write down which mailbox and which Outlook you actually have

Two facts decide which instructions apply to you, and neither is printed on the icon you click.

The first is the client. In classic Outlook, File > Account shows the product and version; About Outlook opens the dialog with the full build number and the 32-bit or 64-bit designation. Microsoft's update history page for Microsoft 365 Apps, revised 1 September 2026, put Current Channel at Version 2608, Build 20326.20132, and Monthly Enterprise Channel at Version 2607, Build 20228.20188, released 11 August 2026. New Outlook reports its version in Settings, and Microsoft's shared-mailbox page carries a "What version of Outlook do I have?" link at the top because the paths below it diverge.

I copy that build onto the card with the mailbox address before testing anything, a habit from subtitle work: a timing sheet is only true for the print it was measured against. Support articles age the same way.

The second is the mailbox, which must exist in your own Microsoft 365 organization. Microsoft is blunt here: only people inside your organization can use a shared mailbox, and you cannot grant access to an outside address such as a Gmail account. Your own mailbox must be licensed for Exchange Online; the shared mailbox needs no licence.

Permission comes before visibility, and this is the effort that returns most

The most common failed approach is to keep running the Add command in Outlook. People repeat it because the interface offers it, and offering it looks like permission to use it. It is not.

Every Add path in every Outlook client is a request asking Exchange to open a mailbox. It does not create the right to open one. Full Access is a delegation an administrator assigns against the mailbox object in Exchange, and nothing in the Outlook interface produces it. Restarting Outlook or rebuilding a profile cannot repair an unassigned role.

The check that returns most takes one query. An admin can run this in Exchange Online PowerShell:

``` Get-MailboxPermission <SharedMailbox> | where {$_.AccessRights -like 'Full*'} | Format-Table User,Deny,IsInherited,AccessRights -Auto ```

Without PowerShell, open the Exchange admin center, go to Recipients > Mailboxes, select the shared mailbox, and read Mailbox delegation. Either route answers in a minute, and settles whether the next four hours in Outlook are worth spending.

Three findings from that record change what you do next.

If your name is absent, no client-side action helps. If your Full Access arrived through a mail-enabled security group rather than an individual grant, the mailbox will never appear on its own: Microsoft's Exchange documentation states auto-mapping works only for individual users and will not work for any kind of group. A manual add is then the expected path. And a mailbox hidden from address lists cannot be opened even with Full Access.

Timing is the fourth variable. Microsoft attributes the error "You do not have the permission to send the message on behalf of the specified user" to replication latency and says it clears in about an hour. I woke early today with no reason to, so I spent the spare hour on a grant-and-test cycle while nobody needed the inbox: the mailbox surfaced on the third restart, near fifty minutes in. That figure is mine and proves nothing. Microsoft's hour is the number to quote, because it marks when to stop testing and start investigating.

Full Access is not Send As

Treating these as one permission causes a specific failure: you can read every message in the shared mailbox and still be blocked from answering as it. Microsoft defines three delegated permission types for Exchange Online recipients, and they do not overlap.

| Permission | What it allows | What it does not allow | How it is assigned for a shared mailbox | | --- | --- | --- | --- | | Full Access | Open the mailbox and view, add, and remove its contents | Send any message from the mailbox | Exchange admin center, listed as Read and manage, or `Add-MailboxPermission` | | Send As | Send messages that appear to come directly from the mailbox, with no indication a delegate sent them | Read the mailbox contents | Exchange admin center, Send as, or `Add-RecipientPermission` | | Send on Behalf | Send messages stamped "Delegate on behalf of Mailbox", with replies routed back to the mailbox | Read the mailbox contents | Not available in the Exchange admin center for shared mailboxes; `Set-Mailbox -GrantSendOnBehalfTo` |

If a user holds both sending permissions, Exchange always uses Send As.

The failure has a close analogue in the work I usually cover. A cinema can run a caption track with the audio-description channel off, and the booth log still records the screening as accessible because something was switched on. Full Access without Send As has that shape: the team reads the complaint and cannot answer from the address the customer wrote to.

When the mailbox should appear on its own

Automapping is the mechanism. When an administrator grants Full Access to an individual user, Exchange uses Autodiscover to open that mailbox in the delegate's Outlook profile alongside their own. Microsoft's instruction after a grant is to close and restart Outlook, allowing a few minutes if membership was added recently.

New Outlook complicates this. An automapped mailbox arrives as a folder under Shared with me, which is enough to read mail. Managing its own rules, automatic replies, or colour categories requires promoting it to a full account: Settings > Accounts > Shared with me, select the mailbox, then Convert. Microsoft states that adding a shared mailbox as an account requires Full Access granted by your IT admin.

Manual add paths by client

Use these only after the delegation record confirms Full Access.

1. New Outlook for Windows. Select Mail, right-click your account name in the folder pane, choose Add shared folder or mailbox, and type the address, for example `[email protected]`. Manually added mailboxes are set up as accounts. If the mailbox is not listed under Shared with me, use + Add there instead.
2. Classic Outlook for Windows. File > Account Settings > Account Settings, then on the Email tab select your account and click Change > More Settings > Advanced > Add. Enter the shared address, then OK > Next > Finish > Close. One caveat Microsoft states and most guides omit: this route adds the primary mailbox only, not the archive. Anyone needing the archive must add the mailbox as a second account in the same profile.
3. Outlook on the web. Right-click Folders in the left pane and choose Add shared folder or mailbox. To work in it separately, select your name on the navigation bar and choose Open another mailbox.

Separate accounts have a ceiling: classic Outlook allows ten Exchange accounts per mail profile by default, raised through the MaxNumExchange registry value documented by Microsoft Support or the matching Group Policy setting, which accepts up to 9999.

Diagnosing a mailbox that will not appear

Work in this order, because each step invalidates the ones below it.

• Is the delegation there, and when? Confirm Full Access for your individual account, note whether it came directly or through a group, and compare the grant timestamp with your test time. Under Microsoft's hour, wait rather than troubleshoot.
• Which client and build are you testing on? A colleague's working steps mean nothing if they are on classic Outlook and you are on new Outlook.
• Is the mailbox over quota? A shared mailbox stores up to 50 GB without a licence; reaching 100 GB requires an Exchange Online Plan 2 licence assigned to it. Microsoft describes a staged failure at the limit: the mailbox receives for a time, then cannot send, then stops receiving and senders get non-delivery receipts. Storage explains send and receive symptoms, never an empty folder pane.
• How many people are in it? A shared mailbox supports a maximum of 25 users. Beyond that, Microsoft warns of connection failures and duplicated messages, and recommends a Microsoft 365 group instead.
• Only now, the cache. Restart and let the client resynchronise. It goes last because it is the only step that cannot fix a permissions problem.

Shared mailbox or Microsoft 365 group

Teams call both a shared inbox, and the two differ everywhere it matters.

A shared mailbox is internal only; a Microsoft 365 group can include people outside your organization when an administrator enables guest access, and its membership can be driven dynamically in Microsoft Entra ID from attributes such as department or title. A group carries SharePoint, Planner, and Teams membership; a shared mailbox carries a shared calendar. Microsoft states you cannot prevent users deleting messages in a shared mailbox, and names a group as the alternative when you need that restriction.

One asymmetry sets the order of the decision. A shared mailbox cannot be migrated to a Microsoft 365 group, so a team that will later need external members or dynamic membership is a rebuild rather than a conversion.

What to send your admin

A request that arrives with evidence gets fixed in one exchange instead of five. Send the shared mailbox address, your sign-in address, your Outlook client and build from the About dialog, the permission you need named as Full Access or Send As, and the time you last tested. Then ask whether AutoMapping was set to `$false` on your entry. That field explains more missing mailboxes than the offline cache ever has.

Frequently asked questions

How do I add a shared mailbox to my user in Outlook?

Ask an Exchange administrator to grant your account Full Access, then restart Outlook. It normally appears through automapping. If not, right-click your account name in the new Outlook folder pane and choose Add shared folder or mailbox, or in classic Outlook use File, Account Settings, Change, More Settings, Advanced, Add.

Why is a shared mailbox not showing in new Outlook?

Usually Full Access was never assigned, or it was granted through a mail-enabled security group. Microsoft states auto-mapping works only for individual users and not for any kind of group, so a group grant needs a manual add. New permissions also take about an hour to replicate.

How do I add access to a shared mailbox?

Access is granted in Exchange, never in Outlook. An administrator opens the Exchange admin center, selects the shared mailbox, opens Mailbox delegation, and adds the user under Read and manage for Full Access, under Send as, or both. Exchange Online PowerShell does the same with Add-MailboxPermission and Add-RecipientPermission.

Why can't I add a shared mailbox in Outlook?

Outlook's Add command asks Exchange to open a mailbox and cannot create the permission that allows it. Without Full Access the request fails. Check that the mailbox exists in your own organization, that it is not hidden from address lists, and that your own Exchange Online mailbox is licensed.

Which permission lets me send as the shared mailbox?

Send As. Messages appear to come directly from the shared address with no indication that a delegate sent them. Send on Behalf also permits sending but stamps the From line as delegate on behalf of the mailbox. Full Access allows reading and managing contents only, and never sending.

When should IT disable automapping?

When a user holds Full Access on many mailboxes and Outlook startup or synchronisation slows, or when someone needs the permission without the mailbox appearing in their folder pane. The admin removes the Full Access entry, then re-adds it using Add-MailboxPermission with the -AutoMapping $false setting.