For managers and admins

Rolling out Copilot to a team: 10 questions to settle first

Short answer: Before you train anyone, write down which Copilot label each person has, what they may paste in, who can build and share agents, and who answers questions. Most rollout problems come from people following tutorials for features they do not have.

Last checked against Microsoft docs: Oct 20, 2026

Why settle these first

People see a Copilot button and assume it can reach their files. Some can, some cannot, depending on the license and your settings. If you answer the ten questions below once and share the answers, your team stops guessing and stops filing the same tickets.

A quick note to your Copilot admin

Copy this into an email or a Teams chat and fill in the brackets. Every guide on this site links here.

Hey [name], quick one. I want to try Copilot for [task].

Do I have the full Microsoft 365 Copilot license, or just Copilot Chat?
Can I use agents?
Can Copilot see our SharePoint files, like [site or folder]?

Thanks!
[your name]

For managers: the ten rollout questions

Settle these once for the whole team and share the answers.

1. Which Copilot label does each person have: Copilot Chat (Basic), M365 Copilot (Basic), or M365 Copilot (Premium)?
2. Which apps can people use Copilot in: the browser, Teams, Outlook, Word, Excel, PowerPoint?
3. What information may people paste into Copilot, and what must stay out?
4. Which SharePoint sites and Teams are shared too widely today?
5. Which sensitivity labels and data loss prevention (DLP) rules apply to Copilot?
6. Who can create agents, and who can share them with others?
7. Do the people an agent is shared with need a license to use it?
8. Is Copilot Cowork turned on, and which spending policy controls its cost?
9. Who reviews Copilot output before it goes to customers or leadership?
10. Who do people ask when a feature is missing or an answer looks wrong?

(Questions from stuckwithcopilot.com/guides/rolling-out-copilot/)

What a good answer looks like

Labels and apps (1, 2): a short table by team. People can check their own label at copilot.cloud.microsoft. See Which Copilot do I actually have?
Data rules (3, 4, 5): one paragraph in plain words, plus a list of sites to fix first. See Before you turn on Copilot: check who can see what.
Agents (6, 7): who can build, who can share, and whether people they share with need a license. See Plan your first Copilot agent.
Cowork (8): whether it is on, for whom, and the spending policy that limits cost.
Review and help (9, 10): a named person or channel.

A simple order to roll out

Answer the ten questions and share them in one place.
Fix the most widely shared sites before you turn on access to work data.
Start with one text-only task everyone has, like the weekly project update.
After two weeks, collect what went wrong and update the answers.

Questions people ask

What should I decide before rolling out Copilot?

Which Copilot label each person has, which apps they can use it in, what they may paste in, who can build and share agents, how Cowork cost is controlled, and who answers questions.

Where can people check which Copilot they have?

At copilot.cloud.microsoft with their work account. The which Copilot guide explains what the label means.

Cite or share this guide

Rolling out Copilot to a team: 10 questions to settle first. Stuck with Copilot. https://stuckwithcopilot.com/guides/rolling-out-copilot/ Last checked Oct 20, 2026.

One Copilot idea a week

One idea a week that makes your job easier, makes you smarter, and gets your Copilot doing more for you. Something genuinely cool, not a hack. Built for people in sales, marketing and ops.

Official references

Last checked against Microsoft docs: Oct 20, 2026.