Troubleshooting Permission Issues in Outlook Shared Mailbox

If you cannot open, send from, or see folders in a shared mailbox, this guide walks through the most likely causes and how to resolve them.

NNeuraDesk TeamNovember 19 20264 min read
On this page

When a shared mailbox stops behaving — messages disappear, the mailbox won’t open, or you cannot send as the shared address — the problem is usually a permission setting or a client‑side issue. Start by confirming the exact symptom: you see an error when opening the mailbox, you can open it but cannot send, or folders such as Sent Items are missing. The steps below are ordered from the most common cause to the less frequent ones.

1. Incorrect Permissions Assigned

How to confirm Open the Microsoft 365 admin center, go to the shared mailbox, and review the delegation settings. Look for Full Access, Send As, and Send on Behalf entries for the affected user or group. How to fix Add the missing permission. For full mailbox access, grant Full Access. To allow sending as the shared address, add Send As. If the user only needs to send on behalf, add Send on Behalf. Save changes and wait a few minutes for replication.

2. Outlook Cache or Profile Issues

How to confirm Open the same shared mailbox in Outlook on the web (OWA). If it works there, the issue is local to the desktop client. Also try creating a new Outlook profile (Control Panel → Mail → Show Profiles → Add). How to fix Clear the Outlook cache: close Outlook, delete the contents of the RoamCache folder (typically %localappdata%\Microsoft\Outlook\RoamCache), then restart Outlook. If the problem persists, remove and re‑add the shared mailbox from Account Settings → Change → More Settings → Advanced → Open these additional mailboxes.

3. License or Subscription Mismatch

How to confirm Verify that the user has an active Exchange Online license (or Microsoft 365 Business Premium, E3, E5). In the admin center, check the user’s Licenses and Apps tab. How to fix Assign the appropriate license if it is missing. After the license is applied, wait up to 30 minutes for the mailbox permissions to become effective.

4. Group Membership vs Direct Permissions

How to confirm If access is granted through a security group, confirm that the group is mail‑enabled and that the user is a direct member. In the admin center, open the group and check the Members list and the Email address field. How to fix Either add the user directly to the mailbox delegation or ensure the group is a mail‑enabled security group (or Microsoft 365 group) with an email address. Non‑mail‑enabled groups cannot receive delegated permissions.

5. Automapping Disabled or Misconfigured

How to confirm Run the PowerShell command Get-Mailbox -Identity "SharedMailbox" | Select-Object Automapping. If the value is False, automapping is off. Also check whether the user sees the mailbox automatically in Outlook’s folder pane. How to fix Enable automapping with Set-Mailbox -Identity "SharedMailbox" -AutoMapping $true. If you prefer manual control, keep automapping off and add the mailbox manually via Account Settings → Advanced → Open these additional mailboxes.

6. Cross‑Tenant or Hybrid Configuration Issues

How to confirm Determine whether the shared mailbox resides in a different tenant or in an on‑premises Exchange environment that is hybrid‑joined. Look for trust relationships and federation settings in the admin center. How to fix For cross‑tenant access, configure Azure AD B2B collaboration and assign the appropriate permissions in the target tenant. For hybrid setups, ensure that the on‑premises mailbox has the correct msExchDelegateListLink and msExchDelegateListBL attributes, and that the hybrid configuration wizard has run successfully.

7. Outlook Version or Platform Limitations

How to confirm Test access from Outlook on the web, the Outlook mobile app, and a different desktop version (for example, the new Outlook for Windows vs classic Outlook). How to fix Update the desktop client to the latest build. If a specific version cannot display the shared mailbox, use OWA as a workaround while the client is updated.

When Nothing Works

If the mailbox still cannot be accessed after the steps above, collect the following information before contacting Microsoft support:

  • Exact error message and timestamp.
  • Results of the OWA test.
  • Output of Get-MailboxPermission and Get-RecipientPermission for the shared mailbox.
  • Details of the user’s license and group memberships.

As an alternative, teams that need a simple shared inbox with AI reply suggestions, automatic email‑to‑ticket conversion, and ticket status tracking can try a free tool built for that purpose. Resolving Shared Inbox Permission Issues shows how a dedicated shared inbox avoids many of the delegation complexities described here. You can also compare free Outlook shared‑inbox options in Shared Inbox for Outlook Free Options Compared and learn how to track replies in How to track who replied to what in Outlook shared inbox. If you want a free shared inbox that includes AI suggestions and ticket tracking, try NeuraDesk free.

Found this useful? Share it with your team.

Join teams already using NeuraDesk

Ready to get started?

Create your workspace and try NeuraDesk for free.

Sign up free