When you are granted full access permissions to a shared mailbox in Exchange Online or Exchange Server, Outlook automatically adds that mailbox to your profile. This feature is called auto-mapping. While convenient, auto-mapping can clutter the folder pane with unwanted mailboxes, slow down Outlook startup, or confuse users who see mailboxes they do not need. This article explains why auto-mapping occurs and provides the steps to disable it for specific users without affecting other mailbox settings.
Key Takeaways: Disabling Auto-Mapping Per User
- Exchange Admin Center > Recipients > Mailboxes > Shared Mailbox > mailbox delegation > Read and manage permissions: Granting Full Access triggers auto-mapping in Outlook.
- Remove-MailboxPermission PowerShell cmdlet with -AutoMapping $false: Disables auto-mapping for a specific user while keeping their Full Access permission intact.
- Outlook profile manual removal: After disabling auto-mapping, the shared mailbox must be manually removed from the user’s Outlook profile to take effect.
Why Auto-Mapping Happens and How It Works
Auto-mapping is a feature in Exchange Online and Exchange Server 2013 and later. When an administrator grants a user the Full Access permission on a mailbox, Exchange automatically pushes that mailbox into the user’s Outlook profile. The mechanism relies on the msExchDelegateListLink attribute on the mailbox object. Outlook reads this attribute during profile creation or Autodiscover refresh and adds the mailbox as an additional Exchange mailbox in the navigation pane.
The feature works for shared mailboxes, user mailboxes, and resource mailboxes. It does not require the user to manually add the mailbox using File > Account Settings. The mailbox appears under the user’s own mailbox in the folder list. If the user has Full Access to multiple shared mailboxes, all of them appear automatically. This behavior can become problematic when a user only needs Send-As or Send on Behalf permissions but not the mailbox visible in their profile.
Steps to Disable Auto-Mapping Per User
You must use Exchange Online PowerShell or Exchange Management Shell to disable auto-mapping for a specific user. The Exchange Admin Center does not provide a checkbox to control auto-mapping per user. The process involves removing the existing Full Access permission and re-adding it with the -AutoMapping $false parameter. Follow these steps carefully.
Prerequisites
- Global Administrator or Exchange Administrator role in Microsoft 365.
- For on-premises Exchange: Organization Management or Recipient Management role.
- Exchange Online PowerShell module (EXO V2) installed. Run
Install-Module -Name ExchangeOnlineManagementif not present. - User’s Outlook must be closed during the change to avoid conflicts.
Step 1: Connect to Exchange Online PowerShell
- Open Windows PowerShell as Administrator
Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin). - Import the Exchange Online module and connect
Run the following commands:Import-Module ExchangeOnlineManagementConnect-ExchangeOnline -UserPrincipalName admin@contoso.com
Replaceadmin@contoso.comwith your admin account. Sign in with multi-factor authentication if prompted.
Step 2: Identify the Shared Mailbox and User
- Get the current permissions on the shared mailbox
Run:Get-MailboxPermission -Identity "shared@contoso.com" | Format-List User, AccessRights, IsInherited, Deny
Replaceshared@contoso.comwith the email address of the shared mailbox. Note the exact user principal name (UPN) of the user you want to modify. - Confirm the user’s current auto-mapping status
Run:Get-Mailbox -Identity "shared@contoso.com" | fl delegate
Look for theDelegateListLinkandGrantSendOnBehalfToproperties. This step is informational only.
Step 3: Remove the Existing Full Access Permission
- Remove the Full Access permission for the user
Run:Remove-MailboxPermission -Identity "shared@contoso.com" -User user@contoso.com -AccessRights FullAccess -Confirm:$false
This command removes the permission but does not delete any data. The shared mailbox remains intact.
Step 4: Re-add Full Access with Auto-Mapping Disabled
- Add the Full Access permission with AutoMapping set to false
Run:Add-MailboxPermission -Identity "shared@contoso.com" -User user@contoso.com -AccessRights FullAccess -AutoMapping $false
The user retains the ability to open the mailbox manually in Outlook using File > Account Settings > Change > More Settings > Advanced > Add. But the mailbox will not appear automatically in the folder pane.
Step 5: Remove the Shared Mailbox from the User’s Outlook Profile
- In Outlook, go to File > Account Settings > Account Settings
Select the account that contains the shared mailbox. Click Change. - Click More Settings > Advanced tab
Under Open these additional mailboxes, select the shared mailbox and click Remove. Click OK, then Next, then Finish. - Restart Outlook
The shared mailbox should no longer appear in the folder pane. The user can still access it manually by going to File > Account Settings > Change > More Settings > Advanced > Add and typing the shared mailbox name.
What to Do If Auto-Mapping Still Appears
Auto-mapping persists after running the PowerShell commands
This usually happens when the user’s Outlook profile has not been refreshed. Close Outlook completely and restart it. If the mailbox still appears, run the following command to verify the permission settings:Get-MailboxPermission -Identity "shared@contoso.com" -User user@contoso.com | fl AutoMapping
If AutoMapping shows True, repeat the removal and re-add steps. Ensure you use the exact user UPN and not a display name.
The shared mailbox disappears for all users after disabling auto-mapping for one user
This is not possible. The -AutoMapping $false parameter applies only to the specific user you specify in the command. Other users with Full Access permission who have not had their permission re-added with -AutoMapping $false will continue to see the mailbox automatically. If other users lose the mailbox, check whether you accidentally removed their permissions in Step 3. Re-add their permissions with -AutoMapping $true (the default).
User cannot manually open the shared mailbox after disabling auto-mapping
The user must have at least Full Access permission to open the mailbox manually. Verify that the permission exists by running Get-MailboxPermission -Identity "shared@contoso.com" -User user@contoso.com. If the permission is missing, re-add it with Add-MailboxPermission -Identity "shared@contoso.com" -User user@contoso.com -AccessRights FullAccess -AutoMapping $false. Then instruct the user to add the mailbox manually in Outlook using File > Account Settings > Change > More Settings > Advanced > Add.
Auto-Mapping On vs Off: Comparison
| Item | Auto-Mapping Enabled (Default) | Auto-Mapping Disabled |
|---|---|---|
| Mailbox appears in Outlook folder pane | Automatically after permission is granted | Only if user adds it manually |
| User needs to perform extra steps | No | Yes, must use File > Account Settings to add the mailbox |
| Send-As or Send on Behalf permissions | Not affected | Not affected |
| Outlook startup performance | Slower if many shared mailboxes are auto-mapped | Faster because fewer mailboxes are loaded |
| Management method | Default behavior; no action required | PowerShell cmdlet with -AutoMapping $false |
Auto-mapping is a time-saver for most users, but when a shared mailbox is irrelevant or causes performance issues, disabling it per user gives you precise control. The PowerShell method preserves Full Access permission while stopping the automatic appearance in Outlook. Always test the change on one user before applying it broadly. After disabling auto-mapping, remind users how to manually add the shared mailbox if they still need to access it occasionally.