Managing Duplicate Azure Costs When Transitioning from PAYG to Enterprise Agreement (EA)

Products

• CloudHealth

Issue/Introduction

When a customer initially connects an Azure environment to CloudHealth using a Service Principal to collect Pay-As-You-Go (PAYG) billing data, CloudHealth begins ingesting and storing those line items.

If the customer later transitions to an Azure Enterprise Agreement (EA) and configures the EA enrollment within CloudHealth, the platform begins collecting data from the EA API. Because the PAYG data and the EA data may cover the same resources for overlapping time periods, and because PAYG costs are not automatically purged or overwritten by the EA ingestion, this results in duplicate cost reporting in the CloudHealth platform.

Symptoms

• Total Azure spend appears significantly higher than expected in Dashboards and Flex Reports.

• Duplicate line items appear for the same Resource ID within the same billing period.

• One set of costs reflects PAYG rates while the other reflects EA negotiated rates.

Resolution

Currently, CloudHealth does not automatically reconcile or delete legacy PAYG data when an EA is added. Manual intervention by the CloudHealth Engineering team is required to purge the redundant records.

Steps to Resolve

1. Verify the Overlap: Identify the specific subscriptions and the date range where the PAYG data overlaps with the EA data.

2. Open a Support Ticket: Contact CloudHealth Technical Support to request a manual duplicate cost cleanup.

3. Required Information: Include the following details in your ticket to expedite the process:

   • CloudHealth Client Name

   • Azure Enrollment Number

   • List of affected Subscription IDs

   • The specific date range for which the PAYG data needs to be removed (e.g., "Purge all PAYG data for Subscription X from January 1st to January 15th").

Once the redundant PAYG data is purged, your reports will accurately reflect only the EA billing data.