Amazon combines low-margin retail, logistics, advertising and a high-margin cloud segment. Microsoft combines software, cloud, productivity, gaming and devices. Consolidated revenue therefore conceals very different profit engines.
| Lens | Amazon | Microsoft |
|---|---|---|
| Official periods used | Amazon FY 2025 and Q1 2026 disclosures | Microsoft FY 2025 |
| Current scale anchor | Q1 2026 net sales of US$181.5 billion | FY 2025 revenue of US$281.7 billion |
| Main profit engine | AWS plus advertising, alongside retail and logistics | Azure, Microsoft 365 and enterprise software |
| Comparison caution | Quarter versus full year and retail pass-through | Fiscal year ends in June |
Amazon and Microsoft can compete for the same investor capital or customer budget while producing revenue in different ways. Begin with the contract, customer, unit of sale, revenue-recognition rule and capital required to deliver it.
Amazon’s consolidated scale is driven by commerce, while AWS supplies a disproportionate share of operating profit. Microsoft’s profit base is more software-heavy. A proper comparison separates segment economics before discussing valuation.
Use at least three years where the business structure has remained comparable. When an acquisition, demerger, listing, accounting change or segment reorganisation breaks the series, rebuild the history from restated disclosures or clearly mark the break.
Start with four separate layers. First, measure growth quality: identify whether expansion comes from volume, pricing, acquisitions, currency, incentives or a change in reporting perimeter. Second, test unit economics: ask what one additional customer, transaction, vehicle, store, workload or contract contributes after direct costs. Third, inspect capital intensity: include capital expenditure, leases, working capital, depreciation, stock compensation and long-term purchase commitments. Fourth, assess durability: customer concentration, switching costs, regulatory permissions, distribution control and the likelihood that competitors can copy the advantage.
For Amazon, the strongest disclosed metric should be paired with the cost or balance-sheet item that makes it possible. For Microsoft, apply the same rule. This prevents a fast-growing operating statistic from being presented without the cash, capacity or incentive needed to produce it. It also prevents a mature company’s slower growth from being dismissed when it may be generating superior cash returns.
Create three scenarios rather than one forecast. The base case should use current disclosed trends; the downside case should include margin pressure, slower demand and higher funding or compliance cost; the upside case should require a specific operating improvement. Do not change growth, margin and valuation assumptions independently when they are economically linked. A higher growth assumption often needs more capital, customer acquisition or working capital.
Finally, keep business quality and share price separate. A stronger company can still be a poor investment at an excessive price, while a weaker company can appear statistically cheap because the market expects deterioration. This article does not use live market prices; insert the current price, share count, net debt and dilution only on the date of your own analysis.
Regulatory lens: Competition, cloud concentration, consumer protection, labour, privacy and AI rules are material.
A revenue multiple applied to Amazon’s entire sales base and Microsoft’s software revenue will produce a false comparison. Use sum-of-parts: retail on cash generation and fulfilment efficiency; cloud on growth, margin and committed infrastructure.
The practical lesson is to reproduce the comparison in a simple worksheet. Put each company in a separate column, use the same period and currency, document adjustments, and keep accounting figures separate from operational indicators.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.