Nuance 中断历史

1. 2026年10月23日 UTC 19:01monitoring

   微软了解并积极监测PHP(CVE-2026-109618和CVE-2026-109619)和相关活动. 根据目前掌握的信息,微软没有发现证据表明在微软操作和开发的下列系统中已利用了这些弱点: • 龙医一号 • DAX 副驾驶 • 龙副驾驶

2. 2026年10月23日 UTC 19:54monitoring

   我们正在继续监测任何其他问题.

自动翻译自官方事件更新。

1. 2026年10月9日 UTC 14:16identified

   微软已经确定了一个影响一个美国地区的用户的问题. 症状 - 草稿生成失败. 各小组正在对此开展工作,并将随着我们获得更多信息而更新。 谢谢你的耐心.

2. 2026年10月9日 UTC 14:17identified

   我们正在继续努力解决这个问题。

3. 2026年10月9日 UTC 15:06monitoring

   微软确定并缓解了影响"龙"副驾驶和DAX副驾驶用户的问题. 症状: 延迟起草。 撞击起始时间:09:28 AM ET 减缓时间:上午10:30 所有草案现已提交,我们正在积极监测这一制度。 谢谢你的耐心和持续的伙伴关系.

4. 2026年10月9日 UTC 15:26resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年9月14日 UTC 14:45investigating

   微软目前正在调查一项间歇性合成警报,这可能表明对客户开始录音的能力产生了影响.

2. 2026年9月14日 UTC 15:11identified

   微软目前正在调查一个可能间歇地影响达克斯/德拉贡副驾驶用户的问题. 症状可能包括: 用户可能遭遇出错“ 无法启动 Dax Copilot ” 用户可能遇到错误“ 无法启动视频记录 ” 以后的尝试可能会取得成功,因为这具有间断性。 一旦获得更多信息,我们将提供更多最新情况.

3. 2026年9月14日 UTC 19:23resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年9月10日 UTC 19:20identified

   微软已经发现并正在积极排除一个影响我们美国数据中心范围内DMO和DAX副驾驶的问题。 如有资料,将提供更多详情.

2. 2026年9月10日 UTC 19:26identified

   我们正在继续努力解决这个问题。

3. 2026年9月10日 UTC 20:15identified

   微软已查明影响Dragon Medical One(DMO)和DAX Copilot的服务中断, 症状: 在使用基于 Auth0 的SSO 发射 DMO 时,用户会收到一个错误,表示: - 用户认证失败; 请联系您的管理员 一旦获得更多信息,我们将提供更多最新情况。 我们为这个问题可能造成的任何不便表示歉意,并赞赏你在我们努力全面恢复正常服务水平时继续表现出耐心和伙伴关系.

4. 2026年9月10日 UTC 20:53monitoring

   微软已经补救了影响Dragon Medical One(DMO)和DAX Copilot的服务中断,为基于DMO Auth0的SSO在我们的美国数据中心登录. 症状可能包括: 在使用基于 Auth0 的SSO 发射 DMO 时,用户会收到一个错误,表示: - 用户认证失败; 请联系您的管理员 我们为这个问题可能造成的任何不便表示歉意,并赞赏你继续耐心地合作.

5. 2026年9月10日 UTC 20:57monitoring

   我们正在继续监测任何其他问题.

6. 2026年9月10日 UTC 21:10resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月28日 UTC 06:58identified

   微软已发现并正在积极排除一个影响达克斯/德拉贡副驾驶产品的问题, 如有资料,将提供更多详情.

2. 2026年8月28日 UTC 07:01identified

   微软正在调查美国数据中心的服务中断,影响DAX/Dragon医生和护士产品的副驾驶. 症状可能包括: • 龙/DAX 副驾驶独立 o 用户可以继续支配和制作录音。 o 用户无法通过用户界面访问生成的摘要。 o 记录/起诉和上传将继续,一旦服务恢复,将再次提供摘要。 • 嵌入客户(Epic/EHR集成): o 继续提供摘要。 o 无人驾驶座车/UI经验。 o 仍预期会提出摘要。 我们的工程队正在积极努力减轻影响。 我们将在获得补充资料后提供补充资料。 我们为任何不便表示歉意,并感谢你在我们努力尽快恢复正常服务水平的同时继续合作.

