All Systems Operational

United States Operational
Dragon Medical One - Login Operational
Dragon Medical One - Speech Recognition Operational
Dragon Medical One - Customizations Operational
Dragon Medical Embedded - Speech Recognition Operational
Dragon Medical Embedded - Customizations Operational
Nuance Management Center Operational
Nuance Healthcare Analytics Operational
PowerMic Mobile Operational
Canada Operational
Dragon Medical One - Login Operational
Dragon Medical One - Speech Recognition Operational
Dragon Medical One - Customizations Operational
Dragon Medical Embedded - Speech Recognition Operational
Dragon Medical Embedded - Customizations Operational
Nuance Management Center Operational
Nuance Healthcare Analytics Operational
PowerMic Mobile Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Feb 12, 2026
DMO Authentication errors
Resolved - This incident has been resolved.
Feb 12, 11:32 EST
Update - Microsoft has identified the service disruption affecting Dragon Medical One (DMO) Auth0 based SSO logins in our US datacenter.

Symptoms:

When launching DMO using Auth0 based SSO, users receive an error stating:
User Authentication Failed.

Note: Users who are already logged in will remain unaffected and can continue their sessions without interruption.

We apologize for any inconvenience and appreciate your continued partnership.
Feb 12, 11:22 EST
Identified - Microsoft has identified the service disruption affecting Dragon Medical One (DMO) Auth0 based SSO logins in our US datacenter.

Symptoms:
When launching DMO using Auth0 based SSO, users receive an error stating:
User Authentication Failed.

We apologize for any inconvenience and appreciate your continued partnership.
Feb 12, 11:11 EST
Investigating - Microsoft is investigating a potential issue affecting Dragon Medical One (DMO) users who are using central authentication within our US datacenter.
This is currently under investigation and more details will be provided when information is available.
Feb 12, 10:42 EST
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

No incidents reported.

Feb 2, 2026
Possible PMM Impact
Resolved - This incident has been resolved.
Feb 2, 15:55 EST
Update - Microsoft continues to investigate a potential issue affecting a subset of PowerMic Mobile users. More details will be provided when information is available.

Symptoms: Unable to pair, no pairing ID.

Note: Dragon Medical One is still fully operational and users can switch to alternate microphone sources.
Feb 2, 14:53 EST
Update - We are continuing to investigate this issue.
Feb 2, 14:52 EST
Update - Microsoft continues to investigate a potential issue affecting a subset of PowerMic Mobile users. More details will be provided when information is available.

Symptoms: Unable to pair, no pairing ID.

Note: Dragon Medical One is still fully operational and users can switch to alternate microphone sources.
Feb 2, 14:52 EST
Update - We are continuing to investigate this issue, and next update will be provided by 2:45 PM EST.
Feb 2, 13:04 EST
Update - We are continuing to investigate this issue.
Feb 2, 12:57 EST
Update - We are continuing to investigate this issue.
Feb 2, 12:39 EST
Update - We are continuing to investigate this issue.
Feb 2, 11:06 EST
Investigating - Microsoft is investigating a potential issue affecting PowerMic Mobile within our US datacenter. This is currently under investigation, and more details will be provided when information is available.

Symptoms: Unable to pair, no pairing ID.

Note: Dragon Medical One is still fully operational and users can switch to alternate microphone sources.
Feb 2, 10:54 EST
Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage