Good morning! Environment is on-prem Ex2016 CU20 DAG with some in-place archives on some mailboxes. No litigation holds on any accounts being discussed; migrations completed last year, archives are readily accessible with Outlook and OWA. Clients have valid licenses assigned (E3).
All user mailboxes that we've migrated successfully to EO with active, valid in-place archives all have the ArchiveState (according to EAC) as "HostedPending".
* Both migrated users in EAC (on-prem) had an Archive Status of "HostedPending", with the state of the AD property "msExchArchiveStatus" as "<not set>". I've since changed the "msExchArchiveStatus" on one account to "1", and the Archive Status in EAC has changed to "HostedPending" on that one modified account.
In Powershell (Exchange Online module loaded) both users have "ArchiveStatus" as "None", and "Archive State" as "Local". (I'm assuming that "Local" is referring to when they archives were actually hosted on-prem originally).
In Powershell (Exchange Online module loaded) when I attempt "enable-remotemailbox <user> -Archive" I get an error indicating the recipient already has an archive.
In EO Admin center, the "Manage Mailbox Archive" option is disabled, and enabling it return the error "Recipient <userID> already has an archive".
Again, all archives are accessible via Outlook and OWA, but our backup agent (Veeam VBO) cannot see the archives to back them up. I've since migrated another account WITHOUT an in-place archive, then enabled the in-place archive on that account and it's working as expected (including backups).
Suggestions? Thanks.
SteveInReno

