Microsoft is making a deliberate strategic choice: constrain third-party Azure to feed higher-margin first-party AI products. This explains why Azure growth is 39% when it could be 40%+.
The Strategic Framework
Third-Party Azure (Constrained)
- External customers using Azure AI services
- Competitive with AWS, Google Cloud
- Lower margin (infrastructure economics)
- Customer can switch providers
First-Party AI Products (Prioritized)
- M365 Copilot: 15M seats, $30/user/month
- GitHub Copilot: 4.7M subscribers, $19-39/month
- Security Copilot: 1.6M customers
- Dynamics 365: Built-in AI agents
The Economics
| Product Type | Margin Profile | Lock-in | Switching Cost |
|---|---|---|---|
| Third-party Azure | Lower | Moderate | Medium |
| M365 Copilot | Higher | Strong | Very High |
| GitHub Copilot | Higher | Strong | High |
The Hood Insight
“If I had taken the GPUs that came online in Q1 and Q2 and allocated them all to Azure, the KPI would have been over 40%.”
— Amy Hood, CFO
Translation: Microsoft is deliberately holding back Azure growth to feed Copilot products.
Why This Makes Strategic Sense
- Higher margins: SaaS AI products vs. infrastructure
- Deeper lock-in: Copilot embeds in daily workflows
- Data moat: Work IQ from M365 usage
- Competitive differentiation: AWS/Google can’t match the integrated experience
The Capacity Allocation Hierarchy
- M365 Copilot (highest priority)
- GitHub Copilot
- Security Copilot / Dynamics
- Azure AI (third-party) — gets remaining capacity
Implication for Investors
Don’t judge Microsoft’s AI progress by Azure growth alone. The real AI monetization is happening in Copilot products — which don’t show up in the “Azure growth” metric but represent higher-quality revenue.
For the complete strategic analysis, read Microsoft In The AI Stack on The Business Engineer.









