Nuance incident

Possible DAX/Dragon Copilot Impact

Notice Resolved View vendor source →

Nuance experienced a notice incident on July 2, 2026 affecting DAX Copilot Mobile - Login and DAX Copilot for DMO - Login and 1 more component, lasting 13h 3m. The incident has been resolved; the full update timeline is below.

Started
Jul 02, 2026, 04:18 AM UTC
Resolved
Jul 02, 2026, 05:22 PM UTC
Duration
13h 3m
Detected by Pingoru
Jul 02, 2026, 04:18 AM UTC

Affected components

DAX Copilot Mobile - LoginDAX Copilot for DMO - LoginDAX Copilot Mobile - Audio UploadDAX Copilot for DMO - Summary AvailabilityDAX Copilot for Epic - Audio RecordingDAX Copilot Mobile - Summary AvailabilityDAX Copilot for DMO - Summary EditingDAX Copilot for Epic - Summary Generation & Delivery

Update timeline

  1. identified Jul 02, 2026, 04:18 AM UTC

    Microsoft has identified and is actively troubleshooting an issue affecting Dax/Dragon Copilot products within our US datacenter. More details will be provided when information is available.

  2. monitoring Jul 02, 2026, 05:15 AM UTC

    Microsoft has identified and mitigated a service disruption in our US Data Center affecting Dragon and DAX Copilot customers. Symptoms may have included Unable to login to DAX Copilot Error message stating "Unable to launch DAX Copilot" Error message stating "Dragon Copilot is currently unavailable" Our engineering teams will continue to closely monitor the service to ensure stability . We apologize for any inconvenience and appreciate your continued partnership

  3. monitoring Jul 02, 2026, 05:52 AM UTC

    Microsoft has identified and mitigated a service disruption in our US Data Center affecting Dragon and DAX Copilot customers. Symptoms may have included Unable to login to DAX Copilot Error message stating "Unable to launch DAX Copilot" Error message stating "Dragon Copilot is currently unavailable" Our engineering teams are continuing to closely monitor the service to ensure stability and that all impacted audio is successfully reprocessed. At this time all services are returned to normal. Note: Users who were already logged in, we recommend logging out and back in to ensure optimal application performance We apologize for any inconvenience and appreciate your continued partnership

  4. resolved Jul 02, 2026, 05:22 PM UTC

    This incident has been resolved.