Program report · filed November 13, 2026
CRM & Sales TechMeasured report
Dynamics 365 Contact Center outage blocked agent calls and messaging
Contact Center agent access returned at 00:57 GMT on November 13 after nearly eight hours. Microsoft 365’s broader incident remained degraded more than 13 hours after Exchange Online first failed.
By Marcus Bennett3 min read645 words
Program notes
- Dynamics 365 Contact Center agent access was restored at 00:57 GMT on November 13, 2026.
- The contact-center incident began at 17:00 GMT on November 12 and lasted just under eight hours.
- Exchange Online incident EX1550543 began at 16:17 GMT; Microsoft 365 incident MO1550821 followed at 18:26 GMT.
- At 05:43 GMT on November 13, both broader incidents remained degraded with no recovery estimate.
- At 05:43 GMT on November 13, Microsoft’s status page showed Microsoft 365 degradation and no Azure issues.

By Marcus Bennett
Microsoft said it restored Dynamics 365 Contact Center agent access at 00:57 GMT on November 13, 2026, after an incident that had lasted just under eight hours. The outage began at 17:00 GMT on Thursday, November 12, leaving some agents unable to enter the workspace. It also stopped voice and messaging, while agents who got in experienced degraded service.
What did contact center agents lose?
Agents who could not sign in could not send or receive messages or make or receive voice calls. Those who did get in saw degraded voice and messaging. For customer-facing teams, this was a combined authentication failure and channel impairment, rather than a single broken feature.
The incident record does not report affected agent headcount, call volume, customer wait time, or differences by team size. Those operating costs therefore cannot be quantified from the published account.
How did Microsoft restore Contact Center?
Microsoft logged the failure as incident CR1550885, classified as a Dynamics 365 Apps incident. It used a separate ticket from the Exchange Online and Microsoft 365 incidents that began that afternoon, with a different preliminary cause.
The preliminary cause appeared in Microsoft’s service-health record: “A portion of the database infrastructure responsible for Contact Center experienced connectivity failures.” Microsoft failed over the affected database infrastructure (switching service away from the disrupted component), then reported that access, voice, and messaging had returned.
Transcripts remained intermittent after agents regained access and voice and messaging resumed. Microsoft restarted the transcript service and monitored it before declaring Contact Center restored, with agent access restored at 00:57 GMT on Friday.
That sequence separated three milestones: workspace entry, conversation channels, and transcript retrieval. For teams running customer contact in Dynamics, it shows why a successful login does not by itself establish full service recovery.
Why was the broader Microsoft 365 incident still open?
Exchange Online incident EX1550543 began at 16:17 GMT on November 12, leaving users unable to reach Exchange Online mailboxes. Microsoft opened companion incident MO1550821 at 18:26 GMT for the wider Microsoft 365 impact.
By the 05:43 GMT update on Friday, both incidents remained in service degradation. The wider outage had continued for more than 13 hours after Exchange Online first failed, with no estimated recovery time. Microsoft scheduled its next update for 07:00 GMT.
Microsoft’s public status page still showed a Microsoft 365 degradation and no Azure issues. The @MSFT365Status account last posted at 05:01 GMT, and the report carried a 05:52 GMT update.
Microsoft said: “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.”
What caused the wider failure?
Microsoft’s explanation for the wider incident centered on a process on affected servers “responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests.” The company had begun reverting “a recent network configuration change that correlates with the start of impact.”
That wording identifies correlation, not proof of a single root cause. Later updates described mitigation work that produced traffic surges and machines “stuck in a bad state.”
Because the wider incidents remained open, these details formed an evolving account rather than a closed root-cause finding. The public record did not supply a final cause or full-recovery time.
What should operators watch next?
For customer-facing teams using Dynamics, the immediate watchpoint is whether Contact Center remains stable after its declared restoration. Transcript continuity and voice handling warrant attention because they degraded before Microsoft restored the service.
The wider incidents had no recovery estimate at 05:43 GMT, making the scheduled 07:00 GMT update the next public checkpoint. Until Microsoft closes them, restoration of agent login should not be read as clearance of the wider Microsoft 365 environment.
via cxtoday.com (Source)
More from Marcus Bennett
Show full bio
Staff writer covering people, launches and day-to-day practice in Sales technique and methodology, sales enablement at Quota Brief.
120 articles
Also rated
- Optimizely Malware Hit 178 Organizations in One Supply-Chain Attack
- Microsoft Ignite 2026: CX Leaders Face Seven Hard Questions
- AI Agent Replaced a Downed Vendor in a Day — and Told Its Team to Never Return
- Microsoft bets contact center harness will outlast the AI model
- Microsoft Says Sellers Can Now Skip the CRM Entirely