BitTitan incident

Microsoft 365 Mailbox migrations intermittent failure

Minor Resolved View vendor source →

BitTitan experienced a minor incident on August 25, 2022 affecting MigrationWiz, lasting 6d 8h. The incident has been resolved; the full update timeline is below.

Started
Aug 25, 2022, 12:20 PM UTC
Resolved
Aug 31, 2022, 09:16 PM UTC
Duration
6d 8h
Detected by Pingoru
Aug 25, 2022, 12:20 PM UTC

Affected components

MigrationWiz

Update timeline

  1. investigating Aug 25, 2022, 12:20 PM UTC

    We are currently investigating Microsoft 365 Mailbox migrations fail intermittently with "Error: ErrorInternalServerError".

  2. identified Aug 25, 2022, 01:32 PM UTC

    The issue has been identified to cause due to the Microsoft 365 tenant EWS response, the developer is working with Microsoft support.

  3. identified Aug 26, 2022, 03:22 PM UTC

    Issue Description: Microsoft 365 Mailbox migrations are experiencing intermittent issues that return the error: `Your migration failed while checking destination credentials. An internal server error occurred. The operation failed. Error: ErrorInternalServerError. Destination Server`` when starting a migration Affected customers: Mailbox migrations with “Microsoft 365” (Exchange Online) as the Source or Destination endpoint. Current status: The issue is due to the Microsoft 365 tenant EWS response. Our teams are currently working with Microsoft Support to resolve the issue. Potential workaround: This is a transient issue. Resubmitting the migration may solve the issue.

  4. monitoring Aug 28, 2022, 04:12 AM UTC

    The Microsoft 365 mailbox migration error "Error: ErrorInternalServerError" observed to be transient and likely self resolved at Microsoft end. The workaround to reset and resubmit the migrations helped customer who reported the error. We will continue to monitor the issue while working with the Microsoft support.

  5. resolved Aug 31, 2022, 09:16 PM UTC

    The Microsoft 365 mailbox migration error "Error: ErrorInternalServerError" isn't observed anymore. The issue is now marked as resolved.