Summary
- Microsoft reported $329.1 billion of additional leases, primarily for datacentres, that had not commenced as of 30 June 2026.
- Some arrangements remain subject to contractual conditions; the leases are scheduled to begin from fiscal 2027 through fiscal 2033 and run for one to 20 years.
- The balance is not current debt, current-year capex, cash already paid or computing capacity already available to Azure customers.
- Microsoft will extend the estimated useful lives of datacentres and office buildings from 15 to 25 years at the start of fiscal 2027.
- That estimate shifts more future datacentre leases from finance to operating classification, moving reported calendar-2026 capex from roughly $190 billion to roughly $175 billion.
- Management says the underlying calendar-2026 investment expectation is unchanged; locations, lessors, power, annual commencement amounts and the contingent share remain undisclosed.
The largest number belongs to a future state
Microsoft’s annual filing places $329.1 billion beside a precise qualifier: these are additional leases that had not yet commenced at the balance-sheet date. Most relate to datacentres. They are expected to start over fiscal years 2027 to 2033, with terms ranging from one to 20 years, and some arrangements still depend on contractual conditions being satisfied.
Each part of that description limits what the headline can prove. “Additional” separates the population from leases already reflected in recognised operating- and finance-lease liabilities. “Not yet commenced” means Microsoft had not obtained the right to use the relevant assets under the lease start condition at 30 June. “Primarily” means the portfolio is not exclusively datacentres. “Some arrangements” means the full total should not be treated as equally unconditional.
The figure therefore describes a planned control surface. It may secure future buildings, space or infrastructure needed to expand cloud and AI capacity, but it does not count operating megawatts, installed accelerators or customer-ready regions. Nor is it $329.1 billion of cash paid in one year. Cash payments, lease recognition and service availability occur on different clocks.
A point-in-time balance is not a gross bookings number
The comparable disclosure a year earlier was $92.7 billion, primarily for datacentres, with planned starts from fiscal 2026 through fiscal 2031. The new balance is about 3.55 times as large. That comparison shows a dramatic expansion in Microsoft’s uncommenced-lease exposure; it does not establish that the company signed exactly $236.4 billion of net-new contracts during the year.
The population rolls forward. Some previously uncommenced leases can start and leave the balance. Other arrangements can be added, revised or fail a condition. Without a reconciliation of additions, commencements, modifications and cancellations, subtracting the two snapshots creates a change in balance, not a contracting-flow measure.
That caveat does not make the increase unimportant. It shows that Microsoft has assembled a far larger pipeline of future leased infrastructure at the same time that Azure demand, according to management, still exceeds available capacity. The missing bridge matters because it would reveal how quickly this commercial promise can become usable supply.
Commencement is the hinge between promise and accounting
A lease generally enters the recognised balance-sheet population when it commences—when the right to use the asset becomes available under the arrangement. That event can turn an off-balance-sheet disclosure into a recognised right-of-use asset and lease liability. It still does not prove that a datacentre is serving production workloads.
Physical delivery has its own gates: land and permitting, utility interconnection, building completion, electrical and cooling systems, network paths, hardware delivery, commissioning and customer deployment. A lease may commence at a different point from full technical readiness. The filing does not disclose how its contracts define that point.
This makes the annual start profile the most useful missing denominator. A single total stretching through fiscal 2033 cannot show whether commitments are concentrated in the next 18 months or back-loaded. It also cannot show how much is conditional, how much power is attached, or which markets receive capacity first.
Why $15 billion can leave capex without leaving the build
The earnings call introduces a second measurement boundary. At the start of fiscal 2027, Microsoft will extend the estimated useful lives of datacentres and office buildings from 15 years to 25 years. Management says the change reflects operating history and expected use. It affects the timing of future depreciation and should provide only a minimal benefit to fiscal-2027 operating income.
The larger presentational effect is on future leases. Microsoft says the longer estimated life will cause more datacentre arrangements to be classified as operating leases rather than finance leases. Its reported capex includes finance leases but excludes operating leases. As a result, the calendar-2026 capex expectation moves from the roughly $190 billion stated in April to approximately $175 billion.
This is not management saying that it removed roughly $15 billion of physical infrastructure from the plan. The company explicitly says that, outside the useful-life impact, its calendar-2026 investment expectation remains unchanged. The expenditure changes accounting bucket. Future operating-lease costs will still affect cash flows and expenses, even though the full lease value does not enter the capex measure at commencement in the same way as a finance lease.
Useful life is an estimate, not an engineering warranty
Moving from 15 to 25 years can sound like Microsoft has made buildings last ten years longer overnight. It has not. Estimated useful life is an accounting judgement about the period over which an asset’s depreciable cost is allocated. It is informed by operating experience and expected use, but it does not guarantee that every site will remain equally productive for a quarter-century.
Buildings and some core systems can serve for decades while their contents turn over much faster. Microsoft said roughly two thirds of its June-quarter capex went to shorter-lived assets, primarily CPUs and GPUs, while the balance went to longer-lived assets. A datacentre shell, electrical plant and cooling system therefore sit on a different replacement cycle from the compute installed inside.
The distinction matters for return analysis. Extending a building’s depreciation period lowers the annual allocation of that building cost, all else equal. It does not slow the obsolescence of accelerators, guarantee utilisation or remove maintenance and retrofit expense. Management’s statement that the fiscal-2027 operating-income benefit will be minimal also constrains claims of a large near-term profit lift.
The commitment creates optionality and counterparty risk
Leasing lets Microsoft reserve a path to capacity without owning every facility. It can bring specialist developers, landlords and financing structures into the build. For a company trying to close a supply gap, that access can be valuable: the lease pipeline may reserve scarce land, power and construction capability before customers can use it.
The same structure distributes risk rather than eliminating it. Conditions may fail. Projects may arrive late. A lessor can depend on financing, utilities, contractors and permitting. Microsoft can face long-duration payment obligations if demand, hardware economics or location requirements change. The filing gives no facility list with which to match those risks to individual markets.
The $329.1 billion figure is thus both a demand signal and a dependency map. It shows management willing to arrange a very large future footprint. It also shows how much of that footprint depends on assets becoming available over time through third-party contracts.
What will turn the disclosure into capacity
The next evidence should separate four ledgers. First, Microsoft can report how much of the uncommenced portfolio starts each year and how much remains conditional. Second, operating data can show power energised, buildings commissioned and regions made generally available. Third, financial reporting can distinguish cash paid, finance-lease additions, operating-lease expense and property-and-equipment purchases. Fourth, demand and utilisation can show whether the new supply earns an adequate return.
Quarterly capex alone cannot do all four jobs. In the June quarter Microsoft reported $41 billion of capex, including $5.6 billion of finance leases, while cash paid for property and equipment was $35.8 billion. Those three numbers already demonstrate why one headline cannot substitute for the underlying schedules.
The annual filing exposes the scale of the next infrastructure wave more clearly than it establishes its delivery. Microsoft has arranged $329.1 billion of leases that mostly point toward datacentres; it has not switched on $329.1 billion of cloud capacity. And when reported capex falls to roughly $175 billion because leases change category, the physical investment has not necessarily fallen with it. Commencement, energisation and productive use remain the events that will close that gap.