In our experience the Fabric projects that go wrong rarely fail on the technology. They go wrong on decisions taken, or skipped, before anyone opened a workspace: why the platform is being built, whose data it depends on, what it will cost to run in year two, who can see what, and who looks after it when the project team has gone. By the time those gaps show up, the money has usually been spent.
This checklist gives a business leader the questions to ask before signing anything, whether of their own team or of a partner they are considering. None of them need a technical background. Each one deserves a clear, written answer, and the checklist says what to do when the answer comes back vague.
Ask for the year two running cost, not just the build price.
The decisions that come before the engineering
Engineers argue about notebooks, Spark and Direct Lake, and those arguments matter. But they sit downstream of a smaller set of decisions that only the business can take: what the platform is for, which systems it depends on and who owns them, and what the key numbers mean. If those are not settled first, the engineering work has nothing solid to build on. The first five questions deal with them.
The invoice in year two
Fabric is billed on capacity, and capacity is consumed by everything that runs on it. The build cost is the number everyone negotiates. The running cost is the number that turns up a year later, after a dozen reports, three pipelines and a Copilot trial have been added and nobody was watching. Two of the questions are about who is watching, and what they do when the line goes up.
What you inherit when the project team leaves
The Fabric estates that cause the most trouble are rarely the ones that go down. More often they are held together by notebooks only one person understands, with no version control, no tests and nobody watching the 6am refresh, and that becomes yours the day the project closes. The last questions cover how the thing is built, who finds out first when it breaks, and what support costs once go-live is behind you.
What the checklist covers
- The 12 questions, grouped into why, data, cost, security and living with it
- A line on why each question matters, in business terms rather than platform terms
- A short note under each on what to do with a vague answer
- How to put the questions to a partner, and what to look for in the replies
- A practical next step if you would rather have the answers worked out for you
Who this is for
Finance directors, IT directors and operations leaders at mid-market businesses who are being told they need Microsoft Fabric, or who have a Fabric project underway and want to check it is being built on the right foundations before it is too late to change course.