I’m Buying Microsoft Exec’s Tactical Assertion That He Supports an AI Killswitch
When Microsoft's president called for an AI killswitch at the UN, most investors shrugged. The financials behind that statement tell a very different story about who benefits most from writing the rules of AI safety.
This post may contain links from our sponsors and affiliates, and Flywheel Publishing may receive compensation for actions taken through them.
This month I added more Microsoft (NASDAQ:MSFT | MSFT Price Prediction) shares after a comment most investors skipped past. On September 24, Microsoft President Brad Smith said AI developers and cloud providers should have the ability to shut down AI systems. He also backed independent safety evaluations during UN General Assembly discussions. The Wall Street Journal framed it simply: “A Kill Switch for AI? Microsoft’s Brad Smith Says Yes.”
A Killswitch Rewards the Company That Owns the Controls
I read Smith’s position as strategy. If the power to shut down AI lies with cloud providers, the platform governing AI becomes the checkpoint everyone must trust. Microsoft has spent years building that checkpoint. On the July 29 earnings call, CEO Satya Nadella said “every model is substitutable” and recommended enterprises to keep memory and context outside any single model.
Agent 365 had nearly 40 million agents registered two months after launch. Purview audited over 15 billion Copilot interactions, up nearly 360%. Rules demanding human control favor the company already selling that control.
Three Receipts Behind Every Purchase
First, demand. Commercial remaining performance obligations, which are signed revenue the company has not yet recognized, reached $678 billion in fiscal Q4, up 84%. Azure passed $100 billion in annual revenue for the first time and grew 43% in the quarter. Full-year revenue came in at $331.84 billion, up 17.79%.
Second, quality. Microsoft runs a 46.78% operating margin and a 22.01% return on invested capital. Its debt-to-equity ratio is 0.29 and its interest coverage is 50.88.
Third, consistency. Fiscal Q4 EPS of $4.74 beat the $4.24 estimate, the fifth consecutive beat. That quarter did include a $3.20 billion Anthropic gain. Microsoft returned $12.7 billion to shareholders in fiscal Q2 alone and announced a quarterly dividend increase on September 15. The 0.69% yield is modest, but it keeps growing, and the shares gained 903.07% over ten years.
Why Amazon and Alphabet Get Passed Over
Amazon (NASDAQ:AMZN) trades at 35 times earnings, compared with Microsoft’s 29. It pays no dividend and runs an operating margin of 11.16%. Its free cash flow yield is 0.29%, against Microsoft’s 1.75%.
Alphabet (NASDAQ:GOOGL) looks cheaper at 15 times earnings. However, a $99.03 billion equity gain inflated its latest net income. Its Q2 free cash flow came in at negative $5.855 billion, it suspended buybacks, and its long-term debt rose from $46.5 billion to $98.2 billion. Its 0.50% yield also lies below Microsoft’s.
Capex Is the Risk I Track Every Quarter
Spending could hurt this position. Fiscal 2026 capital expenditures hit $115.95 billion, up 79.62%, and free cash flow slid 6.46% to $66.99 billion. OpenAI-related losses reached $3.1 billion in fiscal Q1, compared with $523 million a year earlier. Management also expects capex to rise again. If AI demand cools off, those data centers turn into expensive idle assets.
My buying continues because demand still runs ahead of supply. CFO Amy Hood said “There are still constraints in the system.” Operating cash flow rose 34.35% to $182.94 billion, and nearly 90% of Microsoft Cloud revenue comes from customers outside the frontier model companies.
What Keeps My Buy Button Active
Management expects another year of double-digit growth in revenue and operating income, with operating margins falling less than one point. Now the company’s president wants AI safety to run through cloud providers. I see Microsoft helping to write rules it already knows how to follow, and I plan to keep adding shares of the company that controls the shutdown.
Contact [email protected] for any questions or corrections.







