Overview

A shared mailbox may not appear in Outlook because the user lacks Full Access permission, automapping has not completed, Outlook has not refreshed, the wrong account is signed in, or the mailbox must be opened manually.

Do not add permissions just to make the mailbox appearConfirm the user's approved access first. Granting unnecessary access can expose business email.

Why this happens

Shared mailbox visibility depends on Exchange Online permissions and Outlook client behavior. Full Access commonly enables automatic mailbox mapping, but permission propagation can take time and some configurations require manual opening.

Before you begin

  • Confirm the exact shared mailbox address.
  • Confirm the user is supposed to have access.
  • Record whether the mailbox appears in Outlook on the web.
  • Do not remove and re-add the user's main mailbox.

Click-by-click troubleshooting

Step 1: Test the shared mailbox in Outlook on the web

Action: Sign in to Outlook on the web with the user's work account. Select the profile icon and choose Open another mailbox, then enter the shared mailbox address.

Why this matters: This tests Exchange Online permission without relying on desktop Outlook automapping.

What to look for: Confirm whether the mailbox opens or displays an access-denied message.

Expected result: If the mailbox opens on the web, the user has at least functional access and the remaining issue is likely Outlook client mapping.

Step 2: Verify the signed-in Outlook account

Action: In desktop Outlook, open File > Office Account and confirm the intended work identity.

Why this matters: Outlook may be using a different account from the one that has shared-mailbox permission.

What to look for: Look for an old, personal, or unintended Microsoft account.

Expected result: Outlook should be operating under the same work identity that is authorized for the shared mailbox.

Step 3: Restart Outlook after recent permission changes

Action: Close Outlook completely, wait several seconds, and reopen it. If permission was added recently, allow time for Exchange Online propagation.

Why this matters: Automapping is not always immediate and Outlook may need a fresh session.

What to look for: Look for the shared mailbox appearing in the folder pane after restart.

Expected result: The mailbox should appear automatically when Full Access automapping is functioning.

Step 4: Open the shared mailbox manually if access is confirmed

Action: In classic Outlook, open File > Account Settings > Account Settings. Select the primary Exchange account > Change > More Settings > Advanced > Add, then enter the shared mailbox if organizational policy permits manual mapping.

Why this matters: Manual mapping can work when Exchange permission is valid but automapping is unavailable or intentionally disabled.

What to look for: Confirm the mailbox resolves by name and appears after Outlook restarts.

Expected result: The mailbox should appear without changing the user's permissions.

Step 5: Verify Full Access permission if you are an authorized administrator

Action: Open Exchange Admin Center > Recipients > Mailboxes. Select the shared mailbox > Mailbox delegation and review Full Access.

Why this matters: Outlook cannot open the mailbox if Exchange does not grant the user the required permission.

What to look for: Confirm the correct user or approved group is listed and avoid adding broader access than required.

Expected result: The intended user should have the approved level of mailbox access.

Step 6: Compare another authorized user's access

Action: If another approved user has access to the same shared mailbox, confirm whether it appears for them.

Why this matters: This separates a mailbox-wide permission issue from one user's Outlook configuration.

What to look for: Compare web access and desktop visibility between users.

Expected result: The comparison should identify whether the issue is user-specific or mailbox-wide.

What to look for

  • Web access denied: Exchange permission problem.
  • Web works but desktop does not: Outlook mapping or client problem.
  • Recent permission change: allow propagation and restart Outlook.
  • Only one user affected: local Outlook or account-state issue.

When to stop

Stop before broad permission changesDo not grant Full Access, Send As, or Send on Behalf to additional users simply to test visibility. Do not recreate the user's primary Outlook profile without IT direction.

When to contact IT

Contact J3 Systems Group if the mailbox does not open on the web, authorized permissions appear correct but Outlook will not map it, or multiple users are affected. Include article code KB-05.004, mailbox address, user, and web-versus-desktop results.

Need help with this issue?

J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.

Contact J3 Systems Group

Authoritative references

Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.

Article KB-05.004 · Review after material vendor, licensing, interface, security, or service changes.