Microsoft Copilot Reaches 20 Million Paid Enterprise Seats

Satya Nadella said on Microsoft's FY26 Q3 earnings call that Microsoft 365 Copilot now has 20 million paid enterprise seats (Microsoft transcript; TechCrunch; CNBC). Nadella said the number of companies deploying more than 50,000 Copilot seats has "quadrupled" and named Bayer, Johnson & Johnson, Mercedes-Benz and Roche as customers with more than 90,000 seats each (TechCrunch; Economic Times). He highlighted an Accenture agreement for over 740,000 seats, calling it "our largest Copilot win to date" (TechCrunch; Economic Times).

Per the earnings call coverage, Nadella reported that "Copilot queries per user were up nearly 20% quarter over quarter" and asserted that "weekly engagement is now at the same level as Outlook" (CNBC; TechCrunch). He also said Copilot is not tied to a single backend, noting that users have access to multiple models in chat and that Copilot supports offerings such as Anthropic's Claude alongside other systems (TechCrunch; Economic Times).

Industry-pattern observations: Large-seat enterprise deployments are typically driven by centralized procurement and the ability to integrate AI features into core productivity flows. Companies that achieve seven-figure seat counts often use SSO, tenant-wide policy controls, and workflow automation to scale consumption across business units. Agent-style workflows that perform multi-step tasks inside documents can materially raise engagement metrics because they reduce context switching and embed outputs where work happens.

The announced 20 million paid seats is a commercial-scale adoption milestone that several outlets flagged during Microsoft's earnings coverage (CNBC; TechCrunch; Economic Times). For practitioners, the combination of seat scale and reported week-over-week engagement parity with email suggests enterprise buyers are moving beyond pilot phases into broader rollouts, which increases operational pressure on deployment governance, prompt safety, and data residency controls. Public reporting also emphasizes multi-model support, which reflects a broader industry trend toward model heterogeneity rather than single-vendor dependence.

Observed patterns in similar rollouts: Observers should track three indicators over the next quarters: 1) seat churn and net-new seat adds reported in investor updates; 2) metrics for active usage such as queries per user and tasks completed via agent mode; and 3) product controls and integration primitives released for tenant management, auditing, and model routing. Reporting to date comes from the earnings call and press coverage; Microsoft's FY26 Q3 transcript and follow-up product documentation are primary sources for validation (Microsoft investor materials; TechCrunch; CNBC).

What is reported here is based on statements Nadella made on the FY26 Q3 earnings call and contemporaneous coverage by TechCrunch, CNBC, Economic Times and other outlets. Microsoft's public earnings transcript and product documentation are the originating sources for the numerical claims cited above. Microsoft has not published a separate detailed usage breakdown beyond the figures quoted on the call in the sources cited.

For practitioners: Enterprises integrating Copilot at scale should prioritize tenant-level policy configuration, usage monitoring, and data access controls. Observers running deployments or evaluating vendors will want explicit SLAs for model routing, audit logs for agent actions, and clarity on which external models (for example Claude) are available and how vendor-specific routing is controlled.