Moving from EA to MCA: What Actually Changes (and What Doesn't)

What genuinely doesn't change

Start with what Microsoft's EA-to-MCA setup guide gets right, because it's real and it matters: "Azure services in your subscription keep running without any interruption. We only transition the billing relationship for your Azure subscriptions. There are no changes to existing resources, resource groups, or management groups." Access set with Azure RBAC "isn't affected during the transition." Nothing reboots, nothing redeploys, no maintenance window. If your only question is "will production notice?", the answer is no — and that's the honest basis for the "nothing changes" reassurance you heard.

The rest of this page is about the other audience: whoever owns the Azure bill, the Power BI cost reports, and the FinOps process. For them, the transition is a real project. One more documented fact that raises the stakes: "the transition can't be reverted."

What changes in the billing structure?

Your EA hierarchy — enrollment, departments, enrollment accounts — is replaced by the MCA hierarchy: billing account, billing profiles, invoice sections. Microsoft's mapping documentation draws the lines precisely:

• Your enrollment maps to a billing profile — "you use a billing profile to manage billing for your organization, similar to your Enterprise Agreement enrollment."
• Departments become invoice sections, keeping the same names.
• Enrollment accounts have no equivalent — they "aren't supported in the new billing account." Their subscriptions land on the department's invoice section, and account owners become subscription creators there.

One welcome difference: unlike an enrollment, the agreement "doesn't expire," and billing profile IDs never change — no more renewal-driven enrollment numbers rippling through your tooling.

Who can do what afterward? (roles)

Billing admin roles are re-granted, not copied. Per the setup guide: Enterprise administrators become owners at all three levels (billing account, billing profile, and every invoice section); department administrators become owners of their department's invoice section; account owners become Azure subscription creators. Two documented catches: the new billing account only supports users from the tenant selected when the MCA was signed (others must be invited as guests), and EA notification contacts aren't carried over — billing emails go to people with billing profile access instead.

What changes on the invoice?

Instead of one invoice per enrollment, you get a monthly invoice per billing profile, organized by invoice section, generated early in the month after usage. Microsoft's onboarding guide flags the transition-month mechanics: you may receive two invoices that month (final EA, first MCA), the MCA remit-to bank details differ from EA — "your accounts payable need to create two records" — and you should add an AP email address as an invoice recipient. Pricing also changes denomination: under MCA, "Azure is priced in US dollars (USD) worldwide," with conversion to your local billing currency at billing time, whereas EA prices were in local currency. If you bill in a non-USD currency, that exchange-rate step is new line-item math for finance.

What happens to reservations and savings plans?

The headline is good: existing reservations and savings plans "are moved to your new billing account" with "no change to benefits or term." The caveats are currency-shaped and documented: savings plans purchased in non-USD currency are canceled and repurchased in USD at a 1-year term regardless of the original, and monthly-paid reservations can be canceled when the billing currency changes (Microsoft exempts these from the usual cancellation threshold). Non-USD customers should read that section of the setup guide closely before agreeing to a date.

What changes in cost reporting?

This is the part most often discovered after the fact, and it's why this site exists:

• Your cost history stays behind. "Cost data before the transition remains in the EA scope. It doesn't move to the MCA scope" — and reading it afterward requires retained EA admin roles. Bridging both timelines →
• The export schema changes. Column names and casing differ between EA and MCA, and export jobs must be recreated under the new scope. The full mapping reference →
• Power BI needs re-pointing. The connector switches from your enrollment number to a 14-character billing profile ID, the returned tables differ, and the Cost Management template app doesn't support MCA at all. Causes and fixes →
• Budgets, saved views, and spending quotas are rebuilt, not moved. Department spending quotas become budgets; custom Cost Management views need recreating.

MCA Continuity exists for exactly this seam: deployed before the cutover, it collects your EA-era cost history into a SQL database in your own tenant and keeps collecting after, exposing one continuous timeline through a view that carries EA, MCA, and PAYG column names simultaneously — so the reporting changes above become Microsoft's implementation detail rather than your rebuild project.

What should you do before the cutover?

Work the pre-renewal checklist: inventory report dependencies, export EA history while your admin roles still grant access, brief accounts payable, review reservation currency exposure, and stand up your reporting bridge before the date — because the one thing every doc agrees on is that this transition only runs in one direction.