Dragon Systems incident

DAX/Dragon Copilot Impact - Delays in note generation

Notice Resolved View vendor source →

Dragon Systems experienced a notice incident on March 9, 2026 affecting DAX Copilot for DMO - Summary Availability and DAX Copilot Mobile - Summary Availability and 1 more component, lasting 2h 46m. The incident has been resolved; the full update timeline is below.

Started
Mar 09, 2026, 12:25 PM UTC
Resolved
Mar 09, 2026, 03:11 PM UTC
Duration
2h 46m
Detected by Pingoru
Mar 09, 2026, 12:25 PM UTC

Affected components

DAX Copilot for DMO - Summary AvailabilityDAX Copilot Mobile - Summary AvailabilityDAX Copilot for Epic - Summary Generation & Delivery

Update timeline

  1. investigating Mar 09, 2026, 12:25 PM UTC

    Microsoft is aware of an event is actively troubleshooting an issue affecting DAX/Dragon Copilot products within our US datacenter. Symptoms- Delays in note generation. More details will be provided when information is available.

  2. identified Mar 09, 2026, 12:34 PM UTC

    Microsoft is aware of an event and is actively troubleshooting an issue affecting DAX/Dragon Copilot products within our US datacenter. Symptoms- Delays in note generation. More details will be provided when information is available.

  3. identified Mar 09, 2026, 01:38 PM UTC

    Microsoft has identified and is actively working towards the remediation on an issue affecting DAX/Dragon Copilot products within our US and CA datacenters. Symptoms: -Sporadic delays in note generation. More details will be provided when information is available. Thank you for your patience and understanding while we work to resolve this issue.

  4. monitoring Mar 09, 2026, 02:35 PM UTC

    Microsoft has remediated an issue affecting DAX/Dragon Copilot products within our US and CA datacenters. Symptoms may have included: -Sporadic delays in note generation. Microsoft will continue to closely monitor system performance to validate the effectiveness of these mitigation actions and will provide additional updates as they become available. Note: Encounters recorded during the incident window will require reprocessing by our engineering team. We will share additional updates on the scope and expected timelines for this recovery effort in a follow up communication. Potential workaround for time-sensitive notes: -Adding a short, non-silent recording to the encounter may trigger delivery of the summary. We apologize for any inconvenience and appreciate your continued partnership as we worked to resolve this issue.

  5. resolved Mar 09, 2026, 03:11 PM UTC

    This incident has been resolved.