Nuance Outage History

Started Apr 01, 2026, 05:04 PM UTC· resolved Apr 02, 2026, 05:26 PM UTC

1. identified Apr 01, 2026, 05:04 PM 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. investigating Apr 01, 2026, 05:44 PM UTC

   Microsoft is investigating a service disruption in our US Data Center affecting a subset of DAX Copilot customers. Symptoms may include: - Delays in encounter uploads. - Delayed availability of summaries. - Error messages indicating that a visit recording could not be started. Our engineering teams are actively working to identify the root cause and mitigate impact. We will provide additional updates as they become available. We apologize for any inconvenience and appreciate your continued partnership while we work to return to normal service levels as quickly as possible.

3. investigating Apr 01, 2026, 06:29 PM UTC

   Microsoft has stabilized service performance for Dragon/DAX Copilot in our US Data Center. Microsoft will continue to investigate root cause and monitor the environment closely. Encounters recorded during the impacted timeframe are expected to recover automatically.

4. monitoring Apr 01, 2026, 07:25 PM UTC

   Microsoft has stabilized service performance for Dragon/DAX Copilot in our US Data Center and the environment is operating normally. We will continue to closely monitor the service while completing our root cause investigation to ensure continued stability. Encounters recorded during the impacted timeframe are expected to recover automatically. We apologize for any inconvenience and appreciate your continued partnership.

5. resolved Apr 02, 2026, 05:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 23, 2026, 02:45 PM UTC· resolved Mar 24, 2026, 02:33 PM UTC

1. identified Mar 23, 2026, 02:45 PM UTC

   The PMM/DAX Copilot Mobile application is encountering an issue with presenting multiple identity providers. Engineering team is currently working to remediate the issue. During this time, if you are manually updating your product, it is advised to NOT update to 6.0.16

2. identified Mar 23, 2026, 03:52 PM UTC

   The issue with PMM/DAX Copilot Mobile application has been identified and a remediation effort is underway. Another update is expected this afternoon at approximately 2:30pm ET. At this time, if you are manually updating your product, it is advised to NOT update to 6.0.16

3. identified Mar 23, 2026, 06:43 PM UTC

   As remediation, Microsoft has created an updated version of the PMM/DAX Copilot mobile application and submitted it to Apple for approval. Once this has been approved and is available for download we will update this status. At this time, if you are manually updating your product, it is advised to NOT update to 6.0.16

4. monitoring Mar 24, 2026, 12:06 PM UTC

   Updated version of the application has been released as of 8pm ET on 3/23/2026. Version 6.0.17 It is suggested that those utilizing their own identity providers for login take this update to remediate the issue previously encountered.

5. resolved Mar 24, 2026, 02:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2026, 06:01 PM UTC· resolved Mar 12, 2026, 07:00 PM UTC

1. investigating Mar 12, 2026, 06:01 PM UTC

   Microsoft is investigating an issue reported that summaries are not delivering for DAX/Dragon Copilot products within our US datacenters. Impact at this time appears to be isolated to a few Copilot for Epic and specifically Nebula customers. Symptoms may include: -Summary delivery failing We will provide more information as it becomes available. We apologize for any inconvenience and appreciate your continued partnership as we worked to resolve this issue.

2. resolved Mar 12, 2026, 07:00 PM UTC

   Microsoft has partnered with Epic to identify and take corrective action for the issue previously reported where summaries were not delivering for DAX/Dragon Copilot products within our US datacenters. At this time the issue is considered resolved with an expected backlog of summaries to be completed within the hour. Impact was isolated to a few Copilot for Epic and specifically Nebula customers. Symptoms may have included: -Summary delivery failing We apologize for any inconvenience and appreciate your continued partnership.

Read the full incident report →

Started Mar 09, 2026, 12:25 PM UTC· resolved Mar 09, 2026, 03:11 PM UTC

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.

Read the full incident report →

Started Feb 19, 2026, 02:37 PM UTC· resolved Feb 19, 2026, 02:38 PM UTC

1. investigating Feb 19, 2026, 02:37 PM UTC

   testing, immediate resolve