3. 2026年8月28日 UTC 07:46identified

   我们正在继续努力解决这个问题。

4. 2026年8月28日 UTC 08:38identified

   微软继续调查影响美国数据中心后端服务的问题, 症状可能包括: • 龙/DAX 副驾驶独立 o 用户可以继续支配和制作录音。 o 用户无法通过用户界面访问生成的摘要。 o 记录/起诉和上传将继续,一旦服务恢复,将再次提供摘要。 • 嵌入客户(Epic/EHR集成): o 继续提供摘要。 o 无人驾驶座车/UI经验。 o 仍预期会提出摘要。 当前状况 我们的工程小组正在积极努力减轻影响,因为一个支持Dragon和DAX副驾驶功能的数据中心经历了一次电力事件。 我们正在努力开展恢复行动,以恢复受影响的计算资源,同时对健康的基础设施进行故障,以更快地恢复服务。 我们将继续监测局势,并随时提供最新情况。 我们为任何不便表示歉意并感谢你在我们努力尽快恢复正常服务水平的同时继续合作并保持耐心.

5. 2026年8月28日 UTC 10:41monitoring

   微软继续积极解决影响DAX/Dragon Copilots的与我们美国数据中心环境中的后端服务依赖相关的医生和护士问题。 当前状况 我们完成了冗余服务基础设施的故障,然而,我们的监测确定影响仍在继续。 与此同时,我们确认,影响支持Dragon/DAX副驾驶功能的数据中心的电力事件已经恢复,受影响的资源也已恢复。 因此,我们正在将故障恢复到先前已知的良好配置 症状可能包括: • 龙/DAX 副驾驶独立 o 用户可以继续支配和制作录音。 o 用户无法通过用户界面访问生成的摘要。 o 记录/起诉和上传将继续,一旦服务恢复,将再次提供摘要。 • 嵌入客户(Epic/EHR集成): o 继续提供摘要。 o 侧行车/UI经验可能没有或间歇地受到影响。 o 仍预期会提出摘要。 进行中的行动 微软继续密切监测服务健康,同时完成恢复和验证活动. 我们仍然侧重于恢复所有功能和确保稳定的客户经验。 一旦获得更多信息,我们将提供更多最新情况。 我们为这个问题可能造成的任何不便表示歉意,并赞赏你在我们努力全面恢复正常服务水平时继续表现出耐心和伙伴关系.

6. 2026年8月28日 UTC 12:38monitoring

   我们正在继续监测任何其他问题.

7. 2026年8月28日 UTC 14:37resolved

   微软已经解决了影响DAX/Dragon副驾驶医生和护士的问题, 最后状况:在完成倒闭回归之前,我们确认早先的缓解行动恢复了用户通过用户界面加载和取用生成的摘要的能力。 这是事件的最后更新。 初步根因:一个支持"龙"和"DAX"副驾驶功能的数据中心经历了一次动力事件,导致撞击.

自动翻译自官方事件更新。

1. 2026年8月28日 UTC 06:46investigating

   微软已发现并正在积极排除一个影响达克斯/德拉贡副驾驶产品的问题, 如有资料,将提供更多详情.

2. 2026年8月28日 UTC 06:49identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年8月28日 UTC 06:49identified

   我们正在继续努力解决这个问题。

4. 2026年8月28日 UTC 06:50investigating

   我们目前正在调查这一问题.

5. 2026年8月28日 UTC 06:51investigating

   我们正在继续调查这一问题.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 14:00investigating

   We are currently investigating this issue.

2. 2026年8月13日 UTC 14:21investigating

   Microsoft is investigating an issue affecting DAX Copilot for DMO customers. The symptoms include: - Summary unavailable - summaries stay in "writing" status, or disappear after uploading the recording - Delayed summary delivery Clinicians are able to successfully record encounters, but the completed summary is not available or delayed after upload. There is no known data loss and impacted encounters will be successfully processed once this issue is mitigated. Thank you for your patience and continued partnership.

