To roll out organizational Copilot, first decide which capabilities users need, then provision the appropriate entitlement and validate the apps and data they will use. Buying seats does not assign them, but there is also no universal second “enable Copilot” switch that must be turned on after every assignment.
This article covers Microsoft Copilot for work, formerly Microsoft 365 Copilot. Consumer subscriptions, GitHub Copilot, and Copilot Studio have different setup and licensing paths. Official guidance checked October 14, 2026.
Define the pilot and check its prerequisites
Write down the pilot’s actual tasks: drafting in Word, summarizing a mailbox, or finding information across work files, for example. Check each task against Microsoft’s current requirements. A generic chat test cannot validate every app integration.
- License: compare the user’s base subscription and intended Copilot entitlement with the current licensing options. Eligible Copilot Chat access and paid work-grounded features are not interchangeable. Some bundles include Copilot; do not assume every tenant needs a separate purchase.
- Identity and services: use the intended work or school account. Ensure the pilot has the services its tasks need, such as the appropriate mailbox for email-related work.
- Client: record the Office app build and update channel and confirm a supported configuration. An old minimum build number does not establish current support.
- Data: choose a small set of current, appropriately shared documents. Correct oversharing before the pilot; do not give a test group broad file access merely to improve answers.
Separate duties. A license administrator can handle assignment; identity, SharePoint, and compliance specialists should own changes in their areas. Routine rollout is not a reason to grant every participant Global Administrator.
Assign the approved entitlement and test the intended experience
- Check the tenant’s existing products. In the Microsoft 365 admin center, inspect Billing > Licenses. Confirm the approved Copilot product and capacity, including any entitlement already supplied by a bundle. If procurement is needed, confirm the offer, prerequisite plan, commitment, and quantity with your purchasing owner before ordering.
- Assign to the pilot users. Select the relevant product and use Assign licenses. Alternatively, select a user under Users > Active users and use Licenses and Apps. Preserve the user’s existing base license and required services. Resolve assignment errors rather than assuming a submitted change succeeded.
- Verify the result for one pilot account. Confirm that its product assignment is present and that the account is in the intended tenant. Microsoft’s license-assignment instructions cover direct and group-managed assignments.
- Prepare the app through the managed deployment process. Apply supported updates and required connected-experience policies. Use the Copilot area of the admin center for applicable controls, not a supposed Org settings switch exposing separate Graph and Exchange data-source toggles.
- Allow provisioning and refresh the client. Microsoft’s deployment guide allows up to 24 hours for Copilot to appear in some apps after assignment. Have the user restart or refresh and use the licensed account.
- Run a task-specific acceptance test. For a document pilot, use a harmless test file containing a few known facts. Request a summary and verify those facts against the file. For work search, request a known, authorized source and inspect the citation. Record what works separately from what remains unavailable.
Audit logging supports investigation and governance; it is not a switch that provides Copilot with content for grounding. Keep security and compliance work in the deployment plan without presenting every governance recommendation as a technical activation dependency.
Resolve pilot failures before expanding the rollout
The button is absent
Check the exact product assignment, account, app build, update channel, and policy. Compare the same account in a supported web experience. If web works but desktop does not, investigate the client before changing licensing for the whole group. Do not use “version 2311 or later” as a permanent rule for all apps.
Chat works but cannot find project data
Confirm that the conversation has the intended work-grounding capability, then test one explicitly referenced file the user can open. A generic response does not prove that the administrator forgot to enable Microsoft Graph. Use the work-grounding troubleshooting guide to separate scope, permission, and discovery problems.
Access fails for several pilot users
Ask the administrator to inspect service health and assignment errors, then compare failure timestamps. Give the network or identity team the actual error instead of disabling protection policies. Preserve the pilot’s evidence so Microsoft support can distinguish a provisioning problem from an unavailable feature.
Decide whether the pilot is ready to expand
Use acceptance criteria tied to real work: the required app opens, the intended users can complete the task, cited information can be verified, and access boundaries remain appropriate. Track unresolved failures and owners. Expand only after those conditions are met; elapsed time alone is not proof of a successful deployment.