Fabric vs Azure Databricks: monthly TCO inputs

Planning tool, not a vendor quote. No live pricing is fetched. Rates start blank. Enter dated official or contracted rates for one currency and region. Hypothetical scenarios describe workloads; they do not predict runtime or platform sizing.

Planning scenario

RegionCurrency codeVendor rate verification dateSource/quote reference

Fabric

Enter one whole-capacity hourly rate, not a per-CU rate. For reservations, use amortised monthly commitment plus uncovered PAYG separately. Storage/operations and eligible separate Spark charges are additional only when applicable.

Capacity billing method Billable active capacity hours/monthWhole-capacity hourly rateAmortised reservation/monthUncovered PAYG/month Separate Spark billed CU-hoursSeparate Spark rate/CU-hourApplicable overage/monthBillable storage GB-monthEffective storage rate/GB-monthStorage transactions/retrieval/BCDRBI licences/monthNetworking and other servicesSupport and operations/monthIntegration/maintenance/monthEnter rates to calculate

Azure Databricks

Enter total billed DBUs for each workload, not DBU/hour. For included serverless infrastructure, use zero external VM node-hours. For classic, enter actual billable driver and worker node-hours and a blended rate, or split externally for unequal node prices.

Workload	Total DBUs	Rate/DBU
Jobs / batch
SQL
Pipelines / streaming
ML / other

Non-included VM node-hoursEffective rate/node-hourDisks / non-included infrastructureBillable storage GB-monthStorage rate/GB-monthStorage operations and transferBI / applicable service licencesNetwork / optional servicesSupport and operations/monthIntegration/maintenance/monthEnter measured usage and rates

Hybrid and project cost

Shared costs counted in both platformsAdditional hybrid operations/monthOne-time migration/training costChosen amortisation period/monthsComplete both platform models first

Model controls and assumptions

GB/TB are decimal planning units here: 1 TB = 1,000 GB. Convert if the vendor uses a different billing definition.
Billable capacity hours are service availability hours, not job runtime. Two simultaneous jobs do not double active capacity hours.
Utilisation scenarios are workload sensitivity inputs; multiplying a purchased-capacity bill by utilisation would incorrectly discount idle capacity.
Reservations are commitments. Pausing capacity does not remove an amortised commitment.
CU consumption already covered by base capacity is not a second charge. Add separate Spark or overage only as billed.
DBU quantities and runtime must be measured per platform; this tool does not translate CUs into DBUs.
Zero optional costs must be justified. Do not interpret defaults as proof that networking, BI or support is free.
Shared-cost subtraction needs a line-item reconciliation. The hybrid total is an accounting exercise, not a recommendation.
No tax, FX, inflation or discount assumptions are inserted. No claim of comparative savings is made.