3. 2026年8月13日 UTC 14:49identified

   Microsoft has mitigated the root cause of the recent issue affecting DAX copilot for DMO customers. The symptoms included: - Summary unavailable - summaries stay in "writing" status, or disappear after uploading the recording - Delayed summary delivery At this time, clinicians are able to successfully receive summaries after initiating new recordings using DAX Copilot for DMO. We are actively working to reprocess any encounters that were impacted by this incident to make the summaries available. There is no known data loss and impacted encounters will be successfully processed. We will provide additional communication to update the status of the recovery efforts. Thank you for your patience and continued partnership.

4. 2026年8月13日 UTC 16:59resolved

   Microsoft has mitigated the root cause of the recent issue affecting DAX copilot for DMO customers and successfully reprocessed all impacted encounters. The symptoms included: - Summary unavailable - summaries stay in "writing" status, or disappear after uploading the recording - Delayed summary delivery All encounters impacted by this incident have been recovered. At this time, summaries are available for any encounters impacted during this incident, and clinicians are able to successfully receive summaries after initiating new recordings using DAX Copilot for DMO. Thank you for your patience and continued partnership.

1. 2026年8月12日 UTC 18:32investigating

   Microsoft has been made aware of an issue that is impacting customer being able to call and contact support. This is being investigated. At this time please continue to use the other avenues for support access to include the Community Portal and Chat where available.

2. 2026年8月13日 UTC 01:32identified

   Microsoft has identified the issue preventing calls from being received by the support team and continues to work on remediation. At this time, it is encouraged that other methods of contacting support be utilzied such as the Nuance Community Portal.

3. 2026年8月13日 UTC 17:37resolved

   Microsoft has mitigated the issue preventing calls from being received by the support team. The technical support line is functioning as expected. Thank you for your patience and continued partnership.

1. 2026年8月4日 UTC 14:10investigating

   We are curretly investigating reports of issues launching Dragon Copilot/DAX Copilot application. More details will be provided shortly

2. 2026年8月4日 UTC 14:45identified

   Microsoft has identified an issue affecting Dragon Copilot Desktop and DAX Copilot for Epic ambient users.  Dragon Copilot Desktop and DAX Copilot in Epic launch fails with one of the following messages: Ambient recorder failed to load Visit recording could not be started Unable to Launch Dax Copilot  Engineers are currently engaged and working toward remediation. Thank you for your patience and continued partnership.

3. 2026年8月4日 UTC 16:02monitoring

   Microsoft has resolved an intermittent issue that affected some Dragon Copilot Desktop and DAX Copilot for Epic ambient users. While the issue is no longer impacting users, we continue to monitor the environment and investigate the underlying root cause. Impacted users may have experienced one of the following messages: Ambient recorder failed to load Visit recording could not be started Unable to Launch DAX Copilot Thank you for your patience and continued partnership.

4. 2026年8月12日 UTC 18:30resolved

   This incident has been resolved.

1. 2026年8月1日 UTC 22:59investigating

   我们正在调查一个管理员可能无法向NMC添加新用户的问题。 我们很快会提供最新情况

2. 2026年8月1日 UTC 23:50resolved

   调查后发现一个区域问题,立即得到补救.

自动翻译自官方事件更新。

1. 2026年7月15日 UTC 12:57investigating

   微软正在调查所报告的上述错误.

2. 2026年7月15日 UTC 13:18identified

   微软查明了上述错误,并致力于补救.

3. 2026年7月15日 UTC 13:39identified

   微软正在调查Epic星云上影响EPIC环境用户的"龙"和"DAX"副驾驶的问题. 在Epic Haiku的DAX/Dragon副驾驶发射失败, 与服务器通信时遇到错误 。 如果问题依然存在,请向管理员寻求帮助。 代码:串行失败细节:出乎意料的代号. 影响具体归因于: Epic Nebula上的安比特用户. 已采取补救行动并观察到业绩有所改善。 微软正在密切监测,并将相应更新现状. 谢谢你的耐心和持续的伙伴关系.

