Front page
BreakingContact Center11h · 06:11 GMT · 8 min read
Microsoft Outage Cut Agents Off From the Contact Center
Dynamics 365 Contact Center went down for just under eight hours on Thursday, leaving agents unable to take voice and digital conversations. Microsoft restored access just after midnight GMT, but the wider Microsoft 365 outage was still in service degradation as of 11:00 GMT on Friday.
Updated 11:10 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 in service degradation more than 18 hours after Exchange Online first failed, with no time given for a full recovery.
Agents Lost the Contact Center
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. Microsoft opened a companion incident, MO1550821, at 18:26 GMT for the wider Microsoft 365 impact. As of the 09:57 GMT update, both were still in service degradation. Microsoft said “global telemetry and customer reports show incremental improvement in several workloads; however, service health remains variable and capacity has not yet fully returned to baseline.” It has extended the email timeout window to 48 hours to preserve delayed messages, said there is no evidence of malicious activity, and promised a full Post-Incident Report after mitigation.
Microsoft’s first public word on X about the Exchange failure came at 17:54 GMT, 97 minutes after the incident began, and it pointed only to the Americas. Forty-five minutes earlier, the same account had declared a separate Teams incident fully resolved. At 18:07 GMT, 13 minutes after that first post, it said users “in any region” could be affected. By Friday midday, the first post had been viewed more than 18.7 million times.
At 07:25 GMT, Microsoft reported “positive results for server stability” after applying an upstream authentication and routing configuration patch. At 08:09 GMT, it began expanding that patch to regions entering peak business hours. At 09:03 GMT, it reported “early signs of stabilization.” Around 11:00 GMT, The Guardian quoted Microsoft saying recovery actions were complete across parts of the affected infrastructure in Asia Pacific, traffic was being gradually restored, and mailbox access and delayed email processing were improving, though some users may still see intermittent issues. Microsoft said it was extending those recovery actions to other regions.
“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
Overnight, Microsoft 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.” At 06:56 GMT it reported only “marginal success.” Microsoft has not confirmed a root cause, but telecoms engineers will recognize the pattern: even fully redundant systems can be brought down by corrupt or wrongly loaded configuration data in the core layer that routes traffic, and recovery then means a careful, staged restart, system by system, which fits what Microsoft has described so far. 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. On-premises mail flow may be affected if it goes to or from Exchange Online, and some users may have trouble sharing SharePoint files externally.
Sky News technology correspondent Rowland Manthorpe said there is “limited information” coming from Microsoft, but it seems some kind of software update caused a “surge of traffic to their systems.” He compared it to a motorway: “If you imagine a motorway which has one lane closed off so all the traffic goes to the next lane. Then that lane gets closed down and all the traffic goes to the next lane… The trouble they are having is when they reopen the lanes, all that waiting traffic floods in and then the whole system crashes again.” That, he said, is why it is “hard to find a fix,” noting the outage had lasted 16 hours. “Taken on a global level the disruption is huge.”
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, more than 18 hours after mailboxes first failed. 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. Microsoft says Graph calls that access mail, calendar, and contacts may time out, hitting integrations and notifications, and that Copilot may be unable to load Copilot Chat or reach work data such as email, calendar, and files. Power Apps and Field Service mobile apps may fail intermittently at sign-in; the web versions work, and users already signed in should stay signed in. Power Platform advisory PP1550869, still open at 08:52 GMT, says flows, apps, and connectors are failing intermittently because of an upstream Graph outage, and that Copilot Studio may see connector failures.
OpenAI’s status page was still investigating an issue with Microsoft connectors as of 11:10 GMT, saying new connections may be broken and tools are not working as expected. Anthropic’s Microsoft 365 connector incident remained open at 11:10 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.
In the UK, NHS England said staff were falling back on paper records or other IT systems. The GMB union said 111 and 999 staff could not refer patient details in the normal way, creating a backlog, though emergency and life-threatening call-outs appeared unaffected. Police could not receive crime reports online. Pharmacies told The Guardian they could not email some GP surgeries about prescriptions, lengthening waits. Ofsted could not receive emails. Euronext told listed companies to telephone. National Rail warned that emailed tickets may not be reachable and pointed passengers to apps and websites.
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.”
When the Mailbox Went Dark
When email went dark, service organizations pushed customers onto the phone and into apps, and some frontline teams reached for paper. That is a test of channel resilience, and of how much case handling quietly depends on the mailbox.
What CX Practitioners Are Saying
Early on Friday I put the question to the r/customerexperience community on Reddit: if the overflow channel and the AI assistant share the same cloud as the contact center, how many ways are really left to reach a customer? The thread is still young, with one public reply so far. That reader, drawing on past major outages, warned that the post-incident reports that follow tend to be heavily edited by legal and marketing teams, and that the most candid explanation often comes verbally from an account manager or customer success manager rather than from the official write-up.
That is worth remembering when Microsoft’s contact center report lands within five days. Read it, then ask your account team the questions it leaves out. The conversation is still open.
What CX Leaders Should Do Now
A restored contact center is not a resilient one.
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.
rate this storyhelps rank stories across CX Today
