Audience: Exchange Online/Office 365 administrators

Author: Ram Poornalingam, Senior Program Manager, Exchange

We’re updating the policy for inactive migration batches in Office 365 for organizations that haven’t yet been upgraded as part of the 2013 service upgrade. Previously, active migration batches with a status of “Synced” that have no administrator-initiated activity for the last 90 days were stopped, and then deleted 30 days later if no further activity is taken by the administrator. What constitutes activity by the administrator?

• Stopping and restarting a migration batch
• Editing a migration batch by using the Exchange Control Panel or the Set-MigrationBatch cmdlet in Windows PowerShell.

How do we determine if a migration batch is inactive? There is a “Last modified time” property for migration batches, and if the value for this property is more than 90 days, the batch is stopped. If the batch remains inactive for another 30 days (in other words, when the value of this property reaches 120 days), the migration batch is deleted.

Here’s a table comparing the current and new policy for inactive migration batches:

This updated policy for inactive migration batches applies to all migration types: Cutover Exchange migrations, staged Exchange migrations, and IMAP migrations.

Why are we changing the policy for inactive migration batches? We can’t upgrade your organization to the 2013 service update if you have migration batches that are running. By deleting inactive migration batches sooner, we can start the upgrade process for your organization.

For more information about migration, see the following topics on help.outlook.com:

• Manage Migration Batches in Exchange Online
• Cutover Exchange migration
• Staged Exchange migration
• IMAP migration

Image may be NSFW.
Clik here to view.