2. resolved Feb 19, 2026, 02:38 PM UTC

   resolving test

Read the full incident report →

Started Feb 19, 2026, 01:01 PM UTC· resolved Feb 19, 2026, 02:02 PM UTC

1. investigating Feb 19, 2026, 01:01 PM UTC

   testing status page activities, no product status change or impact

2. identified Feb 19, 2026, 01:07 PM UTC

   test identified status

3. monitoring Feb 19, 2026, 01:17 PM UTC

   Monitor status check

4. resolved Feb 19, 2026, 02:02 PM UTC

   resolved status test

Read the full incident report →

Started Feb 12, 2026, 01:30 PM UTC· resolved Feb 17, 2026, 01:03 PM UTC

1. investigating Feb 12, 2026, 01:30 PM UTC

   Microsoft continues to work closely with Azure OpenAI to address this issue. Azure OpenAI has completed a rollback of recent changes identified as the root cause, and we are observing early signs of improvement. The issue impacted note processing due to a dependent global outage affecting certain Azure OpenAI workflows. This has now been remediated across all model regions used by DAX Copilot and Dragon Copilot, and note processing has resumed normal operation. 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. Potential workaround for time-sensitive notes: - Adding a short, non-silent recording to the encounter may trigger delivery of the summary. 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. We apologize for any inconvenience and appreciate your continued partnership as we worked to resolve this issue.

2. investigating Feb 12, 2026, 09:07 PM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 12, 2026, 10:12 PM UTC

   DAX Copilot and Dragon Copilot note processing have returned to normal for new encounters. 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. Potential workaround for time-sensitive notes: - Adding a short, non-silent recording to the encounter may trigger delivery of the summary. 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 on the morning of February 13, 2026. We apologize for any inconvenience and appreciate your continued partnership as we worked to resolve this issue.

4. monitoring Feb 13, 2026, 02:30 PM UTC

   The reprocessing effort referenced in our previous communication is progressing as planned and is approximately 90% complete. A final update will be provided once reprocessing is fully finished. 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 work toward full recovery of impacted summaries.

5. resolved Feb 17, 2026, 01:03 PM UTC

   The incident has been resolved

Read the full incident report →

Started Feb 03, 2026, 03:01 PM UTC· resolved Feb 03, 2026, 05:49 PM UTC

1. investigating Feb 03, 2026, 03:01 PM UTC

   Microsoft has identified an issue impacting a backend service that processes our auto styling of DAX/Dragon Copilot notes. As a result, notes may be delivered without the auto styling applied to the note. Actions have been taken to remediate this issue, and performance appears to be improving. We will continue to monitor, and we will confirm once the issue is fully resolved. Additionally, we are investigating a separate issue which may be impacting note delivery. We do not believe that these issues are related at this time. The note delivery issues are being investigated with a high priority. Further updates will be provided as once we know more. We apologize for the inconvenience and appreciate your partnership while we work to return to normal service levels as quickly as possible.

2. identified Feb 03, 2026, 04:04 PM UTC

   Microsoft has identified an issue impacting a backend service that processes our auto styling of DAX/Dragon Copilot notes. As a result, notes may be delivered without the auto styling applied to the note. Actions have been taken to remediate this issue, and performance appears to be improving. We will continue to monitor, and we will confirm once the issue is fully resolved. Additionally, we are investigating a separate issue which may be impacting note delivery. We do not believe that these issues are related at this time. The note delivery issues are being investigated with a high priority. Further updates will be provided as once we know more. We apologize for the inconvenience and appreciate your partnership while we work to return to normal service levels as quickly as possible.

3. identified Feb 03, 2026, 05:03 PM UTC

   Microsoft continues to investigate the issue impacting a backend service that processes our auto styling of DAX/Dragon Copilot notes. As a result, notes may be delivered without the auto styling applied to the note. Actions have been taken to remediate this issue, and performance appears to be improving. We will continue to monitor, and we will confirm once the issue is fully resolved. We will send a separate communication once this issue has been confirmed to be fully resolved. As previously reported, we were investigating a separate issue which may be impacting note delivery. We have now confirmed that a subset of Epic Nebula users on DAX/Dragon Copilot are experiencing note delivery issues. This has been determined to be unrelated to the auto styling issue. Please note that the ambient encounters have been preserved and will be reprocessed. Remediation actions are in progress for the note delivery issues, and we will provide a separate update on this issue. We apologize for the inconvenience and appreciate your partnership while we work to return to normal service levels as quickly as possible.

