The short version: Microsoft Copilot answers from files a person can already open. If a client's permissions are messy, Copilot makes the mess visible in seconds. Before you switch it on, check sign-in protection, admin accounts and SharePoint sharing, then pilot with a small group. "Not yet, here is the plan and the date" is a better answer than a flat no or a rushed rollout.
Why does Copilot raise a permissions problem?
Because it searches everything the user can reach, and most small tenants have more open access than anyone remembers. Microsoft's own security documentation says Copilot only accesses data that users are authorised to access, and that overshared or poorly governed content can affect Copilot results and increase risk.
Before Copilot, a payroll spreadsheet in a wide-open folder stayed hidden by obscurity. Nobody went looking. With Copilot, a staff member can ask "what do people earn here?" and get an answer if the file is reachable.
Copilot has not created the weakness. It has removed the obscurity.
What does "not yet" mean in practice?
It means a short list of fixes before a pilot, not a permanent no. Most of the list is work you may already be selling.
| Check | What to look for | Why it matters for Copilot |
|---|---|---|
| Sign-in protection | MFA on every account, Conditional Access in place | A stolen password now opens an AI search tool as well as a mailbox |
| Admin accounts | Few, separate, protected | Admin accounts can reach everything |
| Sharing settings | Anyone-with-the-link links, org-wide sharing | Wide links make files discoverable |
| Sensitive sites | HR, finance, legal, client folders | These are the sites you least want surfaced |
| Leavers and guests | Old accounts, external guests with access | Forgotten access is still access |
If you are a small business owner
Ask your IT provider one question before you pay for Copilot: "Who can open our HR and finance folders today?" If the answer is "everyone" or "I will need to check", fix that first.
You do not need to delay for months. A tidy-up of a small tenant is usually days of work, not weeks. Then start with five people, not the whole company. Pair it with a written AI usage policy: the OAIC advises organisations not to enter personal information into publicly available generative AI tools.
If you are an MSP
Treat the readiness check as a fixed-price job, because the client will ask for Copilot whether you offer it or not. Microsoft publishes a deployment blueprint for remediating oversharing, and states that SharePoint Advanced Management is included with a Copilot licence. Which features a client gets depends on their licences, so confirm before you quote. The pricing hub in the MSP compliance pricing guide covers how to package fixed-price jobs.
Do the work in this order:
- Fix identity first: MFA and Conditional Access on all accounts.
- Review sharing links and org-wide sharing on SharePoint and OneDrive.
- List the sensitive sites and decide who should reach each one.
- Pilot with a small group and ask them to test with questions that should return nothing.
- Write down what you changed and the date.
Step 5 matters most later. When a client's insurer or a buyer asks how the business governs AI, a dated record answers it. The evidence problem covers why the work counts for little if you cannot show it.
A worked example: a 20-person accounting firm
An accounting firm asks for Copilot for all 20 staff. A quick look finds MFA on 17 of 20 accounts, two shared admin logins, and a client-files site open to the whole company, including a part-time bookkeeper.
The MSP says: "Yes, and here is the order. This week we finish MFA and remove the shared admin logins. Next week we restrict the client-files site. In week three, five people pilot Copilot. If their test questions return nothing they should not see, we roll out to everyone."
The client gets a date. The MSP gets three small jobs and a rollout. Nobody has to say no.
Where does CYBERWHITE fit?
CYBERWHITE does not assess Copilot or scan SharePoint permissions. We are clear about that so you do not buy the wrong thing.
What it covers is the identity foundation Copilot depends on. CYBERWHITE is a DSI SMB1001 licensed commercial holder and runs Essential 8 and SMB1001 scans against Microsoft 365. A scan takes about 5 minutes and shows MFA, Conditional Access and admin account gaps, ranked by CARS so you fix the highest-risk item first. Where a fix is a deployable policy, AutoFix can deploy it with a snapshot and rollback. Those are items 1 and 2 on the list above, and they come with evidence an assessor can use.
The proof check is a booked, guided session. You scan one tenant with us and see what an assessor would still ask for. Book it here. There is no self-serve trial.
Checklist to copy
- Confirm MFA on every account before any Copilot licence is bought.
- Reduce admin accounts and stop sharing admin logins.
- Review anyone-with-the-link and org-wide sharing.
- List the sites holding HR, finance, legal and client data.
- Remove leavers and review external guests.
- Pilot with five people and test with questions that should return nothing.
- Write down what changed, with dates.
- Review again 90 days after rollout.
For the wider framework context, the Essential 8 pillar page and the SMB1001 guide explain which of these controls count towards each standard.
Sources
- Microsoft Learn: Security for Microsoft Copilot
- Microsoft Learn: Secure and governed data foundation for Microsoft Copilot, deployment blueprint
- Office of the Australian Information Commissioner: Guidance on privacy and the use of commercially available AI products
Keep reading: AI usage policy for clients and Client refuses MFA? How an MSP puts the risk in writing