A hidden bug in Microsoft's cloud gateway caused one of the biggest outages in the company's history, and it ran for almost 24 hours. Businesses and public offices that depend on Microsoft 365 and Exchange Online felt it immediately. The company had two independent gateways for resilience, and both still went sideways.
If you run anything on Microsoft 365, this one is a wake-up call. The root cause was a change to the gateway that, under certain conditions, exhausted CPU and memory until servers stopped responding. Pre-release testing missed it because the test hardware was weaker than systems already in production. Your staging environment may be lying to you in the same way.
The timeline: the outage ran from November 12 at 16:20 UTC to November 13 at 16:10 UTC. About 15 hours earlier, Teams traffic was moved from the alternate gateway onto the primary, which carries Exchange Online access, and capacity was running 14 percent below optimal. Restarts didn't help, and a targeted fix from Microsoft engineers was needed. Microsoft extended email delivery timeouts so delayed messages wouldn't bounce. The full final report is due November 20.
Coral just dropped as an open-source, self-hosted gateway that sits between your agents and the systems they work on. Every tool call gets checked against your workspace policy first. Only then does Coral add the credentials and forward the call to the provider. Agents never see the tokens.
If you're wiring agents into GitHub, Linear, your CRM, or a warehouse, this is the layer you've been missing. Allow, Ask, or Block gets set per provider tool and per custom tool. Custom tools are code, so they can hold rules that flat allow lists can't express, like only rolling back the services named in a ticket. Teammates can share tools without sharing API tokens, which is the part your security team will actually care about.
The numbers are the reason to look. Coral is used by thousands of developers at more than 450 companies, and it's ahead of other MCP gateways in blind benchmarks of 100 enterprise tasks. Custom tools cut tokens by 37%, cost by 31%, and time by 29%. Coral runs on your infrastructure with zero data egress, is written in Rust, and is licensed Apache 2.0. Let's dive deeper…
In today's ContentBuffer update: