A Fabric readiness score between 0 and 100 sits in front of every organization we work with. And almost every time, the first reaction is the same: "What does this number actually mean?"
That's because "readiness score" is vague. It could mean a hundred things. Is it a grade? A prediction? A probability that Fabric will work in your environment? Nobody knows without asking.
So let me be direct: a Fabric readiness score is a diagnostic tool, not a grade. It is not pass or fail. It tells you where your tenant stands across five specific dimensions of maturity — and each one has an action plan attached to it.
The five dimensions of Fabric readiness
Governance Maturity. This measures the structure of access control, role assignments, workspace organization, and policy enforcement in your tenant. Do you have documented governance guidelines? Are sensitivity labels applied consistently? Do you know who has admin rights and why? A low score here means your data access is either too permissive or too complex to manage — both are problems at scale.
Data Model Health. This is about the technical foundation of your datasets — semantic models, dataflows, refresh schedules, connection health, and lineage documentation. If your datasets are fragmented, poorly documented, or dependent on brittle connections, that's a readiness drain. Fabric requires solid data architecture. If you do not have it, Fabric will amplify the problem.
Copilot Readiness. Microsoft Copilot for Fabric has specific prerequisites. Your data must be classified. Your semantic models must have good descriptions and relationships. Your governance must be tight enough that the AI is not making recommendations based on stale or orphaned assets. If your tenant is not ready for Copilot, you are leaving a major productivity feature on the table.
Security Posture. This covers sensitivity labels, access permissions, guest account management, external sharing settings, and compliance controls. A weak security posture means data is either exposed or locked down so tightly that nobody can use it. Neither is acceptable. Fabric intensifies the need for security clarity.
Migration Complexity. This is a forward-looking metric. If you are moving from Power BI to Fabric, or consolidating multiple Power BI tenants, how much rework will it take? Are your current workspaces too chaotic to migrate? Do you have undocumented dependencies that will break in a new environment? Migration complexity tells you the effort required to move forward.
What a low score actually means
Let's say your readiness score is 35 out of 100. That does not mean you cannot use Fabric. It means your tenant has significant gaps across these five areas — and you need to address them before a Fabric migration (or Copilot deployment) will succeed.
A low score usually breaks down like this:
- Governance maturity is poor: workspaces are scattered, access rules are not documented, admin delegation is unclear
- Data models are fragmented: datasets overlap, lineage is undocumented, some connections are stale
- Copilot readiness is low: semantic models lack descriptions, relationships are incomplete, data classification is sparse
- Security controls are inconsistent: sensitivity labels are applied to less than 50% of content, some guest accounts have broader rights than intended
- Migration complexity is high: a Fabric move will require significant cleanup and re-architecture before success
This is not a death sentence. This is valuable information. You now know exactly what needs fixing, and in what order.
What a high score tells you
A readiness score above 75 means your tenant is in good standing across all five dimensions. Governance is documented and enforced. Data models are clean and well-described. You have the foundation for Copilot. Security controls are tight and consistent. Migration to Fabric would be straightforward.
Does a high score mean you have zero work to do? No. It means the work is incremental, not transformational. You are ready to move forward.
Scores between 50 and 75 are the most interesting
This is where most organizations actually live. You have some governance in place, but not everywhere. Your datasets are mostly healthy, but a few are problematic. You have started on security controls, but the coverage is not complete. Migration complexity is moderate — you can move forward, but you will need to make some decisions and fixes along the way.
A score in this range tells you that you need a prioritized roadmap. Not a complete overhaul. A focused 90-day push to hit the highest-impact issues first.
The score is only the first question
Knowing you have a readiness score of 60 is useful. Knowing exactly which categories are holding you back — and what specific actions fix them — is invaluable.
That is where the real assessment work lives. The score is the headline. The report is the playbook.
We have found that most organizations can move the needle 15-20 points on their readiness score in 30 days of focused work. Not because the fixes are complicated. Because the problems were never visible until someone looked.
How to get your readiness score
The Tenant Scan process runs a deep analysis of your Power BI and Fabric environment. We look at every workspace, dataset, gateway, external connection, user permission, sensitivity label, and dataflow. We then score your readiness across the five dimensions above and deliver a prioritized report with specific remediation steps for each gap.
The Tenant Scan Starter gives you the readiness score and a 30-60-90-day action plan. The Tenant Scan Pro adds a full data architecture review and governance roadmap.
Both end with a readout session where we walk you through every finding and answer every question your team has.