4. resolved Feb 03, 2026, 05:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 20, 2026, 05:25 PM UTC· resolved Jan 20, 2026, 07:55 PM UTC

1. identified Jan 20, 2026, 05:25 PM UTC

   Microsoft is currently investigating a potential impact on timely summary deliver for some DAX/Dragon Copilot customers. More details will be provided as it is available from the investigation.

2. identified Jan 20, 2026, 06:06 PM UTC

   We are continuing to investigate.

3. identified Jan 20, 2026, 07:09 PM UTC

   DAX Copilot for DMO customers/users: • Remediation actions have been taken for today's incident, and we are seeing improvement in performance. • We will continue to monitor closely. DAX Copilot for Epic Nebula customers/users: • Remediation actions have been taken for today's incident, and we are seeing improvement in performance. • We will continue to monitor closely. DAX Copilot for Epic Interconnect customers/users: • We continue to investigate delays in summary delivery from today's incident.

4. resolved Jan 20, 2026, 07:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 20, 2026, 12:33 AM UTC· resolved Jan 20, 2026, 02:47 PM UTC

1. monitoring Jan 20, 2026, 12:33 AM UTC

   DAX Copilot for Epic delivery services have returned to normal for all new encounters recorded after 6:30 PM Eastern on January 19, 2026. For encounters recorded during the incident window on January19, 2026, most will be automatically reprocessed overnight. However, some encounters may require manual reprocessing by our engineering team. We will share additional updates on the scope and expected timelines for this manual recovery effort in a follow up communication tomorrow morning.

2. resolved Jan 20, 2026, 02:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 19, 2026, 08:52 PM UTC· resolved Jan 20, 2026, 12:22 AM UTC

1. identified Jan 19, 2026, 08:52 PM UTC

   Microsoft is investigating a potential issue affecting summary delivery for some DAX Copilot for Epic customers. More details will be provided when information is available.

2. identified Jan 19, 2026, 10:01 PM UTC

   Microsoft continues to investigate an issue affecting summary delivery for some DAX Copilot for Epic customers. Please continue to use the application at this time. All summaries are expected to deliver as expected.

3. identified Jan 19, 2026, 11:14 PM UTC

   Microsoft continues to investigate a service disruption in our US Data Center affecting the timely delivery of summaries for a subset of DAX Copilot for Epic customers. Symptoms may include: • Delayed availability of summaries within Epic • Summaries stuck uploading • Warning message: "You are recording for this patient with DAX Copilot, but you are not in their chart." All summaries are expected to deliver as expected. If you are able to open sidecar and see summary content, but not seeing content in Epic you may apply normal troubleshooting steps of removing and then re-adding the ambient Smart Sections. Additionally, if needed urgently you may also copy/paste from sidecar and place into Epic.

4. identified Jan 20, 2026, 12:17 AM UTC

   DAX Copilot for Epic delivery services have returned to normal for all new encounters recorded after 6:30 PM Eastern on January 19, 2026. For encounters recorded during the incident window on January19, 2026, most will be automatically reprocessed overnight. However, some encounters may require manual reprocessing by our engineering team. We will share additional updates on the scope and expected timelines for this manual recovery effort in a follow up communication tomorrow morning.

5. identified Jan 20, 2026, 12:19 AM UTC

   We are continuing to work on a fix for this issue.

6. identified Jan 20, 2026, 12:20 AM UTC

   We are continuing to work on a fix for this issue.

7. identified Jan 20, 2026, 12:21 AM UTC

   We are continuing to work on a fix for this issue.

8. resolved Jan 20, 2026, 12:22 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 16, 2026, 05:05 PM UTC· resolved Jan 16, 2026, 06:51 PM UTC

