Copilot Readiness Assessment: Checklist and Steps (2026)
A Copilot readiness assessment checks whether your Microsoft 365 tenant, your data and your people are ready for Microsoft 365 Copilot before you buy licences for everyone. It answers three questions with evidence: can Copilot run for the people who will get it, will it show anyone content they should not see, and which tasks is it worth using for. Below is the exact checklist, scorecard and report outline I use with clients, so you can run it yourself or know what a good assessment from a consultant looks like.
Quick answer
A Copilot readiness assessment checks four areas before you roll out Microsoft 365 Copilot: licences, data and permissions, security, and people. Start with permissions: Copilot shows users anything they can already open, so fix oversharing in SharePoint and OneDrive first.
1. What a Copilot readiness assessment is (and isn't)
It is a short, evidence-based review that ends in a decision: ready, ready with conditions, or not yet, plus a dated list of fixes and a pilot plan.
It is not a licence sale, and it is not a full security audit. Every finding should change a decision. If something you check does not affect whether, where or how you roll out Copilot, leave it out of the report.
2. The 15-point Copilot readiness checklist
Use this as the quick version. Each item is explained in the steps below.
- Everyone in the pilot has a qualifying Microsoft 365 base licence.
- The Microsoft 365 Copilot readiness report in the admin center has been reviewed.
- Microsoft 365 Apps are on a supported update channel for Copilot.
- Every pilot user has OneDrive and an Exchange Online mailbox.
- Working files live in SharePoint, OneDrive or Teams, not file servers.
- Teams meeting transcription is allowed where you want meeting summaries.
- No sensitive sites are shared with Everyone or Everyone except external users.
- Anyone-with-the-link sharing is limited or switched off for internal content.
- Every SharePoint site and Team has at least two active owners.
- HR, finance, legal and leadership sites are locked down or excluded from Copilot.
- Sensitivity labels are published and actually applied to confidential content.
- Auditing is on, so Copilot activity can be reviewed later.
- The busiest sites are free of obvious duplicates and outdated policies.
- Three to five specific use cases are agreed with the teams that will use them.
- A pilot group and success measures are agreed before licences are assigned.
3. Check licences and technical readiness
Microsoft 365 Copilot is an add-on. Each person needs a qualifying Microsoft 365 or Office 365 base licence, such as Business Standard, Business Premium, E3 or E5, before the Copilot licence can be assigned.
In the Microsoft 365 admin center, open Reports, then Usage, and find the Microsoft 365 Copilot readiness report. It shows who has the prerequisite licences and apps, and it is the fastest way to see who is technically eligible.
- Microsoft 365 Apps installed and on an update channel Microsoft currently supports for Copilot (check Microsoft's list, as it changes).
- A OneDrive and an Exchange Online mailbox for every pilot user, since Copilot works from both.
- Files people actually work on stored in OneDrive, SharePoint or Teams, not on a file server or local drive Copilot can't read.
- Meeting policies that allow transcription for the meetings you want summarised.
Note shared mailboxes, generic accounts and anyone still on on-premises Exchange. Those are where Copilot features in Outlook and Teams most often go missing later, and where pilot users raise the first support tickets.
4. Measure data exposure (the most important step)
Start in the SharePoint admin center with a list of active sites, owners and sharing settings. Copilot licences include SharePoint Advanced Management, which adds the data access governance reports. Run them to find:
- Sites shared with Everyone or Everyone except external users.
- Sites and files with large numbers of sharing links, especially Anyone links.
- Sites with sensitivity-labelled content that is still widely shared.
- Sites with no owner, or owners who have left the company.
Rank findings by how sensitive the content is, not by how many files are affected. One open HR folder matters more than a hundred open marketing drafts.
For sites you can't fix before the pilot, use Restricted Content Discovery to keep them out of Copilot and organisation-wide search while the people who need them can still open them. It buys time; it does not replace fixing the permissions.
5. Review labels, DLP and auditing
In Microsoft Purview, check whether sensitivity labels are published and, more importantly, used. A label policy applied to almost nothing gives no protection.
Record which labels encrypt content, whether any data loss prevention policies cover Microsoft 365 Copilot, and whether auditing is on. Purview's data security posture management for AI gives a useful starting view of how AI tools interact with sensitive data.
If none of this exists yet, recommend a small starting set, such as Public, Internal and Confidential, with Confidential applied first to HR, finance and legal libraries. A simple scheme people use beats a detailed one nobody applies.
6. Check content quality
Copilot answers from what is in your tenant. If the current policy sits next to five old drafts, it may quote the wrong one.
Sample the five busiest sites and note duplicate documents, outdated policies, files named final-v3, and sites with no activity for years. You don't need to clean everything before launch, but the pilot group should work in areas where content is current.
7. Choose use cases and the pilot group
Talk to two or three teams and list the tasks that take them the most time: drafting reports, summarising long email threads, catching up on meetings, finding past work. Pick three to five specific use cases and write down how you'll measure each, such as time to first draft or meetings caught up per week.
Choose 10 to 30 pilot users who do those tasks weekly and already work mostly in Microsoft 365. Mix enthusiasts with sceptics; you'll get more honest feedback. The Copilot Dashboard in Viva Insights helps you track adoption once the pilot starts.
8. Score your readiness
Score each area at the end. One blocker in data exposure is enough to say not yet, even if everything else is green.
| Area | Ready | Not yet | Blocker |
|---|---|---|---|
| Licences and apps | All pilot users eligible in the readiness report | A few users missing apps or channels | Base licences missing for the pilot |
| Data exposure | No sensitive sites open to everyone | Some broad sharing on low-risk sites | HR, finance or legal content open to everyone |
| Ownership | Every site has two active owners | Some sites with one owner | Many orphaned sites |
| Labels and policies | Labels applied to confidential content | Labels published but rarely used | No labels and no plan |
| Content quality | Pilot areas current and tidy | Duplicates in some pilot areas | Pilot areas full of outdated files |
| People and use cases | Use cases and measures agreed | Use cases vague | No pilot group or owner |
9. Red flags that mean 'not yet'
- An HR, payroll or board site shared with Everyone except external users.
- Thousands of Anyone links on internal documents.
- Leavers still listed as the only owners of important sites.
- Salary or contract files appearing in a normal user's search results.
- Leadership asking for Copilot for everyone on day one, with no pilot.
None of these mean Copilot is a bad idea. They mean fix first, then pilot, then roll out.
10. What the final report should include
A good assessment ends with a document leadership can read in ten minutes:
- A clear decision: ready, ready with conditions, or not yet.
- The scorecard, with one line of evidence per area.
- Oversharing findings ranked by risk, each with an owner and a fix date.
- Technical gaps (licences, apps, storage) and who fixes them.
- Label, DLP and auditing changes recommended.
- The pilot group, use cases and success measures.
- A dated plan: fixes, pilot start, review point and wider rollout.
If you finish the assessment and still don't know what to do on Monday, it was a report, not an assessment.
11. How long it takes and who should do it
For a business of 20 to a few hundred people, the assessment itself usually takes one to two weeks, and the fixes plus a pilot another two to four weeks. Larger tenants take longer mainly because of the number of sites to review.
You can run it yourself if someone has Global or SharePoint admin rights, time to work through the reports, and the authority to change sharing on other teams' sites. Bring in a consultant when nobody owns permissions, when sensitive content is involved, or when leadership wants a decision quickly.
Frequently asked questions
What is a Copilot readiness assessment?
A short review of your Microsoft 365 tenant, data and people before rolling out Microsoft 365 Copilot. It checks licences and apps, finds overshared content Copilot could surface, reviews sensitivity labels and content quality, and ends with a ready, ready-with-conditions or not-yet decision and a pilot plan.
How long does a Copilot readiness assessment take?
Usually one to two weeks for the assessment in a small or mid-sized business, then two to four weeks for the fixes and a pilot. Large tenants take longer because there are more sites to review.
Does Copilot bypass SharePoint permissions?
No. Copilot only shows content the signed-in person can already open. The risk is that many people can open far more than they should, and Copilot makes that oversharing easy to find.
Do we need E5 for Copilot?
No. Microsoft 365 Copilot is an add-on for business and enterprise plans such as Business Standard, Business Premium, E3 and E5. E5 adds stronger Purview and security features, which help, but they are not required to start.
Can I keep some SharePoint sites out of Copilot?
Yes. Restricted Content Discovery in SharePoint Advanced Management keeps a site's content out of Copilot and organisation-wide search while people with access can still use the site. Fixing the permissions underneath is still the long-term answer.
Can we run the assessment ourselves?
Yes, if someone has admin rights, time to work through the SharePoint and Purview reports, and the authority to change sharing across teams. Many companies run the checklist themselves and bring in help for the clean-up of sensitive sites.
Want this done for you?
I build this for clients every week. Book a free 30-minute call and I'll tell you exactly what your team needs.