Do you know MigrationWiz does not use a single API path for every workload, and that the throttling behavior you encounter depends heavily on which path it is using?

BitTitan has been steadily shifting MigrationWiz workloads away from Exchange Web Services and toward Microsoft Graph API. For migration engineers, EWS throttling and Graph API throttling behave differently, and your response needs to match what you are actually hitting.

In Exchange Online, EWS throttling is enforced through Exchange-specific service protection policies applied to the migration service account. When those limits trigger, MigrationWiz receives a back-off response and reduces its request rate. Graph API throttling comes from Microsoft broader app-level throttling framework, with different token bucket sizes and retry-after response headers.

In most MigrationWiz job types, mailbox migrations still primarily run through EWS, while OneDrive for Business migrations primarily run through Graph API. The item-level report will reflect this difference: an EWS throttling error does not look the same as a Graph API 429 response. Mixing them up leads to the wrong fix. EWS throttling is typically addressed by reducing concurrency, whereas Graph API throttling may require reducing request frequency instead.

Do you know which API path each of your MigrationWiz workload types is using, and does your throttling remediation process reflect that reality?

#BitTitan #MigrationWiz