Quest incident

Production Incident - On Demand Migration for Teams Affected

Critical Resolved View vendor source →

Quest experienced a critical incident on July 16, 2022 affecting US Region and Australia Region and 1 more component, lasting 3h 21m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2022, 05:39 PM UTC
Resolved
Jul 16, 2022, 09:01 PM UTC
Duration
3h 21m
Detected by Pingoru
Jul 16, 2022, 05:39 PM UTC

Affected components

US RegionAustralia RegionCanada RegionEU RegionUK Region

Update timeline

  1. investigating Jul 16, 2022, 05:39 PM UTC

    We are aware of a potential issue that may impact some of the On Demand Migration for Teams customers in all regions. An investigation is currently underway and we will report back soon.

  2. resolved Jul 16, 2022, 09:01 PM UTC

    The issue that impacted On Demand Migration for Teams customers in all regions is resolved. For any active Teams migrations it is recommended to stop long running tasks. After stopping, please select Teams that are not completed and add them to a new migration task to run again. 100% completed Teams migration tasks do not need further processing and will slow down new migration tasks if resubmitted. We will continue to monitor our services. Quest will contact Microsoft for a root cause analysis as to why this issue appeared and then disappeared on its own. We have not seen a related report yet in the M365 admin center - message center.