Outlook OST File Bloat Due to Auto-Mapped Shared Mailboxes – Causes and Fix

📄 Article

Outlook OST File Bloat Due to Auto-Mapped Shared Mailboxes – Causes and Fix

Outlook performance issues, large OST files, and slow synchronisation are common complaints in Microsoft 365 environments where users have access to multiple shared mailboxes. A frequent root cause is auto-mapping — a default Exchange Online behaviour that forces Outlook to cache entire shared mailboxes locally, significantly increasing OST size and degrading performance.

⚠️ Performance Impact

Auto-mapped shared mailboxes force Outlook to cache the entire mailbox content locally, causing OST files to grow 10GB+ and significantly degrading Outlook performance. Disabling auto-mapping is the recommended fix.

🔍 Symptoms

⚠️ What You May Experience

  • Outlook OST file grows excessively large (10 GB or more)
  • Outlook becomes slow or unresponsive
  • Frequent sync delays or persistent “Updating folder” messages
  • High disk usage caused by cached shared mailbox content

🧠 Root Cause

Why does this happen?

The issue is caused by Exchange Auto-Mapping, which automatically adds shared mailboxes to a user’s Outlook profile when Full Access permissions are granted. By default, Outlook caches shared mailboxes locally in the OST file — downloading the entire mailbox content. This leads to OST bloat especially when:

  • Users have access to multiple shared mailboxes
  • Shared mailboxes contain large volumes of data
  • Cached Exchange Mode is enabled (the default Outlook configuration)

🛠️ Step-by-Step Resolution

1

Disable Auto-Mapping When Granting Shared Mailbox Access

When granting Full Access permissions, explicitly disable auto-mapping using Exchange Online PowerShell.

PowerShell

# Connect to Exchange Online first
Connect-ExchangeOnline

# Grant Full Access with AutoMapping disabled
Add-MailboxPermission `
    -Identity "SharedMailbox@yourdomain.com" `
    -User "User@yourdomain.com" `
    -AccessRights FullAccess `
    -AutoMapping:$false

⚠️ Important

Auto-mapping can only be disabled when permissions are freshly applied. If the permission already exists, you must remove it first and then reassign with -AutoMapping:$false.

2

Remove Existing Auto-Mapped Permissions (If Already Configured)

If Full Access was already granted without -AutoMapping:$false, remove the existing permission first.

PowerShell

# Remove existing Full Access permission
Remove-MailboxPermission `
    -Identity "SharedMailbox@yourdomain.com" `
    -User "User@yourdomain.com" `
    -AccessRights FullAccess `
    -Confirm:$false
3

Manually Add the Shared Mailbox in Outlook

Once auto-mapping is disabled, the shared mailbox must be added manually in Outlook Desktop.

✅ Steps in Outlook

  • Go to File → Account Settings → Account Settings
  • Select your account → click ChangeMore Settings
  • Go to the Advanced tab
  • Click Add… and enter the shared mailbox name or email address
  • Click OK, apply changes, and restart Outlook
4

Optional: Disable Shared Mailbox Caching to Further Reduce OST Size

To prevent shared mailbox content from being cached locally at all, go to File → Account Settings → Change → More Settings → Advanced tab and uncheck “Download shared folders”.

💡 Check Current Auto-Mapping Status via PowerShell

PowerShell

# View Full Access permissions for a shared mailbox
Get-MailboxPermission -Identity "SharedMailbox@yourdomain.com" |
    Where-Object { $_.AccessRights -like "*FullAccess*" -and $_.IsInherited -eq $false } |
    Select-Object User, AccessRights, IsInherited

💡 Best Practices & Recommendations

  • Always use -AutoMapping:$false when granting Full Access to shared mailboxes, especially large or frequently accessed ones
  • Use manual addition with caching disabled for users who access multiple shared mailboxes to keep OST size under control
  • Regularly monitor OST file sizes — Microsoft recommends keeping them below 50 GB for optimal performance
  • Consider using Online Mode for shared mailboxes where real-time access is preferred over local caching
  • Grant least privilege access — avoid broad Full Access where Send As or Send on Behalf is sufficient

📚 References & Further Reading

Leave a Comment

Your email address will not be published. Required fields are marked *