How to Fix Missing Shared Mailboxes in the New Outlook Interface

Switching to the New Outlook for Windows interface often leaves users wondering where their delegated and shared mailboxes went. In classic Outlook, shared mailboxes typically mounted automatically at the bottom of the folder pane through Exchange automapping. In New Outlook, differences in background synchronization, account handling, and folder delegation can prevent these shared mailboxes from appearing automatically.

Fast Fix

Right-click Folders (or your primary account name) in the left sidebar, select Add shared folder or mailbox, enter the shared mailbox email address, and click Add. The mailbox will appear pinned under the Shared with me section in your folder list.

---

Diagnostic Snapshot

Property	Details
Primary Cause	Automapping delay, group-based delegation, or architectural changes in New Outlook
Impact Level	Moderate (inability to view, sort, or send from delegated mailboxes)
Admin Required?	Only if permissions are assigned via security groups or permissions need verification
Resolution Path	Manual folder pinning → OWA validation → Exchange permission audit

---

Why Shared Mailboxes Disappear in New Outlook

Classic Outlook relies on MAPI over HTTP and locally cached Autodiscover XML profiles to discover and attach mailboxes assigned to your account. When Exchange automapping is enabled, classic Outlook reads the msExchDelegateListLink attribute during profile boot and mounts the secondary store.

New Outlook runs on a web-based architecture unified with Outlook on the web (OWA). Instead of maintaining local profile data, it connects directly through Microsoft Graph and modern Exchange Online protocols. This introduces three distinct failure points:

1. The “Shared with me” Container: Shared mailboxes do not always generate an independent root account in the sidebar. Instead, they nest within your primary account structure under a dedicated Shared with me header.
2. Security Group Delegation: Exchange Online automapping only functions when Full Access permissions are assigned directly to an individual user account. If your IT department granted you access through a mail-enabled security group or Microsoft 365 group, automapping does not trigger in New Outlook.
3. Token Caching Delays: Permission updates can take up to an hour to propagate through Microsoft Entra ID and Exchange Online directory caches before New Outlook recognizes the mailbox.

---

Diagnostic Steps and Solutions

Shared Mailbox Missing in New Outlook
 │
 ├── 1. Check Primary Account Pane
 │    └── Expand primary account → Look for "Shared with me" node.
 │         ├── Found? → Expand folder to view mail.
 │         └── Not found? → Proceed to Step 2.
 │
 ├── 2. Manually Pin the Mailbox
 │    └── Right-click "Folders" → "Add shared folder or mailbox" → Enter email.
 │         ├── Mailbox mounts successfully? → Resolved.
 │         └── Error: "Cannot find or open folder"? → Proceed to Step 3.
 │
 ├── 3. Validate in Outlook on the Web (OWA)
 │    └── Sign in at outlook.office.com → Right-click "Folders" → Add shared folder.
 │         ├── Fails in OWA? → Permissions issue (Proceed to Step 4).
 │         └── Works in OWA only? → New Outlook sync issue; reset app data.
 │
 └── 4. Audit Exchange Permissions (Admin Escalation)
      └── Verify direct Full Access assignment (not via Security Group).

Step 1: Manually Pin the Shared Mailbox

If automapping does not display the mailbox, add the mailbox path manually into your personal folder hierarchy:

1. In New Outlook, expand your primary account in the left folder pane.
2. Right-click on Folders (or your account display name).
3. Select Add shared folder or mailbox.
4. In the dialog box, type the display name or full email address of the shared mailbox.
5. Select the account from the directory suggestions and click Add.
6. Look under your primary folder list for a section titled Shared with me. Expand it to access the shared Inbox, Sent Items, and custom folders.

Note: If you receive an error stating the folder cannot be found, your account either lacks permissions or directory replication is still pending.

Step 2: Validate Access in Outlook on the Web (OWA)

When manual pinning fails, isolate whether the issue belongs to the New Outlook client or your cloud mailbox permissions:

1. Open a browser and sign in to Outlook on the web (outlook.office.com).
2. Right-click Folders in the left navigation pane and click Add shared folder.
3. Enter the shared mailbox address and click Add.

• If the mailbox works in OWA but fails in New Outlook: The New Outlook client cache is stuck. Go to Windows Settings > Apps > Installed Apps, locate Outlook (New), select Advanced options, and click Reset.
• If the mailbox also fails to open in OWA: You do not have valid Exchange Online permissions. Proceed to Step 4.

Step 3: Sending Mail from the Shared Mailbox

Viewing messages differs from sending messages. In New Outlook, mounting a shared mailbox does not automatically grant you sending privileges unless your tenant administrator explicitly configured Send As or Send on Behalf permissions.

To verify sending functionality:

1. Click New Mail.
2. If the From field is hidden, click the Options tab in the ribbon and select Show From.
3. Click the From drop-down menu. If the shared mailbox is not listed, click Other email address… and type the shared address.
4. Compose and send a test message. If you receive an immediate Non-Delivery Report (NDR) with status code 550 5.7.1 Client does not have permissions to send on behalf of this sender, contact your administrator to grant Send As permissions in Exchange Online.

---

Administrator Escalation and Directory Checks

If manual mounting fails, your M365 tenant administrator must verify permission assignments using PowerShell or the Exchange Admin Center (EAC).

1. Direct Assignment vs. Group Membership

Automapping does not support mail-enabled security groups. Run the following Exchange Online PowerShell command to check how permissions are structured:

Get-MailboxPermission -Identity "sharedmailbox@domain.com" -User "user@domain.com"

If the user is receiving access through a security group, the administrator must either:

• Grant FullAccess directly to the user’s mailbox object: Add-MailboxPermission -Identity "sharedmailbox@domain.com" -User "user@domain.com" -AccessRights FullAccess -AutoMapping $true
• Or educate the user to access the shared mailbox by opening it via the “Open another mailbox” profile redirection URL in a browser.

2. Verify Send As Rights

To allow outbound mail delivery from the shared address:

Add-RecipientPermission -Identity "sharedmailbox@domain.com" -Trustee "user@domain.com" -AccessRights SendAs -Confirm:$false

---

Hard Stops and Workarounds

If you depend heavily on legacy features—such as opening shared mailboxes as standalone MAPI accounts with independent signature sets, out-of-office rules, and separate offline cache sliders—New Outlook does not currently replicate all classic MAPI functionality.

If your workflow requires legacy shared mailbox management while your organization plans its tenant migration, you can temporarily return to classic Outlook:

• How to Revert to Classic Outlook after “Forced Update” (The Registry Fix)

If you are also experiencing delays when accessing shared calendars linked to this mailbox, see:

• Troubleshooting “Delegated Access” Calendar Sync Lag