How to Show Azure AD Connect Users in Exchange Global Address List
Question details
The user needs to make Azure AD Connect users with third-party email addresses visible in the cloud Exchange Global Address List (GAL).

- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- The user is attempting to replace an on-premises mail contact with an Active Directory user account for LDAP authentication, while ensuring the user remains visible in the Exchange GAL.
- Observed behavior
- Synchronized AD users do not automatically appear in the cloud GAL without the correct mail attributes, hybrid synchronization settings, and Exchange licensing. In some cases, contacts fail to synchronize entirely without triggering errors.
Ensure you have administrative privileges for both your on-premises Active Directory and Exchange Admin Center, and verify that Azure AD Connect is running without critical synchronization errors.
Configure Mail Attributes and Enable Hybrid Synchronization
Ensure the correct on-premises attributes are populated and hybrid sync is active to properly display users in the GAL.
For a synchronized user to appear in the cloud Global Address List, specific Active Directory attributes must be mapped and synchronized. Missing attributes or incorrect Exchange hybrid settings will prevent the object from properly registering as mail-enabled in the cloud.
Open Active Directory Users and Computers (ADUC) with Advanced Features enabled. Right-click the target user, go to Properties, and select the Attribute Editor tab. Ensure the 'mail', 'mailNickname', and 'proxyAddresses' attributes are correctly populated.
Launch the Azure AD Connect wizard on your sync server. Navigate to Optional Features and verify that 'Exchange Hybrid Deployment' is checked and enabled.
In the Microsoft 365 Admin Center, ensure the synchronized user is assigned an Exchange Online license, or properly associate the account with an on-premises Exchange mailbox if maintaining a hybrid routing setup.
Open PowerShell as an Administrator on your Azure AD Connect server and run the command 'Start-ADSyncSyncCycle -PolicyType Delta' to push the attribute changes immediately to Azure AD.
Maintain Separate User and Contact Records (Workaround)
If merging roles fails or causes sync issues, keep separate AD records for authentication and email delivery.
Looking for a Cost-Effective Productivity Suite?
While you are managing Exchange directories and Azure AD environments for your business, providing powerful desktop productivity tools for your end-users shouldn't strain your IT budget. WPS Office is a feature-rich, lightweight, and highly compatible alternative to Microsoft Office.

Frequently Asked Questions
Why are my synchronized on-premises users missing from the cloud GAL?
Users generally will not appear in the cloud Global Address List if their 'mail', 'mailNickname', or 'proxyAddresses' attributes are empty in the on-premises Active Directory, or if they haven't been assigned an appropriate Exchange Online license.
How can I hide a synchronized Azure AD Connect user from the GAL?
You can hide a user by setting the 'msExchHideFromAddressLists' attribute to 'True' in your on-premises Active Directory Attribute Editor, and then running a delta synchronization cycle via Azure AD Connect.
Why does a synced contact fail to appear in Azure AD with no errors reported?
Silent sync failures for contacts often occur if the organizational unit (OU) containing the contacts is excluded from the Azure AD Connect sync scope, or if the contact lacks a properly formatted external email address (targetAddress).




