Email Sync Problems

How to Fix Exchange Archive GUID and Mailbox Alias Sync Errors

Phi Hung VoPhi Hung Vo Nov 2, 2026 869 views

Question details

The user needs to resolve an Active Directory and Microsoft 365 synchronization error regarding the Archive GUID and Mailbox Alias.

How to Fix Exchange Archive GUID and Mailbox Alias Synchronization Errors
Product
Microsoft Exchange
Device & OS
not provided
Scenario
Synchronizing an on-premises archive mailbox with Exchange Online via Azure AD Connect.
Observed behavior
Archive GUID values mismatch between the remote mailbox and Exchange Online, resulting in a synchronization error, often incorrectly referencing the DisabledArchiveGuid instead of the active archive GUID.
Before you start

Before proceeding, ensure you have administrative access to both the on-premises Exchange Management Shell and Exchange Online PowerShell, and verify that Azure AD Connect is functioning.

Solution 1Recommended

Compare and Resolve Archive GUID Mismatches Using PowerShell

Use PowerShell commands to verify the Archive GUIDs on both environments and manually trigger a delta sync after correcting aliases or disabling archives.

For a synchronized mailbox with an on-premises archive, the archive GUID values must match correctly between the remote mailbox and Exchange Online. Relying on DisabledArchiveGuid is incorrect for an active archive.

1
Get On-Premises Mailbox Info

Open the Exchange Management Shell on your on-premises server and run 'Get-RemoteMailbox user | Format-List' to locate the current ArchiveGuid value.

2
Get Exchange Online Info

Connect to Exchange Online PowerShell and run 'Get-Mailbox user | Format-List'. Compare this ArchiveGuid value with the one obtained from your on-premises server.

3
Update Mailbox Alias

If necessary, change the mailbox alias on-premises to trigger an attribute update in the directory.

4
Force Azure AD Sync

Run the command 'Start-ADSyncSyncCycle -PolicyType Delta' on your Azure AD Connect server to push the new synchronization changes to the cloud.

5
Disable On-Premises Archive (If Required)

If the on-premises archive must be completely disabled to clear the conflict, execute the command 'Disable-RemoteMailbox "user" -Archive'.

Compare and Resolve Archive GUID Mismatches Using PowerShell
Review Outputs Carefully: Always review the complete synchronization error logs and PowerShell output thoroughly before manually changing any archive attributes.
Free Microsoft Office alternative

Need a Lightweight Alternative to Microsoft 365?

Managing complex Microsoft server environments and Exchange synchronization can be challenging. If you are looking for a straightforward, lightweight, and completely free office suite for your daily document management, consider WPS Office. It offers a familiar interface, highly compatible formatting, and requires no complicated backend configuration.

  1. 1. Download WPS Office: Visit the official WPS website and click 'Download WPS Office Free' for your operating system.
  2. 2. Install the Suite: Run the downloaded installer and follow the quick setup instructions.
  3. 3. Open and Edit: Launch WPS Office and instantly open your existing Word, Excel, or PowerPoint files without formatting loss.
Fully compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Lightweight installation with zero complex backend synchronization required.Free built-in PDF tools for seamless document editing and conversion.All-in-one suite covering Writer, Spreadsheet, and Presentation in a single tabbed interface.
microsoft office alternative - wps office

Frequently Asked Questions

Why does an Archive GUID mismatch occur during synchronization?

This mismatch typically happens when an archive mailbox is enabled directly in Exchange Online instead of being provisioned on-premises, or if the user object was recreated, causing the on-premises ArchiveGuid attribute to differ from the cloud's record.

What is the role of DisabledArchiveGuid in Exchange?

The DisabledArchiveGuid parameter stores the GUID of an archive mailbox that has been disabled or disconnected. It should not be matched or used for an active archive during a normal synchronization process.

How do I force an Azure AD Connect synchronization?

You can force a delta synchronization by running the PowerShell command 'Start-ADSyncSyncCycle -PolicyType Delta' on the server hosting Azure AD Connect. This pushes the latest attribute changes, including mailbox aliases and GUIDs, to Microsoft 365.