FinOps Toolkit + Fabric vs. MCA Continuity After EA to MCA

Both paths keep Azure cost reporting alive after an EA-to-MCA migration. Microsoft's FinOps toolkit with Fabric or Data Explorer is the free, build-it-yourself stack Microsoft recommends at scale. MCA Continuity is a managed application that preserves your existing reports instead of replacing them. The honest split: the toolkit wins when you have engineering capacity and want a new analytics platform; the managed app wins when you want the dashboards you already have working in about 30 minutes.

What does each path involve?

Microsoft's answer: exports, FinOps hubs, Fabric

The documented stack: configure Cost Management exports (FOCUS format) to a storage account, deploy FinOps hubs for ingestion, add Data Explorer or Fabric capacity for query performance at scale, and use the toolkit's prebuilt Power BI reports. Microsoft's guidance is candid about when this is warranted: exports alone support "$2-5 million in monthly spend depending on your Power BI license," and "if you use more than $2 million in monthly spend, we generally recommend using FinOps hubs with Data Explorer for the best performance." The same page notes the old connector is kept only "for backwards compatibility" with "no plans to update" it.

What you take on: provisioning and paying for the capacity layer, building refresh pipelines, tracking the toolkit's monthly updates, and rebuilding existing reports against FOCUS/toolkit models — your EA-era DAX doesn't come along for free.

MCA Continuity's answer: keep the reports, swap the source

A managed application from the Azure Marketplace: deploy (~5 minutes), run one read-only permissions script (~2 minutes), connect Power BI to the CostManagement_Usage SQL view via DirectQuery (~5 minutes). The view exposes EA, MCA, and PAYG column names simultaneously, so existing DAX measures and visuals are designed to keep working unmodified; DirectQuery means no dataset import, no refresh window, and no spend ceiling, on a standard S0 SQL database (~$15/month). It also bridges EA-era and MCA-era data into one timeline when deployed around the migration.

How do the costs compare?

The toolkit is free software plus infrastructure (storage; Data Explorer or Fabric capacity if you need scale) plus engineering time. MCA Continuity runs on ~$28–35/month of Azure infrastructure plus a subscription fee tiered by subscription count — $149/month (1–5 subscriptions), $349/month (6–15), $995/month (16+) — with a 30-day free trial. Below Fabric scale, the comparison is essentially subscription fee versus engineering hours; at Fabric scale, the toolkit's infrastructure cost rises but brings platform headroom a managed reporting app doesn't aim to provide.

When is Fabric the right call?

  • You already run Fabric or Data Explorer capacity, with a team that owns it.
  • Monitored spend is above roughly $2M/month — Microsoft's own threshold for recommending hubs with Data Explorer.
  • You have data engineering capacity and want custom pipelines, transformations, and platform ownership.
  • You're consolidating multi-cloud or multi-account data under FOCUS as a strategic standard.

When is MCA Continuity the right call?

  • Your existing Power BI reports are good — the problem is the source, not the reports.
  • Nobody wants to own an export-ingestion-capacity pipeline for cost data.
  • You need the EA-to-MCA seam bridged: one timeline, both naming conventions, no rebuild.
  • Refresh timeouts are the pain and DirectQuery's no-import model removes them structurally.

Both are legitimate. If you read this and the toolkit fits your team, use it — and if you later want the managed collection underneath a Fabric layer, the Parquet export means you don't have to choose forever.

Frequently asked questions

Can MCA Continuity feed Fabric anyway?
Yes. Per the product FAQ, the application optionally exports Parquet files to blob storage, which Fabric or import-mode Power BI can consume. Teams sometimes use the managed collection as the data source and keep a Fabric analytics layer on top — the two aren't mutually exclusive.
What are the ongoing maintenance differences?
The toolkit path is yours to operate: export configuration, hub infrastructure, Data Explorer or Fabric capacity, and the toolkit's monthly release cadence with its own upgrade notes. MCA Continuity is a managed application — collection, schema, and API are maintained by the publisher, and your operational surface is the ~$28–35/month of standard Azure resources it runs on (Function App, storage, S0 SQL Database).
What does the Fabric path cost per month?
It depends on capacity sizing, data volume, and retention, so we won't quote a figure. The cost drivers: Fabric capacity or a Data Explorer cluster (the dominant item), export storage, and the engineering time for setup and upkeep. Microsoft's guidance positions this stack for estates above roughly $2M/month in monitored spend, where the overhead is proportionate.
Does either path fix the EA-to-MCA column problem?
Both do, differently. The toolkit standardizes on FOCUS — which means rebuilding reports on FOCUS columns. MCA Continuity's CostManagement_Usage view exposes EA, MCA, and PAYG names simultaneously, which means not rebuilding reports at all. Rebuild-to-a-standard versus keep-what-works is the real choice.

The maintained alternative

MCA Continuity deploys from the Azure Marketplace in about 5 minutes, needs one 2-minute PowerShell script, and connects to Power BI in about 5 more — no Fabric capacity, no pipelines, entirely inside your tenant.

Deploy the free 30-day trial See pricing

Related guides

Last updated: July 15, 2026. MCA Continuity is designed to work across a wide range of Azure environments. Results may vary based on tenant configuration and Microsoft API availability. 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.