EA Cost History Missing After MCA Migration — Bridging Both Timelines

Where did the history go?

Nowhere — and that's the problem. Cost data is scoped to a billing account, and an EA-to-MCA migration creates a new one. Microsoft's setup guide describes both sides of the split: "Cost data stays under your EA enrollment billing scope" while the "MCA scope shows cost data starting from the migration date." You can still reach the old data by switching scopes in the portal — but with a documented access catch. Per the onboarding guide, historical charges are visible "if you're the Department Administrator or Enterprise Administrator for the enrollment. Subscription ownership doesn't provide access to historical data."

So the history exists, behind roles your team may or may not have retained, in a scope your MCA reporting doesn't read, in a schema that differs from your new MCA data. Microsoft's own recommendation in that guide: "We recommend that you download your cost and usage data and invoices before you transfer subscriptions."

How do you bridge the two timelines?

1. Export the EA history while you can (free, do this regardless)

Using retained EA admin access, export historical cost data — the portal covers the last 13 months, and the Exports REST API reaches data retained for at least seven years. Land it in a storage account you own. Two things to plan for: the files use the EA schema, which won't line up column-for-column with your MCA exports, and EA export jobs don't survive the migration — Microsoft documents that they must be recreated under the MCA scope, so standing pipelines stop at cutover even if the data remains readable.

2. Keep two models and stitch visually (free, permanently awkward)

Load EA history and MCA data as separate tables or reports and align them side by side. Every measure exists twice, the schemas disagree on names and casing, and cross-boundary calculations (year-over-year through the migration date) need manual bridging logic in DAX. Workable for one retrospective; frustrating as the permanent state.

3. Collect both sides into one schema

MCA Continuity is built for exactly this seam: deployed before (or soon after) cutover, it collects up to 13 months of history per subscription into a SQL database in your tenant and keeps collecting as the agreement changes — producing one continuous timeline where EA-era and MCA-era records share consistent columns. The CostManagement_Usage view exposes EA, MCA, and PAYG naming simultaneously, so existing reports read the bridged history without a renaming layer, and year-over-year visuals cross the migration date without stitching.

Timing matters: deploying before the cutover captures the EA window at its fullest. If you're planning the migration now, the broader pre-renewal checklist covers this alongside the schema and scale changes.