Update - 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.

Feb 13, 2026 - 09:30 EST
Monitoring - 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.

Feb 12, 2026 - 17:12 EST
Update - We are continuing to investigate this issue.
Feb 12, 2026 - 16:07 EST
Investigating - 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.

Feb 12, 2026 - 08:30 EST
DAX Copilot Mobile Operational
DAX Copilot Mobile - Login Operational
DAX Copilot Mobile - Audio Upload Operational
DAX Copilot Mobile - Summary Availability Operational
Dragon Medical One Desktop App w/ Copilot Operational
Dragon Medical One Desktop App w/ Copilot - Login Operational
Dragon Medical One Desktop App w/ Copilot - Summary Availability Operational
Dragon Medical One Desktop App w/ Copilot - Summary Editing Operational
DAX Copilot for Epic Operational
DAX Copilot for Epic - Audio Recording Operational
DAX Copilot for Epic - Summary Generation & Delivery Operational
Nuance Management Center Operational
Nuance Healthcare Analytics Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Feb 13, 2026

Unresolved incident: 746907948.

Feb 12, 2026
Feb 11, 2026

No incidents reported.

Feb 10, 2026

No incidents reported.

Feb 9, 2026

No incidents reported.

Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026

No incidents reported.

Feb 5, 2026

No incidents reported.

Feb 4, 2026

No incidents reported.

Feb 3, 2026
Resolved - This incident has been resolved.
Feb 3, 12:49 EST
Update - 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.

Feb 3, 12:03 EST
Identified - 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.

Feb 3, 11:04 EST
Investigating - 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.

Feb 3, 10:01 EST
Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.