Inability to solve the "Exchange: Failed to sync the ArchiveGuid 00000000..." problem in Entra ID Connect

Question

The company migrated from on-prem Exchange to 365/ExO three years ago.

A couple of months ago, one of the users asked to change some information about themselves, like office phone number etc.

But, this turned out to be impossible to complete due to errors like "Exchange: Failed to sync the ArchiveGuid 00000000-0000-0000-0000-000000000000 of mailbox ... because one cloud archive ... exists".

Standard methods for solving the problem in the form of editing fields "msExchArchiveGUID", "msExchArchiveName", "msExchRecipientDisplayType", "msExchRecipientTypeDetails" and "msExchRemoteRecipientType" did not help.

I also tried to break the AAD Connect synchronization by moving the user to the OU out of synchronization and removing his cloudAnchor attribute, but this did not help. And in addition, this user, even being purely cloud-based, still had the same error (in the screenshot).
It’s interesting that the user’s mailbox continues to work normally despite the "We are preparing a mailbox for the user" message.
The company has several dozen users with a similar problem, I tested it on two of them.
Both these users do not have any 365 admin roles.
Sync rules in AAD Connect look like standard ones. They are difficult to compare, but I compared them with a freshly installed AAD Connect service in a test environment and they are visually the same.

Unfortunately, the old on-prem Exchange was completely removed for a long time, so editing attributes via the EAC is no longer available.

I tried to use Microsoft support, but after a couple of weeks of reviewing the ticket, MS eventually refused to resolve the problem, citing the lack of on-prem Exchange, as officially recommended.

I wonder how this could have helped if three years ago the company had completely abandoned the on-prem infrastructure and what could have been done if three years ago users had been completely migrated to the 365/Entra ID native.

This problem looks like something related to a synchronization error on the MS backend side.

I am attaching several screenshots and articles according to which I tried to solve the problem.
If anyone can help with advice I would be very grateful.

Answer 1

Typically you fix this by enabling the 365 online archive on-prem from Exchange and once that syncs to Exchange Online, everything good.

Does the EXo mailbox have anythign set for :ArchiveGuid or DisabledArchiveGuid?

If so, you may be able to copy that value to the on-prem MsExchArchiveGUID and let it sync

Answer 2

Hi @Allan Stark

Here is a link which have a detailed guide on this issue:

How to fix Office365 user provisioning issues that are generated by faulty Exchange attributes

Since you no longer have an on-premises Exchange server, please refer to Scenario 2:

However, you might want to use below steps, if you have only few users affected:

a) From a domain controller, open Active Directory PowerShell and run first:

 Import-Module ActiveDirectory

b) Run below command to store the cloud archiveguid in a variable:

 [guid]$guid = "Value of the cloud archiveGUID"

c) Set the ArchiveGUID property on the affected user:

get-Aduser “UserAlias” | set-aduser -Replace @{msExchArchiveguid=$guid.tobytearray()}

---

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.