Fix Shared Inbox Folder Permissions After Migration

After migrating your shared inbox, agents can’t see or manage folders. This guide walks through the most common permission problems, how to verify each one, and the steps to restore access.

NNeuraDesk TeamNovember 19 20264 min read
On this page

After a migration, the most immediate sign of trouble is that agents open the shared inbox and find folders missing, grayed out, or return a "permission denied" error when they try to move messages. The symptom usually appears across the team at once, which points to a system‑level change rather than an individual mailbox issue.

1. Inherited permissions not applied

When folders are created in the source system, they often inherit permissions from the parent mailbox or a security group. Migration tools sometimes copy the folder structure but skip the inherited access control entries.

How to confirm

  • Open the folder properties in the admin console (Exchange Admin Center, Google Workspace Admin, or the equivalent).
  • Check the Access Control List (ACL) for the affected folders. Look for missing entries such as "Full Access" or "Editor" for the support group.
  • Compare a working folder’s ACL with a broken one.

How to fix

  • Add the missing group or user permissions manually on each folder, or run a script that reapplies the parent’s inheritance to all child folders.
  • After the change, ask a test agent to open the inbox and verify the folders appear.
  • For ongoing consistency, see Best Practices Organizing Shared Inbox Folders for Teams.

2. Migration tool stripped ACLs

Some migration utilities focus on message content and folder hierarchy but do not transport mailbox‑level permissions. The result is a clean folder tree with no access rights attached.

How to confirm

  • Review the migration tool’s logs for warnings about "permissions not migrated" or "ACL skipped."
  • In the destination system, inspect a folder’s security tab; it may show only the owner.

How to fix

  • Re‑run the migration with the permission‑migration option enabled, if the tool supports it.
  • If the tool cannot migrate permissions, apply a bulk permission script after migration (PowerShell for Exchange, GAM for Google Workspace).
  • Verify that the shared inbox now shows the expected folders for all agents.

3. Group membership changes

During migration, the support distribution group or security group may have been recreated, renamed, or its membership altered. Agents who were members of the old group lose access because the new group has a different identifier.

How to confirm

  • List the members of the group that should have access in the identity provider (Azure AD, Google Groups, etc.).
  • Cross‑reference with the list of agents reporting the issue.
  • Check the folder ACL for the group’s object ID; a mismatch indicates a new group object.

How to fix

4. Mailbox folder hierarchy mismatch

The source system may have used a nested folder structure (e.g., "Support > Billing > Refunds") while the destination flattens or renames folders. Agents looking for the old path see nothing because the folders exist under a different name or parent.

How to confirm

  • In the admin console, browse the full folder tree of the shared mailbox.
  • Search for folder names that agents expect; note any differences in naming or nesting.
  • Ask agents to use the "All Folders" view to see if the folders appear elsewhere.

How to fix

  • Rename or move folders to match the expected hierarchy.
  • Communicate the new structure to the team and update any internal documentation.
  • Consider a one‑time mapping document to ease the transition.

5. Client‑side caching or Outlook profile issues

Even when server‑side permissions are correct, a stale Outlook profile or cached mode can hide folders or show outdated permission errors.

How to confirm

  • Have an affected agent open the shared inbox via web mail (OWA or Gmail web). If folders appear there, the issue is client‑side.
  • Check the Outlook connection status for "Cached Exchange Mode" and the size of the OST file.

How to fix

  • In Outlook, disable Cached Exchange Mode for the shared mailbox, restart, then re‑enable it.
  • Alternatively, delete the OST file for the shared mailbox and let Outlook rebuild it.
  • Ensure the Outlook profile is updated to the latest version of the mailbox (especially after a tenant‑to‑tenant migration).

When nothing works

If the steps above do not restore access, take a systematic approach:

  1. Collect the exact error message and the time it occurs.
  2. Enable mailbox audit logging (if available) to capture permission checks.
  3. Run a permission report from the admin center to export the full ACL for the shared mailbox.
  4. Compare the report with a known‑good mailbox.
  5. Engage your identity or messaging administrator to verify that no conditional access policies or security defaults are blocking the group.
  6. As a last resort, recreate the shared mailbox, apply the correct permissions from the start, and migrate messages again.

If you repeatedly hit permission walls with your current platform, a tool that includes a shared inbox, automatic email‑to‑ticket conversion, and AI reply suggestions at no per‑agent cost can simplify the setup. Try NeuraDesk free to see how a unified inbox handles permissions out of the box. For related sync problems, see Shared Inbox Not Syncing Across Agents: Troubleshooting Guide.

Try NeuraDesk free and see if it fits your team.

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