The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
In a hybrid Exchange environment, this behavior is expected when mail-enabled security groups are created directly in Active Directory without using Exchange management tools.
If the group is synchronized to Microsoft Entra ID and appears in Exchange Online as a Mail-Enabled Security Group, email delivery is primarily determined by the proxyAddresses attribute.
-If somegroup(at)mydomain.com exists in proxyAddresses and is correctly synchronized, mail sent to this address will be delivered to all group members.
-If only somegroup(at)mydomain.onmicrosoft.com appears in Exchange Online, this typically indicates that the on-premises primary SMTP address was not properly stamped, not correctly synchronized, or not fully recognized during Exchange Online recipient provisioning.
Mail sent to any valid and correctly synchronized SMTP address in proxyAddresses will be delivered, provided the object is recognized as a valid Exchange recipient.
The difference in Global Address List (GAL) visibility is most likely due to incomplete or inconsistent Exchange provisioning of the groups.
Since these groups were created directly in Active Directory and not created or managed using Exchange Admin Center or Exchange Management Shell, they may be missing or inconsistently populated Exchange-related attributes such as:
- proxyAddresses,
- mailNickname,
- msExchHideFromAddressLists
- Exchange recipient metadata (including recipient type and address list visibility attributes).
The most common causes of GAL inconsistency are:
-
msExchHideFromAddressListsbeing set to True (object hidden from address lists) - Or Exchange Online not fully recognizing the object as a properly provisioned mail-enabled security group
As a result, some groups are fully recognized Exchange recipients and appear in the GAL and others are only partially provisioned, leading to inconsistent visibility.
This is a common scenario in hybrid environments where groups are mail-enabled directly in Active Directory without Exchange provisioning. Exchange relies on a consistent and complete set of recipient attributes.
To ensure consistent behavior across all groups, it is recommended to:
- Manage mail-enabled security groups using Exchange tools (Exchange Management Shell or Exchange Admin Center)
- Ensure correct population of proxyAddresses, mailNickname, and related Exchange attributes
- Verify synchronization using Microsoft Entra Connect after updates
I hope this information is helpful.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.