Unify Your Data on One Platform

Not always, and we will tell you honestly if you don’t. Fabric makes sense when reporting outgrows standalone Power BI:

• Many sources to combine
• Large or slow datasets
• Manual data preparation you want automated

If your current setup serves you well, we won’t push a migration.

Fabric is billed through capacity SKUs (F2 and up), so cost depends on workload size and usage. Part of our engagement is right-sizing: starting on the smallest capacity that fits and scaling deliberately, rather than paying for headroom you don’t use. Most of the businesses we work with start between F2 and F8. Indicative monthly figures in Rand, rounded:

*The two storage columns are our guideline pairings, not Microsoft’s: OneLake storage is not tied to the SKU, holds whatever you put in it, and is billed pay-as-you-go only, at R0,395 per GB per month on the standard tier. There is no reserved pricing for storage. As the table shows, storage is small change next to the capacity itself.

Also not in the capacity price:

• Power BI Pro licences for the people building reports, billed through Microsoft 365
• Viewer licences on capacities below F64; from F64 up, report viewers need no paid licence, which is often what justifies the step up
• Reserved capacity needs a one-year commitment to Microsoft; pay-as-you-go can be paused or stopped at any time

Source: Microsoft. Pay-as-you-go figures are Azure portal estimates in Rand; reserved and storage figures are worked out from Microsoft’s published rates. All captured August 2026 and rounded to the nearest R100. Pricing is Microsoft’s, not ours, and changes with your agreement, region and the exchange rate. Confirm current figures on Microsoft’s Fabric pricing page before budgeting; we size and confirm the real number with you as part of scoping.

Yes, and you should.

• Most clients start with one workload, typically the data behind an important report, moved into a lakehouse with an automated pipeline
• The platform then grows one proven use case at a time
• Existing reports keep working throughout

Weeks, not months, for a focused first workload.

• From workshop to a working lakehouse feeding a production Power BI report
• Full rollouts depend on the number of sources, and we put honest numbers to that before anything is committed

No. Power BI is part of Fabric, not replaced by it: Microsoft folded Power BI in as Fabric’s reporting layer.

• Your reports, licences and skills carry over
• What Fabric adds sits behind the reports: pipelines, a lakehouse, warehousing
• The real question is whether you need that engine, not whether Power BI is going away

They keep working. Adopting Fabric does not break or retire a single existing Power BI report.

• The usual first move is repointing the data behind one important report at a lakehouse, so it refreshes automatically instead of manually
• Reports themselves change only when you choose to improve them