4. 2026年7月15日 UTC 14:26monitoring

   微软为Epic Nebula上的EPIC环境用户补救了影响"龙"和"DAX"副驾驶的问题. 在Epic Haiku的DAX/Dragon副驾驶发射失败, 与服务器通信时遇到错误 。 如果问题依然存在,请向管理员寻求帮助。 代码:串行失败细节:出乎意料的代号. 影响具体归因于: Epic Nebula上的安比特用户. 谢谢你的耐心和持续的伙伴关系.

5. 2026年7月15日 UTC 15:27resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月14日 UTC 15:50investigating

   微软目前正在调查关于这个错误的报告.

2. 2026年7月14日 UTC 16:57monitoring

   影响Epic星云上EPIC环境用户的"龙"和"DAX"副驾驶的问题已经解决. 在Epic Haiku的DAX/Dragon副驾驶发射失败, 与服务器通信时遇到错误 。 如果问题依然存在,请向管理员寻求帮助。 代码:串行失败细节:出乎意料的代号. 影响具体归因于:Epic Nebulas上的安平用户. Epic已查明并纠正了截至11:36am ET结束时的问题,并正在积极监测。 谢谢你的耐心和持续的伙伴关系.

3. 2026年7月14日 UTC 17:25resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月2日 UTC 04:18identified

   微软已发现并正在积极排除一个影响达克斯/德拉贡副驾驶产品的问题, 如有资料,将提供更多详情.

2. 2026年7月2日 UTC 05:15monitoring

   微软确定并缓解了美国数据中心影响"龙"和"DAX"副驾驶客户的服务中断. 症状可能包括: 无法登录到 DAX 副驾驶 声明“ 无法启动 DAX 代理驾驶员” 的错误消息 声明“ Dragon Copilot 目前无法使用” 的错误消息 我们的工程小组将继续密切监测这项服务,以确保稳定。 我们为任何不便道歉 并感谢你继续合作

3. 2026年7月2日 UTC 05:52monitoring

   微软确定并缓解了美国数据中心影响"龙"和"DAX"副驾驶客户的服务中断. 症状可能包括: 无法登录到 DAX 副驾驶 声明“ 无法启动 DAX 代理驾驶员” 的错误消息 声明“ Dragon Copilot 目前无法使用” 的错误消息 我们的工程小组正在继续密切监测这项服务,以确保稳定性,并确保所有受影响的音频都得到成功的再处理。 目前所有服务恢复正常。 注:已经登录的用户,我们建议退出和返回,以确保应用程序的最佳性能 我们为任何不便道歉 并感谢你继续合作

4. 2026年7月2日 UTC 17:22resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月1日 UTC 17:22monitoring

   微软正在调查我们美国数据中心的服务中断,影响使用Chrome或Edge扩展的Cragon Medical One(DMO)对少数用户的利用能力.

2. 2026年7月1日 UTC 18:59resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月2日 UTC 17:48investigating

   Microsoft is investigating a service disruption in our US Data Center affecting a subset of DAX Copilot and Dragon Copilot customers. Symptoms may include: -Delay in summary delivery on some encounters. (If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist). 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.

2. 2026年6月2日 UTC 17:55identified

   Microsoft is investigating an issue affecting some Dragon Copilot and DAX Copilot users within your US datacenter region. Symptoms may include: Delay in summary delivery on some encounters. If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist. 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. 2026年6月2日 UTC 18:27monitoring

   Microsoft has remediated an issue affecting some Dragon Copilot and DAX Copilot users within your US datacenter region. Symptoms may have included: Delay in summary delivery on some encounters. If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist. All impacted notes have now been delivered. Note: There are potential delays with orders and backlog is being processed. We apologize for any inconvenience and appreciate your continued partnership.

4. 2026年6月2日 UTC 19:41resolved

   Microsoft has remediated an issue affecting some Dragon Copilot and DAX Copilot users within your US datacenter region. Symptoms may have included: Delay in summary delivery on some encounters. If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist. All impacted notes have now been delivered. The Orders backlog has been processed. We apologize for any inconvenience and appreciate your continued partnership

