Paid Microsoft 365 Copilot seats (latest disclosed)no data
— millions
on track >= 50 · off < 40manual ↗
connector returned no usable reading · checked 2026-10-19
Radar · Enterprise absorption · T2 · 2029 · CALL
Microsoft publicly states at least 100 million paid Microsoft 365 Copilot seats in an earnings release, earnings call, or SEC filing dated on or before 2028-12-31.
Paid Copilot seats are the only enterprise AI adoption number a hyperscaler publishes on a fixed quarterly cadence. Crossing 100 million, about one in five commercial Microsoft 365 seats, would confirm that knowledge-work AI is being bought as a standard license, not a pilot. It also anchors the inference-demand side of Azure's capex.
Registered at 60% on September 8, 2026. Engine repriced 14 times; now 31%.
Dated rungs. Each is scored on its own; the thesis does not get credit for the ladder until the rungs land.
filled bar · my probabilityhollow dot · engineamber date · due, awaiting adjudication
m1 · 2027-07-31 · 70% · Microsoft states at least 50 million paid Microsoft 365 Copilot seats at or before its FY2027 Q4 earnings release.
m2 · 2028-01-31 · 55% · Microsoft states at least 75 million paid Microsoft 365 Copilot seats at or before its FY2028 Q2 earnings release.
Registered thresholds. Status is computed from the latest public reading.
Paid Microsoft 365 Copilot seats (latest disclosed)no data
— millions
on track >= 50 · off < 40manual ↗
connector returned no usable reading · checked 2026-10-19
Microsoft 365 commercial paid seatsno data
— millions
on track >= 480 · off < 460manual ↗
connector returned no usable reading · checked 2026-10-19
Would raise my number
Would cut it
6 personas on one model (openai/gpt-5.6-sol); other vendors were unavailable this run, so read this as one model's persona-averaged view.
32%
grid-and-power-planner · openai/gpt-5.6-sol
I use the reference class of paid enterprise SaaS add-ons already at tens of millions: growth generally decelerates as early adopters saturate, and vendors sometimes retire seat metrics. From the reported 30 million-plus in FY2026 Q4, Microsoft needs more than 3.3x growth in roughly ten quarters, about 1.62x annually compounded. That is feasible against Microsoft 365’s large base but aggressive for a premium-priced add-on. The quoted FY2029 revenue model implies only 60–75 million seat-equivalents by mid-2029 and includes non-seat revenue. I assign 0.40 to reaching the threshold and 0.80 to a qualifying disclosure conditional on reaching it.
38%
semiconductor-supply-chain-analyst · openai/gpt-5.6-sol
My reference class is large-enterprise SaaS add-ons expanding across an established productivity-suite base. From the supplied 30 million in July 2026, Microsoft must grow paid seats 3.3-fold in roughly 29 months, about 65% annualized. That is feasible given Microsoft 365 distribution, but demanding at this scale. The cited FY2029 revenue model implies only 60–75 million seat-equivalents after the deadline and includes E7 and consumption revenue, making 100 million paid seats materially above that trajectory. I also discount for the conjunctive disclosure requirement: Microsoft must both reach the threshold and explicitly publish a qualifying paid-seat count rather than shift to revenue, users, customers, or agents.
32%
enterprise-cio · openai/gpt-5.6-sol
Using the reference class of enterprise productivity add-ons moving from early adopters toward one-quarter of the installed base, I estimate a 0.10 crossing hazard through 2027 and 0.32 during 2028, conditional on not crossing earlier. That gives about 0.39 for operationally reaching 100 million. The supplied FY2026 Q4 count above 30 million must more than triple in roughly 2.4 years, while the cited FY2029 revenue model implies only 60–75 million seat-equivalents later. Procurement, security review, and renewal cycles constrain growth. Applying about 0.82 for Microsoft continuing to disclose an unambiguous paid-seat count near the threshold yields 0.32.
32%
credit-analyst · openai/gpt-5.6-sol
Starting from the supplied FY2026 Q4 disclosure of over 30 million seats, reaching 100 million by December 2028 requires roughly 65% annualized growth. The reference class is enterprise productivity-software add-on diffusion: adoption can scale rapidly but usually decelerates as early adopters saturate. The cited FY2029 revenue model implies only 60–75 million seat-equivalents after the deadline. Bundling could increase reported paid seats, but E7 and consumption revenue weaken that inference. Resolution is conjunctive: Microsoft must reach the threshold and explicitly publish an eligible count; discontinuing the KPI means a miss. No current indicator data offsets these risks.
36%
geopolitics-policy-analyst · openai/gpt-5.6-sol
Starting from over 30 million in July 2026, reaching 100 million by end-2028 requires roughly 65% annual compounded seat growth. The relevant reference class is enterprise productivity add-ons: adoption can compound rapidly from tens of millions, but procurement cycles, discounting, and bundle migration usually slow penetration after early adopters. The cited FY2029 revenue model implies only 60–75 million seat-equivalents by mid-2029, materially below the threshold. Even if actual seats reach 100 million, the literal rule adds disclosure risk because Microsoft could pivot to revenue, customer, usage, or bundled-suite metrics. I therefore place the probability below the forecaster’s 0.6.
19%
superforecaster-statistician · openai/gpt-5.6-sol
I use a 0.20 base rate for premium enterprise-software add-ons tripling from roughly 30 million paid seats within 2.5 years while also receiving a qualifying official disclosure. Microsoft’s distribution and the reported 30-million starting point raise the adoption case, but reaching 100 million requires about 65% annualized seat growth. The cited FY2029 revenue model implies only 60–75 million seat-equivalents later than the deadline, even including broader revenue. Continued seat disclosure is an additional failure mode as Microsoft may pivot to revenue, bundle, customer, or agent metrics. No calibration table was supplied to justify the forecaster’s 0.6.