exchangerecovery

Throttling in Microsoft 365 and Office 365

Microsoft 365 and Office 365 employ various throttling mechanisms in order to ensure service availability and security. These throttling mechanisms can impact migration performance.

Throttling of Office 365 and Microsoft 365 users

Third-party tools for migrating clients and client uploading are affected by user throttling. These methods use client access protocols such as Remote Procedure Call (RPC over HTTP Protocol) to migrate mailbox data into Microsoft 365 and Office 365 mailboxes. These tools can be used to migrate data from platforms like IBM Lotus Domino or Novell GroupWise.

Microsoft 365 and Office 365 have the most restrictive throttling methods, with user throttling being the most restrictive. User throttling works against an individual user and will result in slow data migration.

Related resources:

Exchange 2010 to Office 365 Migration|Exchange 2013 to Office 365 Migration| Exchange 2016 to Office 365 Migration|Exchange 2019 to Office 365 Migration|Exchange 2010 to exchange 2016 Migration|Exchange 2010 to Exchange 2019 Migration|Exchange 2013 to exchange 2016 migration| Exchange 2013 to Exchange 2019 migration|Migrate Exchange 2016 to 2019

Microsoft 365 and Office 365 resource health-based throttling

All migration methods must be subject to the governance of availability throttle. However, Microsoft 365 and Office 365 service throttling doesn’t affect Microsoft 365 and Office 365 migrations in the same way as other types of throttling.

Resource health-based throttle is the most aggressive method of throttling. This is done to prevent service availability issues that could impact end-users or critical service operations.

Hybrid migrations will not be allowed to proceed until the service’s performance has stabilized and is back below the threshold.

These are some examples taken from an Exchange migration statistics report. These are the entries that were logged when the threshold for service-throttling was exceeded.

Export Exchange mailbox to PST| Export Exchange 2010 mailbox to PST

Export Exchange 2007 mailbox to PST| Export public folder to pst | Exchange database recovery | new-mailboxexportrequest | Exchange server recovery | on-premises exchange vs office 365 | Repair Exchange 2013 database | eseutil | migrate distribution lists to office 365 | Office 365 Migration steps | Repair Exchange 2016 database | new-moverequest | Exchange Recovery