Exchange Connection Problems

Fix Exchange Archive GUID Errors in Microsoft 365 Hybrid

Rana GarciaRana Garcia Nov 2, 2026 869 views

Question details

The user needs to resolve an archive validation error in a Microsoft 365 hybrid deployment caused by a mismatch between the on-premises msExchArchiveGUID and the Exchange Online archive GUID.

How to Fix Exchange Archive GUID Errors in a Microsoft 365 Hybrid Environment
Product
Microsoft 365 Exchange
Device & OS
not provided
Scenario
Managing mailbox archives and synchronizing user attributes in a Microsoft 365 hybrid environment.
Observed behavior
Administrators experience Microsoft 365 hybrid archive errors because the on-premises Active Directory msExchArchiveGUID attribute does not match the cloud-based Exchange Online archive GUID.
Before you start

Ensure you have administrator access to the on-premises Exchange Server or Active Directory, as well as the necessary permissions to run Exchange Management Shell or Active Directory PowerShell commands.

Solution 1Recommended

Update ArchiveGuid using the Exchange Management Shell

Use this method if you still maintain an on-premises Exchange server to manage hybrid mailbox attributes.

In a standard hybrid configuration, the on-premises msExchArchiveGUID must perfectly match the Exchange Online archive GUID. You can correct mismatches by updating the RemoteUserMailbox properties.

1
Verify recipient details

Open the Exchange Management Shell and run 'Get-Recipient -Identity user@contoso.com | Format-List ArchiveGuid, RecipientTypeDetails' to check the current status.

2
Enable the remote archive

If the RecipientTypeDetails is RemoteUserMailbox and the ArchiveGuid is 0, run 'Enable-RemoteMailbox -Identity user@contoso.com -Archive'.

3
Set the ArchiveGuid to match the cloud

Run 'Set-RemoteMailbox -Identity user@contoso.com -ArchiveGuid <Cloud Archive GUID>' (replacing the placeholder with the actual Exchange Online GUID).

4
Allow directory synchronization

Wait for your Azure AD Connect sync cycle to complete before verifying the resolution in the Microsoft 365 admin center.

Update ArchiveGuid using the Exchange Management Shell
Routing Address Requirement: If the user is not recognized as a RemoteUserMailbox, you must first enable the remote mailbox with the correct remote-routing address before enabling the archive and setting the ArchiveGuid.
Free Microsoft Office alternative

Looking for a Reliable and Free Alternative to Microsoft Office?

While resolving Microsoft 365 hybrid configuration and Exchange server errors requires advanced administrative overhead, managing your day-to-day office documents shouldn't be complicated. WPS Office provides a free, lightweight, and incredibly intuitive alternative to Microsoft Office. Enjoy full access to powerful word processing, spreadsheets, and presentation tools without the heavy subscription fees.

  1. 1. Download the software: Get the free installer from the official WPS Office website.
  2. 2. Install and launch: Follow the quick installation steps and open the unified workspace.
  3. 3. Open existing files natively: Drag and drop your Microsoft Office files directly into WPS Office to continue working seamlessly.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx).Lightweight application that uses minimal system resources.Familiar tabbed user interface for a zero-learning-curve transition.Built-in PDF editor for comprehensive document management.
microsoft office alternative - wps office

Frequently Asked Questions

How do I find the Exchange Online archive GUID?

You can find the cloud archive GUID by connecting to Exchange Online PowerShell and running 'Get-Mailbox -Identity <User> | Select-Object ArchiveGuid'.

Why does this Archive GUID mismatch happen in hybrid environments?

This mismatch typically occurs when an in-place archive is enabled directly in Exchange Online rather than from the on-premises Exchange server, causing the cloud environment to generate a unique GUID that doesn't sync back to the local Active Directory.

How long does it take for directory synchronization to fix the archive error?

Azure AD Connect typically syncs changes every 30 minutes. If you want to push the changes immediately, run 'Start-ADSyncSyncCycle -PolicyType Delta' on your AD Connect server.