New Policy for Inactive Migration Batches

Audience: Exchange Online/Office 365 administrators Author: Ram Poornalingam, Senior Program Manager, Exchange   We’re implementing a new policy for migration batches in the cloud-based service. Active migration batches with a status of “Synced” that have no administrator-initiated activity for the last 90 days will be 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.   This new policy applies to all migration types: Cutover Exchange migrations, staged Exchange migrations, and IMAP migrations.   Why are we doing this? Inactive migration batches consume resources in the Microsoft datacenter. By stopping and then deleting these batches, we can free up resources and help improve the migration experience for customers who are actively migrating mailboxes to Office 365.   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

Read the rest here:
New Policy for Inactive Migration Batches


Leave a comment!

You must be logged in to post a comment.