Microsoft's valuation seen as attractive versus hyperscaler peers going into Q2 earnings

Jefferies reiterates a Buy on Microsoft with a $675 price target (implying ~52% upside) ahead of fiscal Q2 results, arguing the stock is attractively valued after an 18% pullback and a 23% multiple compression; Microsoft trades at ~23x fiscal 2027 EPS versus hyperscaler peers. The firm highlights a near-term revenue visibility catalyst—the inclusion of a $250bn OpenAI agreement and $30bn Anthropic Azure compute commitments—saying fiscal Q2 RPO should show the largest sequential step-up ever and that Azure is supply-constrained, not demand-constrained. Jefferies models heavy capex (fiscal 2026/2027 capex incl. leases of ~$141bn and $155bn, +60% and +10% YoY) and expects operating income to grow ~16% in fiscal 2026, while flagging capacity risks, potential margin pressure from AI investments and a modest M365 deceleration to ~13–14% CC growth; Microsoft reports earnings Jan. 28.

Analysis

Market structure: Microsoft (MSFT) is the primary beneficiary — its massive RPO (including $250B OpenAI and $30B Anthropic) creates multi-year demand visibility for Azure/M365 and potential pricing power as enterprise AI spend front-loads. Suppliers of GPU/datacenter capacity (NVIDIA, Equinix, server OEMs) also gain; semiconductor names are beneficiaries of investor rotation but face mean-reversion risk if capacity bottlenecks persist. Supply/demand reads as demand-exceeds-short-term-supply for GPU/slots; Azure is supply-constrained not demand-constrained, implying upside if Microsoft accelerates capacity (capex +60%/10% YoY in Jefferies’ FY26/27 model).

Risk assessment: Tail risks include (1) GPU supply shocks or vendor concentration (NVIDIA supply cut -> Azure revenue miss), (2) regulatory/antitrust or AI-safety actions within 6–18 months, and (3) contract renegotiation or delayed monetization of RPOs. Immediate (days) risk: earnings/guide miss Jan 28; short-term (weeks–months): management capex revision and capacity timeline; long-term (quarters–years): margin pressure if capex and premium GPU costs persist. Hidden dependency: first-party Copilot capacity can cannibalize third-party Azure growth, shifting revenue mix and margin trajectory.

Trade implications: Tactical: asymmetric long on MSFT into Jan 28 with defined downside protection, because valuation compressed to ~23x FY27 vs peers and RPO can re-rate multiple. Relative trades: long MSFT vs short AMZN/GOOGL selectively (equal-dollar) to play superior RPO visibility and monetization vectors. Options: prefer limited-risk call spreads or collar structures around earnings to capture upside from an Azure beat while capping gamma; trim semiconductor cyclic overweight and shift 2–4% into cloud/software exposure.

Contrarian angles: Consensus downplays the monetization lag of RPO — large RPO inflates visibility but actual revenue recognition and margin impact can be delayed 6–18 months; market may also underprice margin downside from sustained elevated GPU costs (200–400bp headwind). Reaction could be underdone: MSFT is down ~18% but still capable of a significant rerate if Azure growth and RPO convert; conversely, if capex >$150B FY26 or Copilot diverts >10% capacity, downside 15–25% is plausible. Historical parallel: prior cloud capex cycles saw large capex followed by multi-quarter margin compression before re-acceleration of earnings.

Key Decisions for Investors

• Establish a 2–3% long position in MSFT (ticker: MSFT) ahead of the Jan 28 earnings print; simultaneously buy a 1-week protective put ~3% OTM (expiry the week after earnings) sized at 25–33% of the equity position to limit event risk.
• Allocate 0.8–1.0% of portfolio to a limited-risk call spread on MSFT (buy near-ATM call, sell a call ~+15% strike) expirying 6–10 weeks out to capture potential post-earnings re-rating while capping premium; take profits at +30–50% and cut if spread loses 50%.
• Initiate a pair trade: long MSFT 2.0% vs short AMZN 1.5% (equal-dollar neutralized for beta) to express RPO-driven outperformance; add to the long leg on an Azure revenue beat >200bp above guidance within 48 hours, or close the pair if MSFT misses Azure by >200bp.
• Reduce semiconductor overweight by 2–4% (trim NVDA/AMD positions) and redeploy into cloud/software (MSFT, up to +2% allocation) to reflect rotation risks reversing if hyperscaler capacity execution proves stronger than the market expects.
• Set hard monitoring triggers: if management raises FY26 capex guidance above $150B or publicly states capacity constraints will extend beyond fiscal 2026, cut MSFT exposure to <=1% within 30 days and buy index/sector downside protection (S&P 500 or XLK puts) sized to cover at least 50% of the position.