Moving from EA (or MCA) to CSP: What Breaks in Cost Reporting — A Pre-Migration Checklist

Why plan cost reporting before the transfer?

A CSP transfer moves your billing relationship into your partner's tenant. Resources keep running — Microsoft documents "no service downtime" — but the billing scope your reporting was built on stays behind. Two of the five changes below are time-sensitive: once the transfer completes, portal history is no longer yours to export, and pre-transfer collection at your negotiated rates is no longer possible. The rest can be fixed after the fact, but fixing them before means your dashboards don't go dark on migration day.

The five changes, and what to do about each

1. The consolidated cost view moves to subscription scope

Cost Management doesn't support management group scope for CSP subscriptions — attempting it shows "Management group does not have any valid subscriptions." Tenant-wide cost analysis in the portal ends with the transfer.
Before the transfer: decide how you'll consolidate — partner reporting, per-subscription exports, FinOps hubs, or a managed collector — and stand it up.
Full guide: the management group error →

2. The Power BI Cost Management connector stops returning data

The connector supports EA and direct MCA only; Microsoft Partner Agreements aren't supported. Reports built on it need a new data source, not new credentials.
Before the transfer: inventory reports using the connector and pick their replacement path (exports + rebuild, FinOps hubs, or a compatible SQL source).
Full guide: the connector under CSP →

3. Cost APIs drop to single-subscription scope

Billing account, department, and management group API scopes are gone under CSP; every call targets one subscription. Automation built on broader scopes fails with authorization errors.
Before the transfer: inventory scripts and integrations calling Cost Management APIs; plan the per-subscription loop or point them at a consolidated compatible endpoint.
Full guide: API scopes under CSP →

4. Portal cost history resets — this one is time-critical

"Usage and billing history doesn't transfer with the product." Trend data, baselines, and budgets from the old agreement stay at the old billing scope.
Before the transfer: export 12–13 months of history to storage you own, and/or deploy a collector that captures it into your tenant. After the transfer, the option is gone.
Full guide: preserving cost history →

5. Reservation amortization shows $0 — also affects budgeting

At CSP-accessible scopes, reservation usage appears with zero charges in actual and amortized views. Chargeback and utilization reporting need amortization rebuilt from the Reservations API.
Before the transfer: if you charge back reservation costs, decide who rebuilds amortization and how — it's the most engineering-heavy of the five to DIY.
Full guide: amortization under CSP →

Why deploy before, not after?

CSP Continuity's product FAQ is explicit about ordering: deploy while still on EA or MCA. The application then collects up to 13 months of history at your current negotiated rates; that data stays in your tenant when portal history resets, and collection continues at the new rates after the transfer — one continuous timeline across the transition, which is not reconstructable afterward. Deployment is about 5 minutes from the Azure Marketplace plus a 2-minute read-only permissions script, so it fits at the end of this checklist even on a tight timeline.

Readers whose renewal is moving EA to MCA (not CSP): the equivalent checklist lives at mcacontinuity.com.