Skip to content
FinOps workspace
COST LEDGER / OFFICIAL RELEASE

Azure Cost Management AWS connector retired on 31 March 2025

Published and reviewed: 1 October 2026

Scope my cloud cost review

Microsoft retired the AWS connector in Azure Cost Management on 31 March 2025.

Illustrative server cabinets in a mint-lit room
Illustration, not customer infrastructure.
On this page
  1. What Microsoft stated
  2. Who is concerned today
  3. Rebuilding a reporting path from retained files
  4. Reconciliation and the questions to settle
  5. Primary sources

What Microsoft stated

In the March 2025 edition of its « Microsoft Cost Management updates » series, published on 12 March 2025, Microsoft wrote that the Connector for AWS, built to consolidate Azure and AWS cost data in Microsoft Cost Management, would be retired on 31 March 2025. The post says customers lose access to the connector and that AWS cost and usage data stored in the cost management service, including historical data, would be removed. It adds that Microsoft would not delete the Cost and Usage Report (CUR) files that customers stored in their own S3 bucket as part of the connector setup.

Microsoft asked customers to move to their own choice of reporting for AWS and to delete the connector in the Azure portal. As an alternative it points to exporting data in FOCUS format and using an analytics and reporting solution such as Microsoft Fabric. The retirement date is now in the past: this is a record of an event, not a current deadline.

Who is concerned today

Only organizations that connected an AWS account to Azure Cost Management are concerned. If you never did, there is nothing to remediate and no mission to commission. If you did, the data that lived in Microsoft's service was removed, according to Microsoft's own statement, and what remains is whatever you kept in AWS: the CUR files in your S3 bucket.

Finance may also depend on artifacts built on top of the connector: saved views, budgets, exports, a monthly multicloud slide. These did not live in the bucket.

Rebuilding a reporting path from retained files

Start from an inventory of what exists. List the CUR objects in the bucket, the periods they cover, their format and the account that owns the bucket. The Microsoft post confirms that the retirement did not delete them, but it says nothing about retention rules you may have configured yourself, so check the bucket's lifecycle settings.

Then choose a replacement reporting approach from what is available and what finance needs to decide. A FOCUS export is one input, and the version actually produced by the source needs checking, as explained in the FOCUS implementation checklist. The alternatives Microsoft names, such as Fabric, are tools: they do not remove the need for a mapping and a reconciliation.

Reconciliation and the questions to settle

Reconcile one known month against the AWS invoice before any trend chart is trusted. Explain any gap between the restored figure and what was reported at the time, for example a change of cost basis (billed or effective) between the old connector view and the new one.

  • Ask the provider to price historical reconstruction separately from ongoing reporting.
  • If history is missing for some periods, the deliverable should mark the limit openly. Figures filled in to make a chart continuous would corrupt later comparisons.
  • Agree who owns the export configuration and the queries after handover.

This is also why a managed FinOps agreement should state who holds the data exports and the reporting logic, so that one tool's retirement does not erase the history.

Primary sources

The Microsoft Azure blog post of 12 March 2025, read in full for this page:

Continue your review

Get support on my project

A specialist in the subject reviews your request and sends you a quote.

Get support on my project
Get my FinOps quote