Aftab Alam | Updated On - 05 May 2020 |

Read time 4 min

Automatic mapping for the mailbox is a feature which allows Outlook to find all the mailboxes for which full access permissions are given to the user account. When Outlook starts, the auto mapping tries to enlist all the mailboxes.

It is quite convenient to have automapping in the Outlook as it helps the user to directly access the mailbox rather than manually make changes in the settings or add a new mailbox. Automapping came into existence since Exchange Server 2010 SP1 and works like:

1. The Administrator grants full access to a user to access the mailbox of another user(s).
2. The user account gets full permission to access the mailbox (including shared mailboxes).

But the problem arises when your account has permission over several large-sized mailboxes, and every time the Outlook starts, the Autodiscover feature enlists all these mailboxes. It makes Outlook very slow, and if the bandwidth of your connection is also low, then it will be a headache to work smoothly.

The trouble is that you cannot manually delete any mailbox from your Outlook if the automapping feature is in Enabled state. If you remove the mailbox and restart the Outlook, then the mailbox will appear again due to Autodiscover.

Remove automapping using Exchange Management Shell

If you want to get rid of automapping, then you will have to complete the process in two easy steps:

1. Remove the full access permission of the user from the mailbox.
2. Add back the full access permission level of the user for the mailbox but keep the automapping parameter to false.

To do this, follow the below steps:

1. Start Exchange Management Shell and run the following command:
   Remove-MailboxPermission -Identity UserMailbox -User UserName -AccessRights FullAccess -InheritanceType All

   Example –

   Remove-MailboxPermission -Identity Sales -User David -AccessRights FullAccess -InheritanceType All
2. Run the command:
   Add-MailboxPermission -Identity UserMailbox -User UserName -AccessRight FullAccess -Automapping $false

   Example –

   Add-MailboxPermission -Identity Sales -User David -AccessRight FullAccess -Automapping $false

The command will provide the full access rights of the mailbox Sales to the user David. But the automapping
feature is false. So, Outlook will not automatically add it.
Notes:

• The command will work on Exchange Server 2010 SP2 and later versions.
• The command will remove the reference of the mailbox from the msExchDelegateListLink attribute.

You need to run the command for each user account to remove the automapping. But if the number of a user account is too much and the number of mapped mailboxes is too high, then you should run a command (the command is for removing permissions from a shared mailbox):

Important points related to automapping

• Automapping is enabled by default when Full Access Permissions are provided to a user via Add-MailboxPermission. If you need to disable it yourself, then you can do it by keeping:
  Automapping: $false
• You cannot view the state of the automapping setting for the mailbox (even if it is in enabled/disabled state).
• Automapping feature will work only for the individual user accounts. If you want to apply the automapping for a mail-enabled group member, then it will not work.

Conclusion

Automapping is a handy feature to reduce the time in including the mailbox to Outlook, when the user has full access permission. But when you want to migrate the Exchange data to Office 365 or upgrade it to newer Exchange version, then you need to manage full access permissions again in the new environment. But the task would be easy if you can migrate mailbox permissions as well. This is possible with migration tools like Kernel Migrator for Exchange. It is a comprehensive tool which can access the mailbox data from your Exchange Server and migrate to another Exchange Server along with mailbox permissions. The good thing about Exchange Migration tool is that all the properties of mailbox remain the same as the original, after the migration.