'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Automatic Mapping for On-Premises Mailboxes in Hybrid Exchange
Question details
The user needs to fix an issue where an on-premises mailbox does not automatically map in Outlook for a user whose primary mailbox is hosted in Exchange Online.
- Product
- Microsoft Exchange / Outlook
- Device & OS
- not provided
- Scenario
- A user with an Exchange Online mailbox has been granted full access to an on-premises mailbox, but it fails to appear in their Outlook client.
- Observed behavior
- Despite having full access permissions, the automatic mapping feature fails to display the on-premises mailbox in the Outlook interface.
Ensure you have administrative privileges to the Exchange Management Shell (EMS) on your on-premises server and that Active Directory synchronization is currently healthy.
Remove and Reassign Full Access Permissions with Automapping
Resetting the mailbox permissions using the Exchange Management Shell forces the automapping attribute to correctly apply to the user's profile.
In a hybrid Exchange environment, permissions granted through graphical interfaces do not always correctly trigger the Automapping attribute. Using the Exchange Management Shell (EMS) explicitly configures this setting.
Open the Exchange Management Shell as an Administrator on your on-premises Exchange server.
Run the command: Remove-MailboxPermission -Identity "SharedMailboxName" -User "UserEmail" -AccessRights FullAccess to clear the current, faulty permission.
Run the command: Add-MailboxPermission -Identity "SharedMailboxName" -User "UserEmail" -AccessRights FullAccess -AutoMapping $true to explicitly enable automapping.
Allow enough time for Azure AD Connect to synchronize the updated directory attributes to Exchange Online, then have the user restart their Outlook client.
Verify Autodiscover and Global Address List (GAL) Visibility
Automapping relies heavily on a properly functioning Autodiscover service and mailbox visibility within the Global Address List.
Looking for a Lightweight Alternative to Microsoft Office?
While resolving advanced IT configurations for Microsoft Exchange and Outlook, you or your users may want a more straightforward, fast, and lightweight productivity suite. WPS Office provides an excellent free alternative that is fully compatible with major Office formats and designed to enhance everyday document workflow without heavy subscription fees.
- 1. Visit the WPS Office Website: Go to the official WPS website to find the latest free version for your operating system.
- 2. Download the Installer: Click the 'Free Download' button to save the lightweight installation package to your computer.
- 3. Install and Start Working: Run the installer, follow the on-screen prompts, and immediately begin managing your documents with full Microsoft format compatibility.
Frequently Asked Questions
Why does automapping fail even when a user has Full Access permission?
Automapping can fail if the permission was granted via a method that doesn't trigger the AutoMapping parameter (like certain GUI actions), if the target mailbox is hidden from the Global Address List, or if directory synchronization (AAD Connect) has not yet replicated the change to Exchange Online.
How long does it typically take for automapping to apply in a hybrid Exchange setup?
It typically depends on your Azure AD Connect sync intervals and Outlook client caching. It usually takes anywhere from 30 minutes to a few hours for the synchronized permissions to reflect and automap the mailbox in the user's Outlook client.
Can I manually add the shared on-premises mailbox if automapping isn't working?
Yes. If the user has Full Access permissions, they can bypass automapping by going to File > Account Settings > Account Settings > Change > More Settings > Advanced, and manually adding the mailbox via the 'Add' button.
Does the Test-OutlookWebServices cmdlet work for Exchange Online mailboxes?
Test-OutlookWebServices is primarily used for testing on-premises Exchange Autodiscover and EWS health. For Exchange Online mailboxes, Microsoft provides the Microsoft Remote Connectivity Analyzer tool to test connectivity and Autodiscover resolution.
