Helpdesk: "Alex was added to the info@ shared mailbox this morning and it still isn't in Outlook. Maria got added to billing@ through the Billing Team group last week and she can't see it either. Can you remove and re-add their permissions, or rebuild their Outlook profiles?" An hour later a second ticket: the shared mailbox shows up for Jordan in Outlook on Windows, but not on his MacBook or phone.
Don't rebuild profiles yet. A shared mailbox "showing up in Outlook" is mostly automapping, and automapping only happens when the whole chain holds: the user has their own licensed Exchange Online mailbox → Full Access exists on the shared mailbox → that Full Access was granted to the user directly, not through a security group → the grant wasn't added with -AutoMapping $false → Outlook was restarted so Autodiscover could pick it up → the client actually supports automapping (classic Outlook for Windows and new Outlook do; Outlook for Mac, Outlook mobile, and Outlook on the web are added by hand) → the user didn't hide it in the folder list. Microsoft's Add-MailboxPermission docs, the "mailboxes aren't automapped" troubleshooting article, and the per-client support pages are the sources for that chain, not a forum post that says "delete the OST."
If the real problem is "it shows up but new mail doesn't appear," jump to Step 6 (sync and cached mode). If it's "I can open it but my replies land in my own Sent Items," that's Step 7. If Outlook keeps prompting for a password while opening the shared mailbox, start with Outlook Keeps Asking for My Password. This post covers a shared mailbox that is missing from Outlook, missing on one client only, or visible but not behaving like a mailbox.
TL;DR
- Automapping is driven by direct Full Access grants. Microsoft says Autodiscover doesn't enumerate security groups that have Full Access. Group-granted Full Access works if the user adds the mailbox by hand (or in Outlook on the web), but it won't appear on its own.
-
-AutoMappingdefaults to$true, but it's set at grant time. If someone granted Full Access with-AutoMapping $false(common for admins with access to many mailboxes), the only documented way to flip it is to remove Full Access and add it back. - Restart Outlook, then wait a bit. Microsoft's user guidance is "close and restart Outlook," and if the grant is new, "it may take a few minutes." There is no fixed SLA, so don't rebuild the profile in the first hour.
- Not every client automaps. Microsoft says Outlook for Mac doesn't support automapping. Outlook mobile and Outlook on the web need the shared mailbox added manually. "Works on my PC, not my Mac" is expected behavior, not a broken permission.
- New Outlook puts it under Shared with me, and it may not sync on its own. Automapped shared mailboxes in new Outlook don't auto-sync the Inbox. Users can select Sync or Convert it to an account. Users can also Hide in folder list.
- The user needs their own licensed mailbox. The shared mailbox doesn't need a license (under the documented limits), but the person opening it does.
Where in the chain did it break?
| Step | What should be true | Typical symptom when it breaks |
|---|---|---|
| 1. Symptom captured | Exact client (classic, new Outlook, Mac, web, mobile) and what "not showing" means | "Shared mailbox broken" with no client or user named |
| 2. User is licensed | User has a licensed Exchange Online mailbox | Can't open it anywhere, including Outlook on the web |
| 3. Full Access exists |
Get-MailboxPermission lists the user (or their group) with FullAccess |
Can't open it manually either |
| 4. Granted directly | Full Access is on the user, not a mail-enabled security group | Opens manually or on the web, never appears automatically |
| 5. AutoMapping on | Grant wasn't made with -AutoMapping $false
|
Direct grant, still never appears in classic/new Outlook |
| 6. Client supports it | Classic Outlook for Windows or new Outlook | Missing only on Mac, mobile, or Outlook on the web |
| 7. Shown and synced | Not hidden in new Outlook; cached-mode settings not hiding mail | Mailbox is there but empty, stale, or "missing old mail" |
Write down the user's UPN, the shared mailbox address, every client they tried, when the permission was added, and how it was added (EAC mailbox delegation, Microsoft 365 admin center Add members, PowerShell, or a group). Most tickets are solved by that last field.
Step 1: Capture the exact symptom (read-only)
| What the user sees | Most likely layer |
|---|---|
| Missing in classic Outlook for Windows and new Outlook, but opens fine in Outlook on the web | Group-based Full Access, or a grant with AutoMapping disabled |
| Missing everywhere, and "Add shared folder or mailbox" fails too | No Full Access yet, wrong mailbox, or the user's own mailbox isn't licensed |
| Missing only in Outlook for Mac | Expected. Mac doesn't automap; add it via Delegation and Sharing |
| Missing only on iPhone/Android | Expected. Add it in Outlook mobile with Add a Shared Mailbox |
| Missing only in Outlook on the web | Expected. Add it with Add shared folder or mailbox under Folders |
| New Outlook: listed under Shared with me but Inbox doesn't update | Automapped mailboxes don't auto-sync in new Outlook; Sync or Convert |
| New Outlook: it was there yesterday, gone today | User selected Hide in folder list on the automapped card |
| Classic Outlook: shows, but old mail missing or search finds nothing older | Cached mode Mail to keep offline applies to shared mailboxes |
| Shows up, but can't send from it | Full Access isn't Send As / Send on Behalf; separate permission |
| Replies land in the user's own Sent Items | Expected default; MessageCopyForSentAsEnabled / MessageCopyForSendOnBehalfEnabled
|
Microsoft's shared mailbox admin article is clear that Full Access lets a user open the mailbox and act on items, but can't send from it without Send As or Send on Behalf. "It shows up but I can't send" is a different permission, not a display bug.
Step 2: Confirm the user and the shared mailbox (read-only)
Exchange Online PowerShell, signed in with an account that can read recipients:
# Read-only. Connect-ExchangeOnline -UserPrincipalName admin@contoso.com
$shared = 'info@contoso.com'
$user = 'alex@contoso.com'
# Is the target really a shared mailbox, and is it hidden from the address list?
Get-Mailbox -Identity $shared | Select-Object `
DisplayName, PrimarySmtpAddress, RecipientTypeDetails,
HiddenFromAddressListsEnabled,
MessageCopyForSentAsEnabled, MessageCopyForSendOnBehalfEnabled,
GrantSendOnBehalfTo
# Does the person opening it have their own mailbox (UserMailbox)?
Get-Mailbox -Identity $user | Select-Object DisplayName, RecipientTypeDetails, PrimarySmtpAddress
# Who has Full Access (explicit, non-system entries only)?
Get-MailboxPermission -Identity $shared |
Where-Object { -not $_.IsInherited -and $_.User -notlike 'NT AUTHORITY\*' } |
Select-Object User, AccessRights, IsInherited, Deny
# Who has Send As?
Get-RecipientPermission -Identity $shared |
Where-Object { $_.Trustee -notlike 'NT AUTHORITY\*' } |
Select-Object Trustee, AccessRights
# Is a principal in the Full Access list a group or a user?
# Get-Recipient -Identity '<value from the User column>' | Select-Object DisplayName, RecipientTypeDetails
How to read it:
| Finding | Meaning |
|---|---|
RecipientTypeDetails = SharedMailbox
|
Right object. If it says UserMailbox, someone shared a person's mailbox; same rules, different ticket |
User's own RecipientTypeDetails isn't UserMailbox
|
Microsoft says a user needs a licensed Exchange Online mailbox to access a shared mailbox. UserMailbox proves the mailbox exists; confirm the license in the admin center |
| User not in the Full Access list | Nothing to automap yet; the grant didn't save or went to the wrong mailbox |
| A group in the Full Access list, user not listed directly | Access works, automapping won't (Step 3) |
Deny = True on an entry |
An explicit deny is in play; read it before adding anything |
HiddenFromAddressListsEnabled = True
|
Users can't find it by name in the address book; Microsoft also says Send As and Send on Behalf don't work in Outlook desktop when the mailbox is hidden |
Whichever portal granted access (Microsoft 365 admin center Add members or EAC Manage mailbox delegation), the result is readable with the same Get- cmdlets. If the entry is there, stop editing the permission and move to the client.
Step 3: Direct grant or group grant? (read-only)
This is the most common cause in the whole article. Microsoft documents it in three places:
| Source | What it says |
|---|---|
Add-MailboxPermission |
Automapping uses Autodiscover, and Autodiscover doesn't enumerate security groups that have Full Access |
| "Mailboxes aren't automapped to Outlook profile" | When Full Access is assigned through a security group, members don't get the mailbox automapped. It can still be added manually or used in Outlook on the web |
| Create a shared mailbox (M365 admin) | Using a security group to manage access means automapping won't work; assign permissions explicitly if you want automapping |
So Maria's ticket from the opener ("added through the Billing Team group") is working as designed. Her options are a direct Full Access grant, or adding the mailbox manually in each client. Rebuilding her profile won't change it.
Add-MailboxPermission also notes that only mail-enabled security groups work as the permission holder. Non-mail-enabled security groups can be selected but don't work. If a group is on the list and nobody in it can open the mailbox at all, check the group type with Get-Recipient.
To find every shared mailbox one user has a direct Full Access entry on:
# Read-only. Can be slow in large tenants.
Get-Mailbox -RecipientTypeDetails SharedMailbox -ResultSize Unlimited |
Get-MailboxPermission -User 'alex@contoso.com' |
Select-Object Identity, User, AccessRights
If a mailbox you expected isn't in that output, the user's access (if any) comes from a group.
Step 4: Was AutoMapping turned off at grant time? (read-only)
-AutoMapping is a parameter on Add-MailboxPermission. Microsoft lists $true as the default and says:
-
$true: the mailbox is automatically added to the user's Outlook profile if the user has Full Access. -
$false: it isn't. - To disable automapping for a user who already has Full Access, you remove Full Access and add it back with
-AutoMapping $false.
Get-MailboxPermission output doesn't include an AutoMapping column, so you usually prove this from history, not from a property. Ask:
| Question | Why it matters |
|---|---|
| Was the grant made by a script or onboarding tool? | Scripts often pass -AutoMapping $false to avoid huge Outlook profiles for admins |
| Does the user have Full Access to many mailboxes? | Microsoft's "remove automapping" article exists because many automapped mailboxes slow Outlook startup |
| Did the same user automap other shared mailboxes fine? | Then the client and profile are healthy; the difference is in this one grant |
If the grant is direct, AutoMapping wasn't disabled, and the mailbox still never appears in classic Outlook after restarts, add it manually in the profile (Step 5) to prove access works before touching permissions.
Step 5: Match the client to the right method (read-only)
Automapping is a feature of classic Outlook for Windows (and new Outlook surfaces it under Shared with me). Every other client adds the mailbox by hand. Use this table before anyone opens a ticket for "Mac is broken":
| Client | Automaps? | How the user adds it (per Microsoft support) |
|---|---|---|
| Classic Outlook for Windows | Yes (direct Full Access, AutoMapping on) | Restart Outlook. If not there: File → Account Settings → Account Settings → Email → Change → More Settings → Advanced → Add |
| New Outlook for Windows | Shows automapped mailboxes under Shared with me | Restart. If not there: right-click your account name → Add shared folder or mailbox, or Settings → Accounts → Shared with me → + Add |
| Outlook on the web | No | Right-click Folders → Add shared folder or mailbox; or your name → Open another mailbox for a separate window |
| Outlook for Mac | No (Microsoft says Mac doesn't support automapping) | Tools → Accounts → Delegation and Sharing → Shared With Me → +, or File → Open → Shared Mailbox |
| Outlook for iOS / Android | No | Add Account → Add a Shared Mailbox; both mailboxes need to be in Exchange Online |
Two client notes that cause repeat tickets:
- Outlook for Mac: Microsoft says only Full Access is fully supported for shared mailboxes. Adding a shared mailbox through the main Add email account window gives "Account already exists"; use Delegation and Sharing instead.
- Outlook on the web: to get new-mail notifications for the shared Inbox, Microsoft says to open it in a separate window with Open another mailbox.
If the manual add works but automapping doesn't, the permission is fine. Go back to Steps 3–4.
Step 6: It shows up, but it's empty, stale, or hidden (read-only)
New Outlook for Windows
| Symptom | What Microsoft documents | User action |
|---|---|---|
| Automapped mailbox's Inbox doesn't update | Incoming mail isn't automatically synchronized in Inbox folders of automapped shared mailboxes | Select Sync on the View ribbon, or select the folder |
| Needs notifications, rules, or automatic replies | These need the mailbox added as an account | Settings → Accounts → Shared with me → expand the card → Convert (needs Full Access) |
| Mailbox disappeared from the folder pane | Automapped mailboxes can't be removed by the user, only hidden | Shared with me → expand card → Show in folder list |
Microsoft notes that adding a mailbox as an account "may not be available in your version of new Outlook." If Convert is missing, use Sync or Outlook on the web.
Classic Outlook in Cached Exchange Mode
| Symptom | What Microsoft documents | Read before changing |
|---|---|---|
| Only recent mail visible; search misses older items | Since Outlook 2016, the Mail to keep offline slider applies to shared mailboxes when Download shared folders is on, and there's no "view more on the server" link for them | The user's slider value; any DisableSyncSliderForSharedMailbox policy |
| Slow startup or folders not syncing in a big shared mailbox | Outlook caches every shared folder by default; a shared mailbox with more than 500 folders can exhaust a per-mailbox server limit | Folder count; whether Download shared folders is enabled |
| New mail lags behind Outlook on the web | Cached shared folders sync on Outlook's schedule | Compare with Outlook on the web first. If the web is current, it's the client |
Always check Outlook on the web first for "mail isn't arriving." If the message is in the shared mailbox on the web, mail flow is fine and the issue is the desktop cache.
Step 7: It works, but sending or Sent Items looks wrong (read-only)
| Symptom | Cause (per Microsoft) | Read |
|---|---|---|
| "You don't have permission to send" from the shared address | Full Access doesn't include sending |
Get-RecipientPermission (Send As), GrantSendOnBehalfTo (Send on Behalf) |
| Send As fails only in Outlook desktop | Send As and Send on Behalf don't work in Outlook desktop when HiddenFromAddressListsEnabled is True
|
Get-Mailbox output from Step 2 |
| Sent mail is in the user's own Sent Items, not the shared one | Outlook sends from the user's account, so the copy is saved in the sender's mailbox by default |
MessageCopyForSentAsEnabled, MessageCopyForSendOnBehalfEnabled (both default False) |
For new Outlook, Microsoft says only the mailbox-side MessageCopyFor… settings apply. The classic-Outlook DelegateSentItemsStyle registry workaround doesn't.
Step 8: Change one thing (only after the read)
Only after Steps 1–7, and only with change control:
# EXAMPLES: deliberate changes. Make one, restart Outlook, retest.
# Give a group member automapping: add a DIRECT Full Access grant for the user
# Add-MailboxPermission -Identity 'billing@contoso.com' -User 'maria@contoso.com' -AccessRights FullAccess -AutoMapping $true
# Re-grant to turn automapping back on (documented pattern is remove, then add):
# Remove-MailboxPermission -Identity 'info@contoso.com' -User 'alex@contoso.com' -AccessRights FullAccess
# Add-MailboxPermission -Identity 'info@contoso.com' -User 'alex@contoso.com' -AccessRights FullAccess -AutoMapping $true
# Keep a copy of Send As / Send on Behalf mail in the shared mailbox's Sent Items:
# Set-Mailbox -Identity 'info@contoso.com' -MessageCopyForSentAsEnabled $true
# Set-Mailbox -Identity 'info@contoso.com' -MessageCopyForSendOnBehalfEnabled $true
Retest:
- Close and restart Outlook. Microsoft says a new grant may take a few minutes to appear.
- Check the client the user actually uses (new Outlook: Shared with me).
- Confirm the old group grant is still there if other people rely on it. Adding a direct grant doesn't replace it.
Add-MailboxPermission caps a mailbox at 500 permission entries and recommends security groups past that. That's the trade-off: groups scale but don't automap. For a large team, it's normal to grant through a group and have people add the mailbox manually.
When a change is justified
| Finding | Prefer | Avoid |
|---|---|---|
| Group-granted Full Access, user wants it to appear automatically | Direct Full Access for that user (AutoMapping default) | Rebuilding the Outlook profile or deleting the OST |
Direct grant made with -AutoMapping $false
|
Remove and re-add Full Access with -AutoMapping $true
|
Adding a second identical grant and hoping |
| Admin has Full Access to dozens of mailboxes; Outlook is slow | Re-grant with -AutoMapping $false and open mailboxes on demand |
Leaving every mailbox automapped |
| Missing on Mac, mobile, or the web only | Show the user the manual add for that client | Touching permissions at all |
| New Outlook: Inbox not updating | Sync, or Convert to an account if available | Removing and re-adding permissions |
| Classic Outlook: old mail missing | Adjust Mail to keep offline or shared-folder caching per Microsoft's article | Telling users "the mail was deleted" |
| Sent Items in the wrong mailbox |
MessageCopyForSentAsEnabled / MessageCopyForSendOnBehalfEnabled
|
Registry hacks fleet-wide without testing |
| User can't open it anywhere | Check the user's own license and the Full Access entry first | Assigning a license to the shared mailbox |
FAQ
Why is my shared mailbox not showing in Outlook?
In order of how often it happens: Full Access was granted through a security group (Autodiscover doesn't expand groups, so no automapping); the grant was made with -AutoMapping $false; Outlook hasn't been restarted since the grant; or the user is on a client that doesn't automap (Mac, mobile, Outlook on the web). Read Get-MailboxPermission on the shared mailbox and ask which client the user is on before changing anything.
Why is the shared mailbox not showing in new Outlook?
New Outlook lists automapped shared mailboxes under Shared with me. If it isn't there, right-click your account → Add shared folder or mailbox, or use Settings → Accounts → Shared with me → + Add. If it was there and vanished, check whether it was set to Hide in folder list. Automapped mailboxes in new Outlook also don't auto-sync their Inbox; use Sync or Convert to an account.
Why is the shared mailbox not showing in Outlook for Mac?
Microsoft says Outlook for Mac doesn't support automapping of shared mailboxes. Add it under Tools → Accounts → Delegation and Sharing → Shared With Me → + (or File → Open → Shared Mailbox). Use Full Access; other permission types aren't fully supported on Mac.
Does automapping work with security groups?
No. Microsoft says Autodiscover doesn't enumerate security groups that have Full Access, so members of a group can open the mailbox manually or in Outlook on the web, but it won't appear automatically. For automapping, grant Full Access to each user directly.
How long does it take for a shared mailbox to appear in Outlook?
Microsoft's user guidance is to close and restart Outlook, and that if you were only recently added "it may take a few minutes." There's no published fixed SLA. If it hasn't appeared after a restart and a reasonable wait, check whether the grant is direct and whether AutoMapping was disabled rather than rebuilding the profile.
Related posts
- Does a Shared Mailbox Need a License? (shared mailbox limits, and why the user needs the license)
- A Monthly Exchange Online Hygiene Check (read-only review of who has Full Access and Send As)
- Outlook Keeps Asking for My Password (when the shared mailbox opens with credential prompts)
- An Offboarding Checklist for M365 + Intune Admins (converting a leaver to a shared mailbox and granting access the right way)
Free checklist
Shared mailbox tickets tend to show up during the same week as a Conditional Access or MFA rollout, when "I can't see the billing mailbox" and "I can't sign in" get mixed in one queue. Before you enforce, the free Conditional Access pre-enforcement checklist keeps break-glass accounts, pilot groups, and report-only review on one page:
If you want the rest of the M365 admin runway written down for the team (break/fix cards, offboarding and mailbox decisions, and read-only PowerShell snapshots), the Intune & M365 Admin Starter Pack pairs with this triage: https://cashflow4375.gumroad.com/l/joonf?utm_source=devto&utm_medium=article&utm_campaign=aps_first_sale&utm_content=shared-mailbox-not-showing-in-outlook
Admin Pack Studio; not affiliated with Microsoft. Steps 1–7 only read: client menus, Outlook on the web, Get-Mailbox, Get-MailboxPermission, Get-RecipientPermission, and Get-Recipient. Add-MailboxPermission, Remove-MailboxPermission, Set-Mailbox, Outlook cache settings, and registry values are deliberate changes. Make one change for one user, restart Outlook, retest on the client they actually use, and check current Microsoft Learn and Microsoft Support for menu labels, which change often in new Outlook.
Top comments (0)