Word's Copilot needs a license, a role, and up to a day to appear

The setup

Turning on Copilot inside Word is not a Word-level setting. Microsoft's own setup and licensing documentation, as it reads on 16 September 2026, routes the task through three separate admin centers, Microsoft 365, SharePoint, and Purview, each requiring its own role assignment. Licensing is described plainly: Copilot "is included as part of the Microsoft 365 E7 subscription plan" or purchased "as an add-on to other licensing plans" through the admin center marketplace, a partner, or an account team. Only after a license is assigned does Copilot appear inside Word itself, and Microsoft's documentation warns users may "need to wait up to 24 hours" and restart the app before it shows up.

What the documents show

The setup guide frames licensing as only the first step. It recommends multifactor authentication, unified audit logging through Microsoft Purview, and a review of conditional-access and SharePoint sharing policies before rollout, specifically to prevent Copilot from surfacing oversharing that already existed in a tenant's file permissions. The parent Copilot documentation hub, read the same day, separately discloses that Microsoft now offers "Anthropic as a subprocessor," an opt-in a tenant chooses independently of the Word licensing steps above. Both pages are Microsoft's own admin-facing documentation, not marketing copy, and neither states a specific list price for the add-on license.

The friction

The documentation itself discloses the friction: Copilot licenses cannot be assigned to cross-tenant users or guests, education customers see the license listed under a different bundle name depending on their A3 or A5 tier, and the recommended readiness checklist includes running a SharePoint permission-state report before deployment specifically because Copilot can expose content a user technically already had access to but had never found. None of that is a hidden defect; it is the documented cost of connecting a generative assistant to an existing, imperfectly governed file system.

What changed in the work

For an IT administrator, the task changed from installing an application to auditing a permissions surface first and assigning a license second; the setup guide's own phased pilot-deploy-operate structure treats license assignment as the easy part and oversharing review as the real project. That is an editorial reading of the guide's own emphasis, not a claim Microsoft states as a warning.

• Which admin center in your organization currently owns the Copilot rollout decision?
• Has anyone run the SharePoint oversharing report the setup guide recommends before assigning licenses?
• Do your users know which subprocessors, including Anthropic, are opted into for their tenant?

The setup documentation reads less like a feature announcement and more like a security project plan with a licensing line item attached.