Microsoft Backlog Metric Highlights Contracted Revenue While Shares Struggle

Microsoft’s shares have been under pressure, down about 20% over the last year and trailing broader market performance, according to market commentary carried by Trefis on July 3. In that debate, attention has largely centered on how quickly the company can translate major planned spending into earnings power, especially with artificial intelligence (AI) infrastructure at the core of the investment story.

The most visible number in the conversation is Microsoft’s expected capital outlay. The Trefis write-up frames Microsoft’s roughly $190 billion capital expenditure plan for calendar year 2026 as the key test for skeptics, who question whether demand for AI is strong enough and durable enough to justify the pace and scale of spending.

But the same analysis spotlights a counterpoint it says gets less attention from investors: Microsoft’s Commercial Remaining Performance Obligation, or RPO. In plain terms, RPO represents contracted future revenue from signed customer agreements, a backlog of service commitments that the company expects to recognize over time as it delivers the underlying cloud and software services.

According to the Trefis article, Microsoft’s commercial RPO totals $627 billion. The commentary also describes the backlog as moving, not just sitting still. It states that commercial RPO grew 26% year-over-year, and it adds that this growth persists even when excluding the largest commitments attributed to Microsoft’s partner OpenAI, a distinction the piece uses to suggest broader customer demand across Microsoft’s commercial business lines.

Near-term revenue visibility is another focus. Trefis says the portion of the backlog that is expected to be recognized as revenue within the next 12 months increased 39% year-over-year. Investors often treat this kind of “near-term” backlog visibility as a announcement that new contracts are being signed and that near-term delivery capacity and spending plans may be matched with existing customer commitments.

The article’s argument is that Microsoft’s spending is not just an internal forecast. It contends the company is building capacity to serve demand that, at least in part, has already been contracted through legally binding customer commitments. Under that framing, RPO becomes a bridge between the capital-intensive buildout and the eventual revenue recognition that follows from contracted deals.

Even so, the company itself does not provide full “how” detail in the Trefis post. The article does not lay out the precise contract mix, the durability of pricing across those commitments, or how much of the spending will be directly tied to delivering backlog booked over specific periods. It also does not quantify the extent to which changes in customer consumption patterns, competitive pricing, or regulatory and procurement cycles could alter revenue recognition timing.