Eight dimensions. Three result bands. A composite score that tells you whether to pilot, remediate, or wait. Free and independent.
An eight dimension readiness model that scores whether your tenant, your data and your people are actually ready for a Microsoft 365 Copilot rollout in 2026.
Microsoft will sell you Copilot today. Whether you can use it tomorrow is a different question.
We built this assessment after running Copilot readiness reviews for more than 40 enterprises. The pattern is consistent. The companies that score high on the dimensions below get value inside the first quarter.
The companies that score low spend the first year doing the work they should have done before the contract. That is an expensive way to learn.
The model is derived from real engagements, not from product marketing. Each dimension carries a weight based on how often we saw it determine the rollout outcome.
We weight data readiness higher than identity readiness because data problems are more painful to fix after a Copilot tenant is live.
Green, amber, red. Each dimension produces a sub score. The composite sets the headline band.
The composite is not an average. A red on data readiness can hold the whole result back. Foundations matter more than peripherals.
Dimension weights and what we are looking for
| Dimension | Weight | Green looks like |
|---|---|---|
| Tenant hygiene | 10% | Recent audit, MFA universal, CA policies enforced. |
| Data classification | 20% | Active Purview labels, 70 percent plus coverage of confidential docs. |
| Permissions and oversharing | 20% | Site permissions reviewed in last 12 months, open shares contained. |
| Identity readiness | 10% | Entra ID modern auth, guest hygiene, service account segregation. |
| Use case maturity | 10% | Five plus mapped use cases by role with named owners. |
| Adoption and change | 10% | Champion network, training plan, feedback loop in place. |
| Value tracking | 10% | Named KPIs, baseline measured, monthly reporting cadence. |
| Commercial posture | 10% | EA renewal aligned, ramp modelled, exit clause negotiated. |
The fastest Copilot rollouts we have seen scored green on data readiness six months before they signed the contract.
Is your Microsoft 365 tenant in a state where Copilot can be turned on without a cleanup? Recent tenant audits, MFA coverage and conditional access posture all count here.
Have you classified the data Copilot will see? Has Purview rolled out the sensitivity label catalog? Are confidential documents actually labelled, or only the easy ones?
Are SharePoint sites locked to the right groups? Are open shares limited? Has the Restricted SharePoint Search baseline been considered? Oversharing is the single biggest cause of Copilot rollout drag.
Are users on Entra ID with modern auth? Are guest accounts cleaned up? Are service accounts segregated from human accounts? Identity is the floor under everything else.
Have you mapped concrete use cases to roles? Do you know which teams will use Copilot daily and which will use it weekly? A good rollout starts with a short list of high impact use cases, not with a tenant wide enable.
Do you have a champion network? Is there an internal training plan? Is there a feedback loop that surfaces what is working and what is not?
How will you measure the value Copilot creates? Time saved, output produced, error rates avoided. Without a number the renewal conversation gets uncomfortable.
Is your EA renewal aligned to Copilot adoption? Have you modelled the impact on your discount band? Are you buying the right number of seats for the right term?
Pilot inside 30 days. Negotiate a 12 month commit with a flexible scale ramp. Capture value metrics from week one.
Run a 90 day remediation sprint. Focus on the two lowest scoring dimensions. Then pilot in a contained scope of 200 to 500 seats while you finish the rest of the foundation.
Do not sign a large Copilot commitment yet. The math will not work and the rollout will stall. Build the foundation. Run the assessment again in 60 to 90 days.
Yes. We publish it because most Copilot rollouts fail on foundations, and we would rather you fix those before you sign than after. There is no obligation to engage us afterwards.
Around 8 minutes for one person. Around 20 minutes if you run it as a workshop across IT, security, and a business owner. The workshop version produces better results.
No assessment can guarantee that. A green score means you can pilot without rework. The financial payback depends on use cases, adoption, and the discount you negotiate.
Yes. Many of our clients do. A central IT score plus per business unit scores produces a clearer picture, especially in conglomerates with mixed maturity.
They sit side by side. This one measures readiness. The optimizer models the financial impact of the seat decision. We recommend running both before any commit over 500 seats.
From our engagement data. We weight data readiness highest because that is where we have seen the largest gap between marketing claims and reality across 40 plus rollouts.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
We saw the same pattern again and again. The companies that scored green on data readiness six months before the contract were the ones that captured value in the first quarter.
500+ enterprise clients. 11 vendor practices. Gartner recognized. One conversation can change what you pay for the next three years.
Independent Microsoft and AI licensing intelligence in your inbox. No spam.