Azure Cost History Disappeared After Moving to CSP — What Happened and How to Preserve It

Billing transfers reset cost history in the Azure portal. When subscriptions move to a CSP agreement, trend data, baselines, and budgets from the previous agreement don't carry over — Microsoft's transfer documentation states that "usage and billing history doesn't transfer with the product." The data still exists at the old billing scope, but you lose access to it. The only reliable way to keep a continuous timeline is to export or collect the history into your own tenant before the transfer completes.

What actually happens to cost data in a billing transfer?

Cost Management data is scoped to a billing account. A transfer to CSP doesn't move your subscriptions' cost records to the new agreement — it starts a new record under the partner's billing account, and the old record stays behind. Microsoft says this consistently across four separate docs:

  • "Usage and billing history doesn't transfer with the product." — Azure product transfer hub
  • "Download or export cost and billing information that you want to keep before you start a transfer request. Billing and utilization information doesn't transfer with the subscription." — CSP transfer guide
  • "When you transfer subscriptions, cost and usage data for your Azure products aren't accessible after the transfer." — MPA billing ownership guide
  • "Historical costs before the transfer to the new partner don't move to the new billing account. However, the cost history does remain with the original associated billing account." — Cost Management for partners

Your resources, subscription IDs, RBAC assignments, and running services are unaffected — Microsoft documents "no service downtime" for billing transfers. What breaks is continuity of reporting: the portal's cost views on your subscriptions start from the transfer date, and year-over-year comparisons, baselines, and trend lines end at it.

What can you do about it?

1. Before the transfer: bulk-export your history (free, act in time)

While the old agreement is still active, you can export cost and usage data — up to 13 months through the portal experience, and older data via the Exports REST API. Land it in a storage account you keep. This works and costs nothing beyond storage, with two caveats: it's a one-off snapshot that won't update after the move, and the export schema differs from what you'll collect under CSP, so building a single continuous timeline means reconciling two schemas yourself.

2. After the transfer: ask your partner about invoice history (free, coarse)

If the transfer already happened and nobody exported, your CSP partner may retrieve some historical billing information — but typically at invoice level, not daily resource-level detail. It answers "what did we spend," not "which resource, which meter, which day."

3. Deploy a collector before the migration

CSP Continuity's product FAQ makes a specific recommendation: deploy before the transfer. While you're still on EA or MCA, the application collects up to 13 months of history at your current negotiated rates into a SQL database in your own tenant. That data stays with you when portal history resets. After the migration, collection continues at the new rates — producing one continuous timeline across the transition, visible in Power BI, the query API, and the in-portal workbook. Deployment is about 5 minutes plus a 2-minute permissions script, so it fits comfortably in a pre-migration checklist.

Planning a CSP move?

History is one of five cost-reporting changes a CSP transition brings — the consolidated tenant view, the Power BI connector, API scopes, and reservation amortization change too. We've collected all five, with pre-transfer actions for each, in the EA/MCA-to-CSP cost reporting checklist.

Frequently asked questions

We already migrated — is the history recoverable?
Partially, at best. Microsoft documents that "the cost history does remain with the original associated billing account" — but access to that account depends on who holds it and what roles were retained. If the old agreement's billing scope is no longer accessible to anyone in your organization, your CSP partner may be able to retrieve some invoice-level history, which is far coarser than the daily resource-level data you had. There is no supported way to import old billing-scope history into your new CSP view.
How far back can CSP Continuity collect?
Up to 13 months of history from the Cost Details API, typically available within hours of deployment (2–3 hours for large tenants). That window is why deploying before the transfer matters: pre-transfer, the 13 months reflect your current negotiated rates; post-transfer, collection continues at the new rates, giving you one continuous timeline.
What happens during the transfer window itself?
Microsoft documents that a billing transfer has "no service downtime" — resources keep running, and only the billing relationship changes. Cost Management features on transferred or new subscriptions can take up to 48 hours to become fully usable. CSP Continuity is designed to keep running through the window: per its product FAQ, affected subscriptions are marked temporarily errored and retried on the next daily collection run, and previously collected history is untouched.
Do budgets and saved views carry over?
No. Budgets, saved Cost Analysis views, and exports are attached to the old billing scope. Microsoft recommends downloading cost and usage data and invoices before transferring. Plan to recreate budgets and alerts on the new subscriptions after the move.

The maintained alternative

CSP Continuity deploys from the Azure Marketplace in about 5 minutes, needs one 2-minute PowerShell script, and starts collecting consolidated cost data within hours — entirely inside your tenant.

Deploy the free 30-day trial See the deploy-before workflow

Related guides

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