How to Make On-Premises Exchange Users Visible in Microsoft 365 GAL
Question details
On-premises mailbox users synchronize to Microsoft Entra ID but fail to appear in the cloud Global Address List, causing NDR 550 5.1.10 errors for cloud users.
- Product
- Microsoft Exchange Server
- Device & OS
- not provided
- Scenario
- Managing a hybrid Microsoft 365 and on-premises Exchange deployment where directory synchronization is active.
- Observed behavior
- Synchronized on-premises users are missing from the cloud GAL, and cloud users receive a '550 5.1.10 RESOLVER.ADR.RecipientNotFound' error when attempting to email them.
Ensure that Microsoft Entra Connect is properly installed and currently running without general synchronization errors, and that you have global admin privileges.
Convert to Remote Mailboxes and Force Synchronization
The most common reason for missing GAL entries is that on-premises users are synchronized as ordinary user objects instead of mail-enabled users. Converting them to remote mailboxes resolves this.
In a hybrid environment, the cloud directory needs to know that the synchronized object is a mail recipient whose mailbox is hosted on-premises. The proper way to represent this is through a remote mailbox object.
Launch the Exchange Management Shell on your on-premises Exchange server.
Run the Enable-RemoteMailbox cmdlet for the affected user to properly configure the mail-enabled user object attributes.
Retrieve the cloud mailbox's ExchangeGuid using Get-Mailbox in Exchange Online PowerShell, then set it on the on-premises object using Set-RemoteMailbox.
Open PowerShell on your Microsoft Entra Connect server and run 'Start-ADSyncSyncCycle -PolicyType Delta' to push the updated attributes to the cloud.
Log into Microsoft 365 and verify that the user now correctly appears in the cloud Global Address List.
Validate Exchange Connectors and Target Addresses
If users are visible but mail flow fails with recipient-not-found errors, target routing addresses or connectors might be misconfigured.
Looking for a Lightweight Office Suite? Try WPS Office
While troubleshooting complex Microsoft 365 hybrid Exchange deployments, you might be looking for a simpler, cost-effective office suite for users who don't require full Microsoft 365 licenses. WPS Office provides a highly compatible, lightweight, and free alternative.
Frequently Asked Questions
Why am I getting a '550 5.1.10 RESOLVER.ADR.RecipientNotFound' NDR?
This Non-Delivery Report (NDR) occurs when the Microsoft 365 cloud directory cannot find a matching mail-enabled object for the recipient. In a hybrid setup, this usually means the on-premises mailbox wasn't correctly synced as a remote mailbox or mail user with the proper target address.
Does enabling a remote mailbox migrate the user to the cloud?
No. Using the Enable-RemoteMailbox cmdlet on an existing on-premises user simply tells Microsoft 365 that the user's mailbox resides on-premises, allowing proper mail routing and GAL visibility without moving the actual mailbox data.
How long does it take for a user to appear in the Microsoft 365 GAL after synchronization?
Once the Microsoft Entra Connect sync cycle finishes, the object appears in Entra ID almost immediately. However, the Microsoft 365 Exchange Online GAL can take up to 24 hours to fully update and replicate across all cloud services and offline address books (OAB).
