Microsoft Stock: A July Update Knocked Out Over 80% of…
Business

Microsoft Stock: A July Update Knocked Out Over 80% of…

Microsoft stock closed at $517.99 on Monday, down 1.12%, after Microsoft traced last week’s Microsoft 365 outage to a defect in a July update for its network gateway servers. The company said its load tests ran on weaker hardware and missed the bug, according to the preliminary post-incident review reported by The Register. Shares traded at $515.90 before Tuesday’s open at 08:22 GMT, per TradingView.

On day two of the outage, 13 November, Microsoft was reversing a recent network change to test whether it played a part. The review now places the fault in code that ran in production for more than three months. A final report, the next disclosure for Microsoft stock, is due on 20 November.

A July Gateway Fix Passed Load Tests on Fewer-Core Servers

Microsoft shared the review in the Microsoft 365 admin center, and Charles Lamanna, executive vice president for Copilot, Agents and Platform, summarized it on X early on 16 November. It names three factors that hit the networking gateway in front of many Microsoft 365 services. The first was the July code, which caused “lock contention inside an internal Windows process which caused the machine’s resources (CPU & memory) to be exhausted,” The Register reported.

The lab tests that cleared the July code ran on different hardware from the servers that failed in production. “The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on weaker hardware with fewer cores,” Microsoft wrote, per BleepingComputer.

The second factor was extra load from Teams, which moved its traffic onto the gateway that also serves Exchange Online about 15 hours before the outage. The third was capacity, since nearly 14% of gateway capacity was already offline for an unrelated reason. “At its lowest, more than 80% of servers were unresponsive,” Microsoft said, and safeguards meant to keep a failure inside one region also failed.

Teams Moved Traffic at 01:07 UTC, 39 Hours Before Full Recovery

The Register’s account of the timeline starts with the Teams failover at 01:07 UTC on 12 November. Microsoft detected the anomaly at 16:03 UTC and logged the first support case at 16:33 UTC. Microsoft stock closed at $523.00 that day, about five hours after detection. At 00:30 UTC on 13 November, engineers pinned the problem on the process that negotiates connections.

Mitigation began at 07:20 UTC, and Microsoft declared services healthy at 16:10 UTC, 24 hours and 7 minutes after detection. Lamanna explained the delay in a post quoted by The Guardian. “Since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change,” he wrote.

Fifteen hours separated the Teams failover from the first alarm, and recovery took another 24 hours and 7 minutes, per Microsoft’s preliminary review (The Register, BleepingComputer). Source: Microsoft via The Register, BleepingComputer · Chart: FinanceFeeds

Exchange Online Stayed Down After Teams and OneDrive Moved

Teams, OneDrive, SharePoint and Office apps switched to the other gateway and recovered sooner. Exchange Online could not move “for scale reasons,” The Register reported, so Outlook mailboxes stayed dark. Defender and Intune were also affected, per The Stack.

Downdetector logged more than 7.4 million reports worldwide, peaking near 20,000 a minute, according to Reuters reporting carried by CBC News.

Microsoft Has Rolled Back the Code Path and Added Capacity

Engineers built an update that returned the Windows code path to its earlier state, The Register reported. Microsoft has since “increased capacity, improved monitoring, and added safeguards to prevent traffic redirection from triggering similar cascading failures,” BleepingComputer said. Lamanna wrote that the fix was “prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments,” per The Stack. That matters for Microsoft stock because enterprise customers have no Windows patch to install.

“We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations,” Lamanna added.

Investor Takeaway

Microsoft has named the defect, confirmed the fix is limited to its own gateway servers, and set 20 November for the final report, so the open question for Microsoft stock is now how often this kind of failure can recur.

Microsoft Stock Beat the Nasdaq-100 by 2.9 Points Through the Outage

Microsoft stock fell 0.96% from the 12 November close to Monday’s $517.99, while the Invesco QQQ Trust, which tracks the Nasdaq-100, fell 3.84%, according to EODHD data. On 13 November, Microsoft stock dropped to $513.82 intraday, then closed at $523.88. A spokesperson told CNBC the company was “deeply sorry for the disruption this incident has caused our customers and partners.”

Microsoft stock slipped 0.60% from 11 to 16 November while QQQ lost 4.15%, a 3.55-point outperformance across the outage and the root-cause review (EODHD). Source: EODHD · Chart: FinanceFeeds

Mario De Cicco of Morningstar DBRS put global insured losses at $300 million to $500 million, against $400 million to $1.5 billion for the 2024 CrowdStrike outage, CBC reported. Josh Gilbert, market analyst at eToro, told Reuters, “The bigger worry is that this is not the first Microsoft 365 outage this year.” He added, “If reliability starts to look like a recurring problem, it hands every IT department a reason to think twice before putting even more of their business in one provider’s hands.” Microsoft 365 also went down in January, and Azure had an outage in October.

Microsoft stock sits 7.4% below its 4 November high of $559.15 and $13 above the 2 November low of $504.96, with the outage dip on 13 November holding above that level (TradingView). Source: TradingView

Copilot was among the services hit, CBC reported, and Lamanna, who apologized for the outage, also leads the Copilot business. Microsoft stock sits above the $505 bear reference FinanceFeeds set after the $545.18 close on 9 November and below the $520.19 bear case in the 24 October Microsoft stock prediction. The ex-dividend date for the $0.98 payout is 19 November, the day before the final report.

The next earnings test for Microsoft stock is expected around 26 January. Azure revenue grew 48% in the September quarter, and Microsoft spent $41 billion on capex in the June quarter.

Investor Takeaway

Microsoft stock outperformed the Nasdaq-100 through the outage and the review, so the market has so far treated the incident as an operations problem with a limited insured cost.