Microsoft says three-month-old bug behind global M365 outage

Résumé détaillé
Newer servers proved more vulnerable than those in test labs.
Microsoft has blamed a bug that sat undetected in its networking gateway servers for more than three months for last Friday's lengthy global Microsoft 365 outage.
The defect, said to be lock contention inside an internal process, made servers unresponsive under certain load conditions, Charles Lamanna, Microsoft executive vice-president of Copilot, agents and platform, said in a post on social media.
Lock contention occurs when many tasks queue for the same shared resource, meaning work stalls while they wait.
The bug was introduced by a fix Microsoft wrote specifically for the gateway servers.
That fix began rolling out in July, and had been running worldwide for more than three months without problems.
"Neither the underlying defect nor the fix applies to broader Windows deployments," Lamanna said.
Load testing missed the problem because Microsoft's labs concentrated on weaker hardware with fewer cores, while the contention was worse on newer machines with more processor cores.
Contributing to the issue, about 15 hours before the outage, Teams failed over from a separate gateway system onto the primary one that also serves Exchange Online, adding load and changing traffic patterns.
At the same time, nearly 14 per cent of gateway capacity was out of service because of an unrelated issue the previous day.
Début de l'article, extrait de iTnews. Pour lire la suite, ouvrez l'article chez le média.
MarketNews présente le titre et le résumé publiés par le média. L'article complet se lit sur le site de l'éditeur. (www.itnews.com.au)
