Microsoft Outage Cut Agents Off From the Contact Center

Updated 07:38 GMT, November 13, 2026

Dynamics 365 Contact Center went down for just under eight hours on Thursday evening. Agents could not get into the workspace. Voice and messaging stopped.

Microsoft says it restored agent access at 00:57 GMT on Friday. The wider Microsoft 365 outage was still running more than 15 hours after Exchange Online first failed, with no time given for a full recovery.

Microsoft logged the failure as incident CR1550885, a Dynamics 365 Apps incident that began at 17:00 GMT on November 12. It is a separate ticket from the Exchange Online and Microsoft 365 incidents that started the same afternoon, with a different preliminary cause.

“A portion of the database infrastructure responsible for Contact Center experienced connectivity failures.”

Microsoft service health, incident CR1550885, November 13, 2026

Agents who could not sign in could not send or receive messages or voice calls, and those who could get in saw degraded voice and messaging. Microsoft failed over the affected database infrastructure and later said access, voice, and messaging had returned, with transcripts still intermittent. After a transcript-service restart and a period of monitoring, it declared the service restored.

The Wider Outage Is Still Open

Exchange Online incident EX1550543 began at 16:17 GMT on November 12, leaving users unable to reach Exchange Online mailboxes. Microsoft opened a companion incident, MO1550821, at 18:26 GMT for the wider Microsoft 365 impact. As of the 07:25 GMT update on Friday, both were still in service degradation, with the next update due at 08:30 GMT and no estimated recovery time. Microsoft said it is seeing “positive results for server stability” after applying a patch to part of its infrastructure, and is working to expand that work to servers in active regions. Microsoft’s public status page still showed a Microsoft 365 degradation and no Azure issues. @MSFT365Status last posted at 06:12 GMT.

“As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution.”

Microsoft service health, incidents EX1550543 and MO1550821, 07:25 GMT, November 13, 2026

Microsoft earlier said a process on affected servers “responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests,” and that it had begun reverting “a recent network configuration change that correlates with the start of impact.” Later updates described mitigation work that produced traffic surges, and machines “stuck in a bad state.” At 06:56 GMT, Microsoft reported only “marginal success” after patching and rebooting affected servers.

The BBC, citing Downdetector, said Outlook problem reports peaked at nearly 140,000 around 18:00 GMT on Thursday. Nine.com.au reported the disruption reached 74 countries. Microsoft says Teams calls, chats, and meetings have mostly kept working, while calendar and scheduling have not. Microsoft 365 Copilot users may be unable to load Copilot Chat or reach email, calendar, and files. Microsoft also says on-premises mail flow may be affected if it goes to or from Exchange Online, and that some users may have trouble sharing SharePoint files externally. Power Platform advisory PP1550869 began at 17:36 GMT and was still open at 06:37 GMT, with the next update due at 09:00 GMT. Microsoft says flows, apps, and connectors are failing intermittently because of an upstream outage affecting Microsoft Graph, and that Copilot Studio may see connector failures.

The Outage Is Still Hitting Users Worldwide

Microsoft has not restored the wider Microsoft 365 outage that began Thursday afternoon, and it was still hitting users around the world on Friday morning. As of the 07:25 GMT service-health update, Exchange Online and the companion Microsoft 365 incident were still in service degradation, more than 15 hours after mailboxes first failed, with no recovery time given. Microsoft said it is seeing “positive results for server stability” after applying a patch to part of its infrastructure, and is expanding that work. Outlook and Copilot remain impaired, while Teams calls and meetings have mostly kept working, a split UC Today has been tracking as the fix has failed to hold.

The AI Layer Failed With the Same Cloud

If your agents, automations, and AI assistants all need Microsoft Graph to read mail, calendars, or case data, they fail together. OpenAI’s status page was still investigating an issue with Microsoft connectors as of 07:37 GMT, saying new connections may be broken and tools are not working as expected. Anthropic still listed a major unresolved incident at 07:37 GMT. Its last update, at 22:23 GMT on Thursday, said the issue “is caused by a Microsoft 365 service incident” and that mail, calendar, and search tools “are still failing for most requests.” Claude for Outlook remains affected.

Public Services Had to Fall Back

In Australia, the Department of Agriculture, Fisheries and Forestry said “there is a broad service disruption affecting DAFF messaging due to the current Microsoft D365 outage,” and that clients may not be able to send or receive departmental emails. That describes a Dynamics 365 messaging failure, not a confirmed CR1550885 impact. Service NSW said some service-center and call-center transactions were unavailable. The Department of Foreign Affairs and Trade told anyone with an urgent sanctions enquiry to call the Australian Sanctions Office. Triple Zero told Nine.com.au there would be “no direct impact on our services.”

What CX Leaders Should Do Now

A restored contact center is not a resilient one. For nearly eight hours, the primary voice and digital channel sat on a database path that failed. Email, the usual overflow, was already in trouble, and the AI layer failed with it.

If your overflow channel and your AI assistant share the same cloud as the contact center, you do not have a fallback. You have a second way to fail.

I would ask which customer channels still work if Dynamics 365 Contact Center, Exchange, and Graph are all impaired at once, and whether that path has been tested recently.

At Microsoft Ignite last week I set out seven questions for CX leaders. This outage is the concentration risk in live traffic. Microsoft’s contact center post-incident report is due within five days. Until the larger outage is over, keep failover channels staffed and do not assume Teams chat being up means the contact center is safe.