Microsoft Fabric Readiness Assessment

It’s a fixed-scope review that answers whether Fabric suits your data estate, what a move would involve, and what Fabric would cost to run each month. Ours combines three working sessions with read-only analysis of your admin portals and capacity data. The output is a written recommendation you can take to leadership: move now, move in phases, or wait.

Readiness comes down to five things: what you run today, what Fabric would cost to run it, how it would be laid out, who owns it and can access it, and what could get in the way, including skills gaps and objects that won’t convert cleanly. The scorecard rates each of the five from 1 to 5, with the reason behind every score. The roadmap then sets the first workload and the rollout order.

Two weeks from the first working session to the final report. Your team spends about 5.5 hours in sessions: two 2-hour working sessions and a 90-minute findings walkthrough, plus the discovery call beforehand, which takes 45 to 60 minutes. Between sessions, our consultants work from read-only access, so your team isn’t pulled away for data gathering.

A written readiness report with the recommendation, a scorecard rating six areas from 1 to 5, an inventory of your sources, pipelines, and reports, a draft target architecture, a capacity model with a starting F-SKU and monthly cost range, a risk and gap list with mitigations, and an adoption roadmap. Everything is presented in a stakeholder walkthrough and is yours to keep.

It starts with a free discovery call of 45 to 60 minutes to confirm scope and stakeholders. The assessment itself is a fixed fee, quoted after the call based on the number of data sources, workloads, and stakeholders involved. The fee is agreed before work begins and doesn’t change based on what the report recommends, including a recommendation to wait.

Only read-only access, and not to the data itself. We ask for a user who can view the Fabric admin portal, the Capacity Metrics app, and pipeline metadata for Synapse or Data Factory if you use them. Where that isn’t possible, we work from exports and screen-shared sessions, and your team can revoke access as soon as the report is delivered.

Capacity depends on your workloads, which is why the assessment measures them. F64 matters for Power BI: below F64, everyone viewing reports needs a Pro or Premium Per User licence, while from F64 up, users with a free licence and the Viewer role can view content in that capacity. The report compares the cost of F64 against Pro licences for your viewer count.

Yes. If your sources, skills, or licensing make Fabric a poor fit right now, the report says so and explains why. Common reasons include data that mostly lives outside Microsoft services, a viewer count that Pro licences already cover at lower cost, or governance gaps to close first. The report also sets out what would need to change before you revisit the decision.

Each P-SKU subscription ends when its current agreement term does, and Microsoft no longer sells new P-SKUs, so P capacity moves to an F-SKU. In compute, P1 is roughly F64, though Microsoft notes this isn’t a licensing equivalence. Microsoft allows a 30-day grace period after the term ends, followed by throttling. The assessment checks whether a smaller or larger F-SKU fits your actual usage.

No. The report is written so your own team or another partner can act on it, with the architecture, capacity model, and roadmap documented in enough detail to scope the next phase. If you’d like us to continue, the roadmap carries straight into our Fabric consulting or migration work, and the findings mean that work starts without repeating discovery.