The important distinction is between more activity and demonstrably better outcomes. Microsoft’s figures indicate expanding use, but its own adoption guidance cautions that rising credit consumption does not establish business value. For IT administrators, that makes cost attribution and workflow measurement just as important as deployment numbers.
Copilot growth: what the numbers actually measure
During Microsoft’s October 28 earnings call, Nadella reported several adoption indicators:
- Daily Copilot users: nearly 50% growth quarter over quarter and more than fivefold growth year over year.
- Automated tasks: nearly doubled since July.
- Customers with more than 50,000 Copilot seats: increased more than eightfold year over year.
- Customers actively consuming usage-based credits: grew more than 75% during the quarter.
These measures are not interchangeable. Growth in customers using credit billing is not growth in credit revenue, nor does it mean 75% of all Copilot customers use that model. Likewise, purchased seats and daily users describe different aspects of adoption.
Rollout announcements need similar care. Nadella cited Volkswagen’s plans to bring Copilot to more than 330,000 employees; that is a planned deployment, not confirmation that every employee is already using it.
The takeaway: Microsoft is reporting broader engagement and larger commitments, not an independently audited productivity result.
Enterprise AI moves into operational workflows
PYMNTS reports that Nadella highlighted three customers to illustrate the transition from individual assistance to business-process automation:
| Organization | Work Microsoft described |
|---|---|
| Unilever | Automated order intake and trade-promotion dispute handling |
| Rolls-Royce | Jet-engine maintenance planning, inventory and supply-chain management |
| Raiffeisen Bank International | More than 20 business processes, including credit-related workflows |
These were management’s deployment examples, rather than independently measured demonstrations of savings or accuracy. Rolls-Royce’s example concerns managing maintenance workflows; it should not be interpreted as evidence that AI independently makes safety-critical engineering decisions.
The editorial significance is the change in what buyers should evaluate. A useful draft can tolerate a correction before anyone sends it. An operational workflow needs a defined response when information is missing, an action fails or a person must intervene. That is an assessment framework—not a claim about the internal controls at these customers.
Usage billing changes the budget conversation
Nadella described subscriptions as a way for IT to fund everyday assistance, while business units can fund consumption for higher-value agent work. CFO Amy Hood added a qualification: adoption of consumption pricing outside software development is likely to take longer, requiring customer education and changes to sales practices, PYMNTS reports.
Microsoft’s documentation provides a concrete example of how that model works in Copilot Studio. Pay-as-you-go billing links an environment to an Azure subscription through a billing policy in the Power Platform admin center. The organization then pays monthly for the Copilot Credits its agents actually consume. That is a product-specific arrangement, not a universal description of every Copilot offering.
For administrators, the practical implication is to identify the billing owner before expanding a workflow. “The business requested it” and “IT receives the bill” should not become competing explanations at month-end.
Microsoft’s adoption guidance recommends examining who is active, which workloads drive consumption and whether spending is concentrated. It also distinguishes consumption analytics from official billing: the Consumption Dashboard in Insights is an analysis view, while Microsoft 365 admin-center Cost Management handles official spending and billing controls for its supported scope.
A sensible review should therefore ask:
- Which team owns the workflow and its budget?
- What completed outcome counts as success?
- Are retries or abandoned results increasing consumption?
- Could a spending limit interrupt important work?
Those questions follow Microsoft’s guidance to evaluate consumption alongside outcomes—not simply celebrate a larger credit total.
Windows and GitHub bring governance into focus
Nadella also described Microsoft Execution Containers as a policy-driven layer for governing and containing agents across Windows and other platforms, integrated with Agent 365. He named OpenAI Codex, Anthropic Claude Code and Meta Muse as adopters, with Meta beginning enterprise deployment. Microsoft reported more than 50 million agents in the Agent 365 registry and over 7.6 billion agent activities audited through Purview. Registry entries and audited events should not be treated as counts of active production deployments.
For developers, PYMNTS reports that agents now open more than one-third of GitHub pull requests, with agent-generated pull requests increasing sixfold in six months. Those figures measure submitted changes, not accepted code or software quality.
Strong financial results, with a measurement caveat
Microsoft’s official release reported $92.3 billion in revenue, up 19%, for the fiscal first quarter ended September 30, 2026. Microsoft Cloud revenue reached $63.9 billion, up 30%, while Azure revenue increased 48%. Microsoft 365 consumer cloud revenue grew 17%; management attributed its sequential slowdown to comparisons against an earlier price increase.
Those results establish company-level growth, but do not isolate Copilot’s contribution.
The clearest lesson for enterprise readers is therefore practical rather than promotional: measure adoption, spending and outcomes separately. Microsoft’s own guidance makes the distinction explicit—more AI consumption is evidence of more activity, not automatically more value. The next deployment review should reward reliable work completed, not merely a busier meter.
References
- Microsoft Sees Enterprise AI Adoption Accelerate as Copilot Usage Grows - PYMNTS.com PYMNTS.com · 2026-10-29T01:25:37+00:00
- Understand your team’s Microsoft Copilot usage and spend – Microsoft Adoption adoption.microsoft.com
- Purchase and manage Copilot Credits in usage-based billing - Microsoft Copilot Studio | Microsoft Learn learn.microsoft.com