Microsoft (MSFT) CFO says capital expenditures were lower than guidance in Q1, as some third-party capacity deliveries we expected in Q1 were delayed

Microsoft (MSFT) CFO says capital expenditures were lower than guidance in Q1, as some third-party capacity deliveries we expected in Q1 were delayed.

Capex prints that land below guidance purely on delivery timing have historically been read as quarter-shifting rather than as a change in the buildout trajectory, and the phrasing here points squarely at that case: third-party capacity arriving late rather than the company pulling spend. The distinction that matters is timing versus intent, since a deferred delivery typically reappears in the following quarter's print and steepens the sequential ramp, whereas a genuine step-down in commitment would signal something different about demand expectations for AI workloads. For the megacap cloud names, the relevant transmission runs from the capex line through depreciation guidance and into the cloud segment's margin and growth capacity, with constrained capacity historically framing Azure-type growth as supply-limited rather than demand-limited. The named culprit, third-party deliveries, also implicates the leased datacenter and colocation channel rather than Microsoft's own construction, which has tended to be the lumpier, less controllable portion of the capacity stack. The follow-ons are the next quarter's capex run-rate, any catch-up language on the delayed capacity, and whether management ties cloud revenue guidance to capacity availability. As CFO commentary on timing mechanics, this is at the lower end of the materiality scale unless the next print fails to show the recovery.