1. investigating Jan 16, 2026, 05:05 PM UTC

   Microsoft is currently investigating an alert with our interoperability service that has the potential to have impact on summaries being delivered timely. At this time we suspect the primary impact may be delivery delay, however, more details will be provided as it is available from the investigation.

2. investigating Jan 16, 2026, 05:57 PM UTC

   Microsoft is investigating a service disruption in our US Data Center affecting the timely delivery of summaries when using DAX/Dragon Copilot. Symptoms may include: Delayed delivery of summaries At this time we have identified the potential cause, taken steps to remediate the issue, and will continue monitoring to confirm performance improves.

3. resolved Jan 16, 2026, 06:51 PM UTC

   Microsoft has resolved an issue affecting Dax/Dragon Copilot products within our US datacenter. A detailed analysis for the impact will be available within the next 10 days.

Read the full incident report →

Started Jan 15, 2026, 06:24 PM UTC· resolved Jan 15, 2026, 07:38 PM UTC

1. investigating Jan 15, 2026, 06:24 PM UTC

   Microsoft is currently investigating an alert with our interoperability service that has the potential to have impact on summaries being delivered timely. At this time we suspect the primary impact may be delivery delay, however, more details will be provided as it is available from the investigation.

2. monitoring Jan 15, 2026, 07:28 PM UTC

   Microsoft is investigating a service disruption in our US Data Center affecting the timely delivery of summaries when using DAX/Dragon Copilot. Symptoms may include: Delayed delivery of summaries At this time we have taken some steps to remediate the issue and will be monitoring to confirm improved behavior. All summaries are expected to deliver as expected. If you are able to open sidecar and see summary content, but not seeing content in Epic you may apply normal troubleshooting steps of removing and then re-adding the ambient Smart Sections. Additionally, if needed urgently you may also copy/paste from sidecar and place into Epic.

3. resolved Jan 15, 2026, 07:38 PM UTC

   Microsoft has resolved an issue affecting Dax/Dragon Copilot products within our US datacenter. A detailed analysis for the impact will be available within the next 10 days.

Read the full incident report →

Started Jan 09, 2026, 08:14 PM UTC· resolved Jan 09, 2026, 10:19 PM UTC

1. investigating Jan 09, 2026, 08:14 PM UTC

   We are currently investigating reports of issues with Dax Copilot using DMO. Users are reporting blank summary or a refresh error after some inactivity. Temporary work around is to close DAX Copilot window and do a short dictation with DMO, then reopen the Dax Copilot window. More information as it becomes available.

2. investigating Jan 09, 2026, 08:55 PM UTC

   We have identified an issue in DAX Copilot for DMO where some users may encounter errors after a period of inactivity. Symptoms may include: - Error message stating: "Refresh failed." - Blank summaries being returned Temporary workaround: - Please close the DAX Copilot window and then reopen DAX Copilot window.

3. resolved Jan 09, 2026, 10:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 17, 2025, 03:50 PM UTC· resolved Dec 17, 2025, 05:49 PM UTC

1. investigating Dec 17, 2025, 03:50 PM UTC

   Microsoft is investigating a potential issue affecting summary availability in the DMO application for DAX Copilot for DMO customers within our US datacenter. Summary availability in the mobile application is not affected. More details will be provided when information is available.

2. investigating Dec 17, 2025, 03:50 PM UTC

   We are continuing to investigate this issue.

3. investigating Dec 17, 2025, 04:39 PM UTC

   Microsoft is currently investigating an issue affecting some customers using DAX Copilot for DMO. Observed Symptoms: - Summaries are not available within the DMO application. Important Notes: - Summary access through the mobile application remains fully functional. Customers can continue viewing summaries on mobile without interruption. - There is currently no known workaround. - If urgent summary availability in the EHR is required, please use alternative methods to create and enter the note directly in the EHR. If immediate summary availability in the EHR is not required, you may continue to use the application as normal and access your summaries within DMO once the issue is resolved. If your organization is impacted, please open a ticket with DAX Copilot Support.

4. resolved Dec 17, 2025, 05:49 PM UTC

   This incident has been resolved.

Read the full incident report →