Dragon Systems incident

Possible DAX/Dragon Copilot Impact

Notice Resolved View vendor source →

Dragon Systems experienced a notice incident on April 28, 2026 affecting DAX Copilot for DMO - Summary Availability and DAX Copilot Mobile - Summary Availability and 1 more component, lasting 6d. The incident has been resolved; the full update timeline is below.

Started
Apr 28, 2026, 02:25 PM UTC
Resolved
May 04, 2026, 02:51 PM UTC
Duration
6d
Detected by Pingoru
Apr 28, 2026, 02:25 PM UTC

Affected components

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

Update timeline

  1. identified Apr 28, 2026, 02:25 PM UTC

    Microsoft has identified and is actively troubleshooting a recurrence of an issue affecting Dax/Dragon Copilot products. Symptoms may include: -- delayed summaries -- auto styling failures More details will be provided when information is available. We apologize for any inconvenience and appreciate your continued partnership as we work to resolve this issue.

  2. identified Apr 28, 2026, 03:39 PM UTC

    There was a brief issue yesterday impacting auto styling for a small subset of DAX and Dragon Copilot customers. There was a brief reoccurrence of that same issue today, which has been quickly remediated. Some end users may have experienced delay summaries as a related impact. We are seeing improvements in system stability, and we will continue to closely monitor to confirm improved behavior. We apologize for any inconvenience and appreciate your continued partnership while we worked to resolve this issue.

  3. monitoring Apr 28, 2026, 03:41 PM UTC

    There was a brief issue yesterday impacting auto styling for a small subset of DAX and Dragon Copilot customers. There was a brief reoccurrence of that same issue today, which has been quickly remediated. Some end users may have experienced delay summaries as a related impact. We are seeing improvements in system stability, and we will continue to closely monitor to confirm improved behavior. We apologize for any inconvenience and appreciate your continued partnership while we worked to resolve this issue.

  4. resolved May 04, 2026, 02:51 PM UTC

    This incident has been resolved.