Your EA Is Moving to MCA-E: Cost Reporting Checklist Before Renewal

Microsoft's documented renewal path for expiring direct Enterprise Agreement enrollments is to sign a Microsoft Customer Agreement (MCA-E, in Microsoft's enterprise-motion terminology). For cost reporting, that renewal changes three things at once: the export schema and connector scope, where your historical data lives, and the scale limits of the reporting stack. All three are predictable, and the highest-stakes item — history — has a deadline attached to your cutover date.

What changes for cost reporting under MCA-E?

The schema and connection. MCA data arrives with different column names and casing than EA (full mapping reference), and the Power BI connector reconnects with a 14-character billing profile ID instead of your enrollment number. DAX measures and Power Query steps bound to EA names can break (causes and fixes).

The history. Cost data before the transition stays in the EA billing scope — it doesn't move. Access afterward requires retained enrollment admin roles, and EA export jobs stop and must be recreated under MCA (bridging both timelines).

The scale story. Microsoft's FinOps guidance marks the connector "not recommended" above $1M in monitored spend, with no plans to update it, steering larger estates toward exports and FinOps hubs (the numbers, precisely attributed). Renewal is a natural moment to decide whether you rebuild on the connector at all.

The pre-renewal checklist

1. Inventory your report dependencies

List every Power BI report, dataset, DAX measure, Power Query step, and downstream consumer touching cost data — and note which column names each references. Reports built on legacy EA names (PreTaxCost, UsageDateTime, SubscriptionGuid) have the most exposure. This inventory sizes the whole project.

2. Export your EA history — before cutover

Microsoft's own recommendation: "We recommend that you download your cost and usage data and invoices before you transfer subscriptions." Portal experiences cover 13 months; the Exports REST API reaches further back. Confirm who holds Enterprise Administrator or Department Administrator on the enrollment, because subscription ownership won't grant historical access afterward.

3. Decide your post-migration reporting path

Three real options: rebuild reports on the MCA schema (or FOCUS exports) yourself; adopt the FinOps hubs + Fabric stack, which fits large estates with engineering capacity (honest comparison); or keep existing reports intact by pointing them at a source carrying EA and MCA column names simultaneously, which is MCA Continuity's approach.

4. Recreate exports and integrations under the MCA scope

Export jobs don't migrate — plan to recreate them under the new billing profile, along with anything authenticated against the enrollment number.

5. Deploy your continuity layer before the cutover date

Whatever path you chose, have it running before renewal. If that's MCA Continuity: deployment is about 5 minutes from the Azure Marketplace plus a 2-minute read-only permissions script; it collects up to 13 months of EA-era history into your tenant and keeps collecting through the transition, so dashboards read one continuous timeline across the boundary and the column mapping stays Microsoft's problem rather than yours.

If your renewal is moving you to a CSP partner rather than to MCA-E, the CSP-specific changes are bigger — see the EA-to-CSP checklist at cspcontinuity.com.

Frequently asked questions

Is Microsoft actually retiring the Enterprise Agreement?
We'll stick to what Microsoft documents: the renewal path for expiring direct EA enrollments is to sign a Microsoft Customer Agreement, expiring indirect EAs currently can't renew into MCA, and eligibility is worked through your Microsoft account manager. Microsoft's FinOps docs treat the EA-to-MCA transition as an expected event for EA organizations. For your specific enrollment's timeline, your account manager is the authoritative source.
What is MCA-E exactly?
Microsoft's term for the "Microsoft Customer Agreement in the enterprise motion" — the MCA as offered to enterprise customers who historically bought through an EA. For cost reporting purposes it behaves as an MCA: billing profile scopes, the MCA export schema, and MCA connector setup.
How long before renewal should we start?
Enough to inventory report dependencies, export EA history, and stand up whichever reporting path you choose — for most teams, weeks rather than days, mostly calendar time for testing dashboards against the new source. The history capture is the step with a hard deadline attached to your cutover date.
Should we just adopt FOCUS exports instead?
It's a reasonable strategy Microsoft explicitly suggests: "For organizations still on EA, switching to FOCUS now puts you in control of timing so you're not 'offline' after your account is transitioned to MCA." FOCUS 1.0/1.0r2 exports are generally available and schema-stable across agreement types. The trade-off: your existing reports were built on EA columns, so adopting FOCUS is itself a report rework — comparable to rebuilding on MCA columns.

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 How deployment works

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.