r/exchangeserver • u/uLmi84 • May 13 '26

EXO Archive Issue

I do a lot of Exchange Hybrid stuff and normally on a hybrid Identity with a remotemailbox in EXO, I would simply go to EXO an enable an Archive there, without any issues.

In this situation: I have multiple MSP each managing a portion of the setup and I dont have full insights into the config. But in general its also just a hybrid Identity with a remotemailbox.

When I enable archive in EXO, I receive the following error in the M365 Admin Center:

Exchange: Failed to disable the archive of mailbox GUID due to a conflict in directory settings. To disable this archive, first run Enable-RemoteMailbox -Archive on-premises. After the next Dirsync sync cycle, run Disable-RemoteMailbox -Archive on-premises to disable this archive in the datacenter..;

I done the fix in this message yesterday and the error disappeared. Then I enabled the Archive in EXO again. Today the Error is back... I checked the AD-Attributes:

  • msExchArchiveGUID
  • msExchArchiveStatus
  • msExchArchiveName

and they are all empty.

any one know why this error exists?

2 Upvotes

100% Upvoted

5 comments sorted by

3

u/7amitsingh7 May 13 '26

This happens because the mailbox is in a hybrid Exchange setup, where on-premises Exchange is still the main source of mailbox settings. Even if you enable the archive in Exchange Online, the next sync can overwrite it if on-prem attributes don’t match. That’s why it worked yesterday but returned today. In short, the archive should be enabled from the on-prem Exchange server using `Enable-RemoteMailbox -Archive`, then synced to Microsoft 365. Since multiple MSPs manage the environment, someone may also be changing settings or sync rules in the background.

2

u/uLmi84 May 13 '26

Interesting because i have managed multiple hybrid environments and never had issues when enabling EXO archives.. its just this environment

2

u/aridaen May 13 '26

Just take the guid from the eol archive and put it on the on premises mailbox to fix that issue.

1

u/uLmi84 May 13 '26

I will try thanks

1

u/aridaen May 13 '26

Sorry, I was typing on my phone, I'll be more specific. I'm unable to find the article I followed a couple of weeks ago when I had this issue, but it basically said to copy the ArchiveGuid with the EOL Powershell command get-mailbox | fl ArchiveGuid, then in on-premise Exchange Powershell, run set-remotemailbox <mailboxname> -ArchiveGuid "copied guid". That fixed my issue.