Troubleshoot Exchange Server Hybrid MRM and Cloud Archive Errors
Question details
Determine why Exchange Server cannot provision a cloud archive or process a Messaging Records Management policy in a hybrid environment that uses a proxy for Internet access.
- Product
- Microsoft Exchange Server and Exchange Online in a hybrid deployment
- Device & OS
- not provided
- Scenario
- An on-premises mailbox uses, or needs, an Exchange Online archive while the Exchange server reaches Microsoft 365 through a proxy server.
- Observed behavior
- Cloud archive provisioning or MRM policy processing may fail. The record does not identify a specific error message or establish which operation is failing.
Identify the affected mailbox, Exchange Server version and cumulative update, assigned retention policy, and exact error message. Use an account with the appropriate Exchange administrative permissions and confirm whether the cloud archive is missing or already provisioned.
Identify whether archive provisioning or MRM processing is failing
Use this first to separate two operations that require different troubleshooting paths.
In the on-premises Exchange Management Shell, run Get-Mailbox -Identity <mailbox> | Format-List DisplayName,ArchiveStatus,ArchiveState,ArchiveGuid,ArchiveDomain,RetentionPolicy. Replace <mailbox> with the affected mailbox identity and record the results.
In the Exchange Online admin center, inspect the corresponding recipient and archive status. Compare the cloud-side archive information with the on-premises mailbox information; do not treat an unprovisioned archive as an MRM processing failure.
In the on-premises Exchange Management Shell, run Get-RetentionPolicy -Identity <policy-name> | Format-List Name,RetentionPolicyTagLinks. Review the linked tags with Get-RetentionPolicyTag and confirm that applicable tags use the MoveToArchive action.
Verify cloud archive prerequisites and proxy connectivity
Use this when the archive is not provisioned or Exchange cannot reach Microsoft 365 through the required proxy.
Test MRM processing after the cloud archive is available
Use this when the archive exists but eligible mailbox items are not moving into it.
Document Exchange Troubleshooting with WPS Office
WPS Office cannot fix Exchange hybrid connectivity or manage cloud archives. For preparing troubleshooting reports and tracking proxy checks, it offers a free, lightweight, easy-to-use alternative to Microsoft Office with a familiar interface and support for existing Office files, making document migration straightforward.

Frequently Asked Questions
Does creating a cloud archive also run the MRM retention policy?
No. Archive provisioning and MRM processing are separate operations. Confirm that the archive exists, inspect the mailbox's assigned policy with Get-Mailbox, and use Get-RetentionPolicyTag to verify the applicable MoveToArchive tags.
Which proxy settings should I check on the Exchange server?
Review the Exchange InternetWebProxy setting with Get-ExchangeServer, the Windows WinHTTP configuration with netsh winhttp show proxy, and Internet Options settings where present. These settings can differ, so check which connection path the failing operation actually uses.
Why are messages not moving even though the archive exists?
Items may not meet the retention age, may have overriding tags, or may be affected by RetentionHoldEnabled or ElcProcessingDisabled. Inspect the policy and mailbox settings, then request processing with Start-ManagedFolderAssistant on the server hosting the primary mailbox.
Will updating Exchange automatically resolve the failure?
Not necessarily. Verify and apply a supported cumulative update and applicable security updates, but also check archive prerequisites, proxy access, and logs. Retest the specific failed operation after the update rather than assuming it fixed the cause.
Can WPS Office repair Exchange cloud archive or MRM errors?
No. Those issues require Exchange administrative tools and network configuration checks. WPS Writer and WPS Spreadsheet can help organize diagnostic reports and test results, but they do not manage Exchange mailboxes, archives, or retention policies.