1. 2026年5月27日 UTC 17:40identified

   Microsoft is investigating an issue affecting DAX Copilot for EPIC users within our US datacenters. Symptom: Subsequent recordings are failing to generate new drafts. Microsoft is actively working on remediation and will provide more information as soon as it is available. Thank you for your patience and continued partnership.

2. 2026年5月27日 UTC 17:59resolved

   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.

1. 2026年5月18日 UTC 18:09identified

   Microsoft is currently aware of an intermittent analytics-related impact stemming from a Microsoft Fabric / Power BI issue. Our engineering teams are actively investigating. Current symptoms include: -Service Unavailable errors -Delays when loading analytics At this time, there is no confirmed workaround. However, some users have reported intermittent success by restarting the application and retrying the operation. We will continue to provide updates as more information becomes available. Thank you for your patience while we work to resolve this issue. Azure Status Link: https://azure.status.microsoft/en-us/status

2. 2026年5月19日 UTC 13:01resolved

   This incident has been resolved.

1. 2026年4月28日 UTC 17:28identified

   Microsoft is actively investigating an intermittent issue impacting Epic Nebula customers using DAX and Dragon Copilot. We are working jointly with Epic to identify the root cause. We expect to provide an update shortly regarding the scope of impact and recommended next steps. Known intermittent symptoms include: - Summaries being delayed We will share additional updates as soon as more information is confirmed. We apologize for the disruption and appreciate your continued partnership while we work to resolve this issue.

2. 2026年4月28日 UTC 20:58monitoring

   Microsoft has mitigated the issue impacting Epic Nebula customers using DAX and Dragon Copilot. Summaries are now being successfully delivered to Epic. We apologize for the disruption and appreciate your continued partnership while we worked to resolve this issue.

3. 2026年5月4日 UTC 14:51resolved

   This incident has been resolved.

1. 2026年4月28日 UTC 14:25identified

   Microsoft has identified and is actively troubleshooting a recurrence of an issue affecting Dax/Dragon Copilot products. Symptoms may include: -- delayed summaries -- auto styling failures More details will be provided when information is available. We apologize for any inconvenience and appreciate your continued partnership as we work to resolve this issue.

2. 2026年4月28日 UTC 15:39identified

   There was a brief issue yesterday impacting auto styling for a small subset of DAX and Dragon Copilot customers. There was a brief reoccurrence of that same issue today, which has been quickly remediated. Some end users may have experienced delay summaries as a related impact. We are seeing improvements in system stability, and we will continue to closely monitor to confirm improved behavior. We apologize for any inconvenience and appreciate your continued partnership while we worked to resolve this issue.

3. 2026年4月28日 UTC 15:41monitoring

   There was a brief issue yesterday impacting auto styling for a small subset of DAX and Dragon Copilot customers. There was a brief reoccurrence of that same issue today, which has been quickly remediated. Some end users may have experienced delay summaries as a related impact. We are seeing improvements in system stability, and we will continue to closely monitor to confirm improved behavior. We apologize for any inconvenience and appreciate your continued partnership while we worked to resolve this issue.

4. 2026年5月4日 UTC 14:51resolved

   This incident has been resolved.

1. 2026年4月16日 UTC 13:18identified

   Microsoft has identified and is investigating an intermittent service disruption in our US Data Center affecting a subset of DAX Copilot for DMO customers. Symptoms may include: Error messages indicating a problem in displaying summaries. More details will be provided when information is available.

2. 2026年4月16日 UTC 13:42identified

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

3. 2026年4月16日 UTC 15:07monitoring

   Microsoft has identified the root cause of the reported issue related to summary errors affecting a subset of DAX Copilot for DMO customers. Mitigation steps are currently underway, and encounters recorded during the impacted timeframe are expected to recover automatically. Note: There will be no data loss for impacted encounters. At this time, we recommend continuing to use the application as this issue appears to be intermittent. We apologize for any inconvenience and appreciate your continued partnership.

4. 2026年4月16日 UTC 20:33monitoring

   A fix will be deployed overnight (with no expected downtime)

5. 2026年4月16日 UTC 20:33monitoring

   We are continuing to monitor for any further issues.

6. 2026年4月17日 UTC 12:49resolved

   This incident has been resolved.