How to enable Microsoft 365 Copilot for a pilot group

Enabling Microsoft 365 Copilot for a pilot group is mostly licensing — assign the add-on to a group — plus a data-readiness check so the first thing the pilot finds is not a payroll spreadsheet on an open site, and a few app settings that decide whether Copilot in Teams meetings works at all. The technical part takes an afternoon; the pilot's value depends on who is in the group and what you ask them to try.

The full order of operations — data security first, then licensing, permissions, adoption, and measurement — is the Microsoft 365 Copilot rollout learning path; the prerequisites and the pilot design are in Copilot rollout prerequisites and Copilot pilot best practices. This page is the enablement.

Prerequisites

• Copilot add-on licences purchased (see Copilot licensing for eligibility and the Chat tiers that need no add-on).
• License Administrator (assignment), SharePoint Administrator (oversharing reports), Teams Administrator (meeting policy).
• Pilot users on Microsoft 365 Apps Current Channel or Monthly Enterprise Channel — Semi-Annual lags Copilot features by months. Check with the deployment rings guide.
• A pilot group of 20–50 people across roles, with a sponsor, a Teams channel for feedback, and a defined six-to-eight-week window.
• Entra ID P1 or higher if you want to gate Copilot behind Conditional Access (it is a cloud app like any other).

Steps

1. Run the oversharing check

SharePoint admin center → Reports → Data access governance: run Sharing links and Sensitivity labels applied reports, and — the important one — Oversharing baseline report for sites (part of SharePoint Advanced Management, included with Copilot licences). Sort by Everyone except external users permissions. For the sites that should not be broadly readable, either fix permissions or turn on Restricted Content Discovery so Copilot ignores them without breaking direct access. The rationale is in Copilot data access and permissions.

2. Create the licensing group

An assigned (static) security group LIC-Copilot-Pilot with the pilot users. Assign the Copilot licence to the group via group-based licensing; leave all Copilot service plans enabled. Static rather than dynamic so seats are added deliberately.

3. Check the Copilot settings page

Microsoft 365 admin center → Copilot → Settings. Review: Data, privacy, and security (web search grounding on or off — most pilots leave it on and note it), Copilot in Bing/Edge/Windows (the Chat entry points), Agents (whether pilot users can install agents from the store; see Copilot agents and Agent Store governance), and the Pin Copilot Chat setting for Teams and Outlook.

4. Teams meeting policy

Copilot in meetings needs transcription. Teams admin center → Meetings → Meeting policies → the pilot policy: Transcription: On, Copilot: On with saved transcript (or On without saved transcript if privacy requires, at the cost of post-meeting recap). Assign the policy to the pilot group. The trade-offs are in Copilot in Teams meetings.

5. Optional: Conditional Access

If you want Copilot behind compliant devices, the existing all-apps policies already cover it. To add a Copilot-specific rule, target the Microsoft 365 Copilot and Microsoft 365 Chat cloud apps.

6. Brief the pilot

A one-page start guide: where Copilot appears in each app, three prompts per role to try in week one (the use cases by role and prompt engineering guides supply them), what to do when it gets something wrong, and where to post feedback. Schedule a 30-minute check-in in weeks two and five.

Verify

• A pilot user opens Word: the Copilot button is on the ribbon; in Teams, Copilot appears in the left rail and in a test meeting's transcript panel; in Outlook, Summary by Copilot appears on a long thread.
• Microsoft 365 admin center → Reports → Usage → Microsoft 365 Copilot shows active users and per-app usage within a few days (it is the source for the pilot report).
• Copilot → Settings changes are reflected in what pilot users see (web grounding toggle, agent store).
• A prompt like "find documents about [a sensitive project]" from a pilot user who should not have access returns nothing — the oversharing check worked.

Roll back

Remove the user from LIC-Copilot-Pilot; the licence is released at the next processing pass and Copilot disappears from the apps at next launch. Copilot-generated content the user saved stays theirs. Meeting transcripts already saved remain under the existing Teams retention rules. Nothing in steps 1 or 3 needs undoing — an oversharing fix is an improvement regardless of Copilot.