Sooner or later, every MSP gets the same email from a client: “We’d like to turn on Copilot. Is it safe?”
A plain yes leaves the risk with you. A plain no loses you the project, and the client will probably switch it on anyway. A better answer is: “Yes, once five things are in place, and we’ll keep checking them every month.” That’s Copilot governance.
Security asks whether Copilot can be misused. Governance asks who decides, what Copilot is allowed to reach, who builds on top of it, and who checks that all of that still holds in three months. For an MSP looking after many tenants, governance is what turns a risky one-off rollout into a service you can repeat for every client.
This Copilot governance checklist is written for MSPs. For the risks themselves, read Copilot security: what Microsoft 365 Copilot can see.
Why Copilot needs governance, not just a licence
Microsoft says Copilot only surfaces organisational data that each user has at least view permission for. Copilot doesn’t change who can open what. It makes everything a person can already open much easier to find.
So the hard part of a Copilot rollout isn’t the licence. It’s everything the licence exposes:
- Data: years of loose sharing that nobody noticed, because finding the files took effort.
- Agents: Copilot isn’t just a chat box any more. People can build agents on top of it, share them with colleagues and connect them to other data.
- People: staff need to know what they may paste, ask and share, and what to do when Copilot shows them something it shouldn’t.
- Time: a tenant that’s clean in week one drifts. New sites, new sharing links, new agents.
Governance covers all four, with a named owner for each.
The five parts of Copilot governance
1. Decide who decides
Before anyone touches a setting, agree three names with the client:
- A business owner for Copilot. Usually the owner, the COO or the office manager. They approve who gets a licence and settle disputes over access.
- An owner for each sensitive area. HR, finance, legal and the leadership team each name someone who confirms who should see their files.
- The MSP as operator. You run the reviews, make the changes and report back.
Write this down in a short Copilot policy. One page is enough. Without named owners, every overshared folder becomes your decision, and you shouldn’t be the one deciding who sees the payroll files.
2. Make the data ready
This is where most of the work is. Because Copilot follows existing permissions, a readiness review is really a sharing review:
- Find sites, folders and files shared with everyone or by open links.
- Ask each area owner to confirm who needs access, and narrow the rest.
- Keep the most sensitive sites out of Copilot search while the review runs.
- Label sensitive files where the client’s licence supports sensitivity labels.
Microsoft’s own guidance helps here. According to Microsoft Learn, assigning a Copilot licence in a tenant gives SharePoint admins the SharePoint Advanced Management features that support Copilot deployment, such as oversharing reports. Some features still need a separate add-on, and the list of qualifying base plans is set by Microsoft, so check it against each client’s plan before you promise anything.
3. Control who can build and share agents
Copilot agents are where governance is weakest today. People can build an agent in minutes, point it at a SharePoint site and share it with the whole company.
Microsoft gives you some controls:
- In the Microsoft 365 admin center, admins can set who may share agents built with Agent Builder: all users, specific users or groups, or no one. Microsoft Learn notes that all users is the default, and that changing the setting only applies to new sharing. Agents already shared stay shared until you change them.
- Copilot Studio agents are governed separately, through sharing limits in the Power Platform admin center.
- Microsoft Learn says Copilot Studio automatically creates a Microsoft Entra Agent ID for each new agent, so agents show up as identities of their own.
Decide with the client who may build agents, who may share them, and who approves an agent that reaches sensitive data. Then give every agent a named owner and a review date, the same as any other app. Read AI agent identity for why each agent needs its own account and owner.
4. Set the rules people follow
A short usage rule does more than a long policy nobody reads. Cover:
- Which AI tools staff may use for work, and which they may not.
- What they must never paste or upload, such as client records or passwords.
- What to do when Copilot shows them a file they shouldn’t see: report it, don’t share it.
Copilot also doesn’t stop staff using other AI tools. If the client’s people use ChatGPT or an AI note-taker on the side, Copilot governance alone misses it. Our AI usage policy template gives you one page to start from, and shadow AI explains the gap.
5. Review it every month
Governance fails quietly. Nobody notices the new “everyone” link or the agent a sales manager shared last week. Put a monthly review in the client’s service:
- New oversharing since last month.
- New agents, who built them and who they’re shared with.
- New AI apps connected to Microsoft 365, and what they can reach.
- Licence changes: who got Copilot, who left.
- A short report to the business owner, with any decisions they need to make.
Copilot governance checklist
Use this per client. Each line has an owner.
| Area | Check | Owner | When |
|---|---|---|---|
| Decision | Copilot business owner named and policy signed | Client | Before rollout |
| Decision | Owner named for HR, finance, legal and leadership files | Client | Before rollout |
| Data | Sites and folders shared with everyone or by open link listed | MSP | Before rollout, then monthly |
| Data | Sensitive areas narrowed to the people who need them | Area owners | Before rollout |
| Data | Most sensitive sites kept out of Copilot search during the review | MSP | Before rollout |
| Agents | Agent sharing set to specific users or groups, not all users | MSP | Before rollout |
| Agents | Copilot Studio sharing limits set | MSP | Before rollout |
| Agents | Every agent has an owner and a review date | Builder | Monthly |
| People | Usage rule shared, including what never to paste | Client | Before rollout |
| People | Staff know how to report something Copilot shouldn’t show | Client | Before rollout |
| Identity | MFA and sign-in rules cover every Copilot user | MSP | Before rollout |
| Review | Monthly report: new sharing, new agents, new AI apps, licence changes | MSP | Monthly |
A worked example: a 30-person accounting firm
This is an illustrative example, not a real client. The firm’s managing partner asks their MSP to turn on Copilot for everyone before tax season.
Week 1: owners and policy. The managing partner becomes the Copilot owner. The practice manager owns HR and payroll folders, and a senior partner owns client files. A one-page policy says who gets Copilot first and what staff must never paste.
Week 2: data. The sharing review finds a “Scans” folder open to the whole firm, holding years of client tax returns, and a partners’ site with an old open link. Both are narrowed. The partners’ site stays out of Copilot search until its owner confirms the fix.
Week 3: agents and pilot. Agent sharing is limited to two named staff. Ten people get Copilot. Within days, one of them builds a “client lookup” agent pointed at the client files site. Because sharing is limited, it doesn’t reach the whole firm. Its owner and scope are reviewed before anyone else uses it.
Month 2 onwards: review. The monthly report shows two new open links and one AI note-taker connected by a junior accountant. Each goes to its owner for a decision.
The firm gets Copilot before tax season. The MSP gets a monthly service line instead of a one-off project.
How Centeye helps
Running this review by hand, tenant by tenant, doesn’t scale. The Centeye Copilot security page shows how it works across every client:
- Centeye Synthwatch (early access) finds files and folders Copilot can surface to anyone, and gives each one an owner and the exact sharing fix.
- Centeye Lumen keeps a register of every AI app and agent connected to Microsoft 365, with an owner and a review date, and shows AI use outside Copilot with the browser extension.
- Centeye Gatewatch watches the sign-ins behind every Copilot user, so a stolen account with Copilot attached gets caught.
Reading agents directly from Copilot Studio and Microsoft Entra Agent ID is coming.
Want to see what Copilot can reach in one client’s tenant? Start a free Synthwatch trial.
Frequently asked questions
What is Copilot governance?
It’s the set of decisions, owners and regular checks that keep a Copilot rollout safe: who approves access, what data Copilot can reach, who can build and share agents, what staff may do, and how often it’s all reviewed.
Is Copilot governance the same as Copilot security?
They overlap. Security looks at how Copilot could be misused, for example through oversharing or a stolen account. Governance makes sure someone owns each of those risks and checks them over time.
Who should own Copilot governance at a small business?
A business owner on the client side, with the MSP running the reviews. The MSP shouldn’t decide who sees payroll or client files. The people who own that data should.
Can we stop staff from sharing Copilot agents?
Partly. Microsoft lets admins limit who can share agents built with Agent Builder, and Copilot Studio has its own sharing limits. Microsoft notes that changing the setting doesn’t undo sharing that already happened, so review existing agents too.
How often should we review a client’s Copilot setup?
Monthly is a sensible default for most small businesses. Run an extra review after big changes, such as a reorganisation, a new department or a large batch of new licences.
New to the terms? See shadow AI, AI agent, OAuth grant and non-human identity in our glossary.
Copilot data access, SharePoint Advanced Management with Copilot licences, agent sharing settings and Copilot Studio sharing limits as described on Microsoft Learn, November 2026. Microsoft Entra Agent ID for Copilot Studio agents from Microsoft Learn. Licensing and settings change, so check each client’s tenant. The worked example is illustrative. Microsoft, Microsoft 365, Copilot, Copilot Studio, SharePoint and Entra are trademarks of the Microsoft group of companies.