Microsoft 365 Migration

How to Resolve Cloud-Based Archive Pending in Exchange 2010 Before Removal

Muhammad TalhaMuhammad Talha Nov 2, 2026 870 views

Question details

The user needs to resolve a 'Cloud-based archive pending' status in Exchange 2010 to allow database removal and server decommissioning after migrating to Microsoft 365.

How to Resolve Cloud-Based Archive Pending in Exchange 2010 Before Removal
Product
Microsoft Exchange 2010
Device & OS
not provided
Scenario
Migrating mailboxes and archives to Microsoft 365 in a hybrid Exchange environment.
Observed behavior
Exchange 2010 incorrectly displays 'Cloud-based archive pending', which blocks administrators from removing databases and decommissioning the legacy Exchange 2010 server.
Before you start

Ensure you have full administrative access to both your on-premises Exchange 2010 server and Microsoft 365 tenant, and verify that the target archives have actually completed migration to the cloud.

Solution 1Recommended

Verify Azure AD Connect Exchange Hybrid Settings and Force Sync

Enable the Exchange Hybrid deployment feature in Azure AD Connect and force a directory synchronization to update archive statuses.

Often, the on-premises Exchange server is unaware that the cloud migration is complete because the hybrid deployment features in Azure AD Connect are not properly syncing the required Exchange attributes.

1
Check Azure AD Connect Configuration

Open Azure AD Connect on your primary sync server, navigate to the optional features configuration, and verify that the 'Exchange Hybrid deployment' feature is checked and enabled.

2
Force Directory Synchronization

Open PowerShell as an Administrator on the Azure AD Connect server and run the command 'Start-ADSyncSyncCycle -PolicyType Delta' to force an immediate directory synchronization.

3
Verify Archive Status

After the synchronization completes, check your Exchange 2010 management console to see if the pending archive status has cleared and allows database removal.

Verify Azure AD Connect Exchange Hybrid Settings and Force Sync
Check Exported Configuration: You can export the Azure AD Connect configuration to confirm that 'exchangeOnlineFeaturePolicy' has 'hybridDeployment' set to true.
Free Microsoft Office alternative

Simplify Your Workflow with WPS Office After Microsoft 365 Migration

While managing complex Exchange server decommissioning, give your team a seamless, lightweight, and cost-effective productivity suite. WPS Office provides enterprise-grade tools with zero learning curve.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install the Suite: Run the lightweight installer and follow the on-screen instructions to deploy WPS Office on your computer.
  3. 3. Open Microsoft Formats: Launch WPS Office and directly open your existing Word, Excel, and PowerPoint files without needing any format conversion.
Highly compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Cost-effective solution for enterprises optimizing their IT budget after extensive cloud migrations.Lightweight installation with a familiar, easy-to-use tabbed interface.Includes a robust PDF editor for comprehensive document management across your organization.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Exchange 2010 prevent database removal when archives are pending?

Exchange safeguards data by preventing the deletion of databases that it believes still contain active mailboxes or pending archive migrations, avoiding accidental data loss.

What does an msExchRemoteRecipientType value of 6 mean?

In a hybrid Exchange environment, a value of 6 for the msExchRemoteRecipientType attribute indicates that the user's archive has been successfully provisioned and migrated to the cloud.

Do I still need Azure AD Connect after decommissioning Exchange 2010?

Yes, if you plan to continue syncing on-premises Active Directory identities to Microsoft Entra ID (formerly Azure AD), Azure AD Connect is still required even after the legacy Exchange servers are decommissioned.