FinOps Toolkit + Fabric vs. CSP Continuity for CSP Cost Reporting

Both paths solve the same CSP problem — no consolidated cost view — by collecting per-subscription data into your own tenant. Microsoft's FinOps toolkit is free, flexible, and yours to operate: per-subscription exports, hub infrastructure, optionally Data Explorer or Fabric. CSP Continuity is a managed application: about 30 minutes to working reports, a subscription fee, and no pipeline to maintain. Which one fits depends on your team, scale, and appetite for operating data infrastructure.

What does each path actually involve?

The FinOps toolkit path

Microsoft's FinOps hubs ingest Cost Management exports into storage, with optional Data Explorer or Fabric for querying at scale, plus prebuilt Power BI reports. Under CSP, the documented setup is per-subscription: "CSP customers need to configure exports for each subscription in order to ingest their total cost into FinOps hubs. Cost Management doesn't support management group exports for MCA or CSP subscriptions." You configure and monitor an export per subscription (including new ones as they appear), deploy and operate the hub, and track the toolkit's monthly releases. Two documented limits worth knowing under CSP: savings summaries are EA/MCA-only, and Microsoft's own Power BI guidance steers exports-based reporting to roughly the $2–5M/month range depending on Power BI license, with Data Explorer recommended above ~$2M/month.

The CSP Continuity path

A managed application from the Azure Marketplace: deploy (~5 minutes), run one read-only permissions script (~2 minutes), and collection starts automatically — every subscription, daily, up to 13 months of history, discovered without per-subscription export administration. It adds two things the toolkit path doesn't include for CSP: rebuilt reservation amortization (matching reservations to resources by SKU flexibility group, region, and scope, with unused capacity as synthetic records) and a query API compatible with Microsoft's Cost Management Query API for existing scripts. Data lands in a SQL database and Parquet files in your tenant; nothing leaves it.

How do the costs compare?

The toolkit is free software; its costs are infrastructure (storage, plus Data Explorer or Fabric if you need them) and engineering time — setup, per-subscription export administration, and monthly update tracking. CSP Continuity runs on ~$28–35/month of Azure infrastructure (B1 App Service, S0 SQL Database, storage) plus a subscription fee tiered by subscription count: $225/month (1–5 subscriptions), $495/month (6–15), or $1,495/month (16+), after a 30-day free trial. The honest framing: below Fabric-scale, the comparison is mostly subscription fee versus engineering hours; at Fabric scale, the toolkit's infrastructure costs rise but so does its headroom.

When is each the right choice?

Choose the FinOps toolkit path when:

  • You already have Fabric or Data Explorer capacity and the team that runs it.
  • You have dedicated FinOps engineering and want full pipeline ownership and customization.
  • Monitored spend is above roughly $2M/month, where Microsoft explicitly recommends hubs with Data Explorer.
  • You need custom ingestion or transformations beyond consolidated reporting.

Choose CSP Continuity when:

  • You need consolidated CSP reporting working in about 30 minutes, not weeks.
  • Nobody owns (or wants to own) an export-and-ingestion pipeline.
  • You want existing Power BI reports and API scripts to keep working via compatible column names and endpoints.
  • Reservation amortization visibility matters — the toolkit path doesn't rebuild it for CSP scopes.

Both are legitimate answers to the same architectural gap. If you read this page and the toolkit fits your team better, use it — the per-subscription export caveat is the main thing to plan around.

Frequently asked questions

Can I use the FinOps toolkit and CSP Continuity together?
Yes. CSP Continuity exports Parquet files to blob storage partitioned by year/month/subscription, which can feed Fabric or other pipelines alongside its own SQL database and API. Some teams use the managed collection as the data source and keep their FinOps toolkit reporting layer.
Does the FinOps toolkit support CSP at all?
Yes — with a documented caveat. Microsoft's FinOps hubs documentation states that "CSP customers need to configure exports for each subscription in order to ingest their total cost into FinOps hubs," because management group exports aren't supported for MCA or CSP subscriptions. Savings summaries are also documented as EA/MCA-only.
What does the Fabric / Data Explorer path cost per month?
It depends on capacity sizing, data volume, and retention, so we won't quote a number. The cost drivers are: Fabric capacity or a Data Explorer cluster (the dominant line item), storage for exports, and the engineering time to set up and maintain ingestion. Microsoft's guidance positions this path for organizations above roughly $2M/month in monitored spend, where that overhead is proportionate.
When is the DIY path clearly the right call?
If you already run Fabric or Data Explorer capacity, have a FinOps or data engineering team that wants pipeline ownership, need custom transformations Microsoft's or our schemas don't cover, or operate at a scale where Microsoft explicitly recommends hubs (above ~$2M/month monitored spend). In those cases the toolkit's flexibility earns its setup cost.

The maintained alternative

CSP Continuity deploys from the Azure Marketplace in about 5 minutes, needs one 2-minute PowerShell script, and starts collecting consolidated cost data within hours — entirely inside your tenant.

Related guides

Last updated: July 15, 2026. CSP Continuity is designed to work across a wide range of Azure environments. Results may vary based on tenant configuration, Microsoft API availability, and CSP partner setup. See our Terms of Use for details. Microsoft, Azure, and Power BI are trademarks of Microsoft Corporation. This page describes documented behavior of Microsoft services and links to official Microsoft documentation.