Description:

Today, Azure Marketplace purchases often ingest into Harness CCM without tags or unique identifiers beyond subscription details. This creates a challenge when trying to allocate costs, especially for recurring annual purchases where each year’s line items look identical in the billing data.

Problem:

Azure Marketplace charges do not generate usage triggers, so inheritance rules cannot apply.

The billing data does not provide unique dimensions to distinguish new charges from previous years.

The only differentiator available is the transaction date, which currently cannot be used in Cost Bucket filter criteria.