Fix Exchange Account Not Updating in GAL with Mailbox Name Suffix
Question details
A recreated Exchange account fails to update in the Global Address List (GAL) and displays a suffix on the mailbox name due to identifier conflicts or synchronization issues.

- Product
- Microsoft Exchange
- Device & OS
- not provided
- Scenario
- Managing a recreated Exchange account in a hybrid or synchronized environment.
- Observed behavior
- The account does not appear correctly in the GAL, and the mailbox name unexpectedly includes a suffix, often caused by duplicate identifiers, litigation holds, or Azure AD Connect sync errors.
Ensure you have Exchange Administrator permissions in both your on-premises and Exchange Online environments, and strictly review your organization's compliance and retention policies before modifying any litigation hold settings.
Verify Exchange GUIDs and Azure AD Sync Object Matching
Resolve naming and visibility issues by verifying consistency between on-premises and Exchange Online objects, ensuring accurate GUID matching and synchronization.
Incorrect object matching during Azure AD Connect synchronization is a leading cause for recreated accounts failing to display in the GAL. Conflicting Exchange GUIDs or duplicate archive values typically trigger automatic mailbox suffixes to avoid database collisions.
Open the Exchange Management Shell for your on-premises server and Exchange Online PowerShell. Run the Get-Mailbox cmdlet to compare the ExchangeGUID attribute for the specific user across both environments.
Using Exchange Online PowerShell, verify the account's provisioning status by checking the HiddenFromAddressListsEnabled property. If it is set to True, modify it to False so the user can be displayed in the GAL.
Check for duplicate ArchiveGuid values and conflicting email addresses on the tenant that might be holding onto the original mailbox name.
Once the on-premises and cloud object attributes are aligned, open PowerShell on your AD Connect server and run 'Start-ADSyncSyncCycle -PolicyType Delta' to push the corrected attributes.

Manage Litigation Holds and Rename Mailbox
Temporarily manage litigation holds to allow correct mailbox renaming and synchronization, eliminating the unwanted suffix.
Discover a Lightweight Office Suite with WPS Office
While WPS Office does not manage Exchange server configurations or GAL syncing, it serves as a powerful, free, and lightweight alternative to Microsoft Office for your daily productivity and documentation needs. It offers seamless format compatibility and a familiar interface, ensuring smooth team collaboration.

Frequently Asked Questions
Why does a recreated Exchange mailbox get a suffix in its name?
This typically happens when Exchange detects a duplicate mailbox identifier or email address from a previously deleted account. This is usually caused by active litigation holds or replication delays that prevent total deletion of the original account.
How long does the Global Address List (GAL) take to update?
By default, the Offline Address Book (OAB), which clients like Outlook download to view the GAL locally, updates once every 24 hours. Administrators can force an immediate update using the Update-OfflineAddressBook cmdlet in the Exchange Management Shell.
Can a litigation hold prevent an Exchange account from updating correctly?
Yes. An active litigation hold preserves all mailbox items, properties, and identifiers. This preservation can cause conflicts during account recreation or block name changes from synchronizing properly across hybrid environments.
How do I check if a mailbox is hidden from the GAL?
You can check this in the Exchange Admin Center by opening the mailbox properties and reviewing the 'Hide from address lists' checkbox. Alternatively, use Exchange PowerShell and run the Get-Mailbox cmdlet to check if the HiddenFromAddressListsEnabled property is set to True.




