746907948

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.

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.

We are continuing to investigate this issue.

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.