Azure Cost Details: fully identical AmortizedCost rows contradict documented uniqueness guidance

Michiel de Vos 0 Reputation points
2026-11-17T11:29:58.41+00:00

We ingest Azure Cost Details reports into an external reporting system. In an AmortizedCost report requested at billing-profile scope, we found multiple pairs of records whose decoded values are identical across every exported CSV column.

This appears inconsistent with Microsoft’s guidance that a unique record ID can be constructed from selected exported fields.

We would appreciate clarification from the Azure Cost Management team on whether this is expected behavior, a reporting defect, or a limitation in the documented record-identity guidance.

What we verified

The identical records exist inside a single source CSV returned by Azure, before any field mapping, transformation, aggregation, or deduplication.

We compared every exported column, including columns our ingestion pipeline does not map.

Within each pair, all values match, including resource and subscription identifiers, usage date, meter, product, quantity, unit, prices, costs, tags, additionalInfo, priceFactors, and supplementalChargeDetails.

Where additionalInfo contains an instance identifier, that identifier also matches within the pair.

A separately generated, fresh AmortizedCost report for the same billing scope and usage day contains the same identical pairs.

Separately requested Azure Cost Management queries return totals consistent with retaining both occurrences. The fresh report’s overall daily total also matches the corresponding query total at the precision returned by the query API.

These checks establish consistency between Azure’s published outputs. They do not independently establish whether both occurrences represent valid underlying usage.

Simplified synthetic example

All values below are synthetic. This example shows selected columns for readability; the actual comparison covered every source column.

Date Resource Meter Quantity Unit Cost in billing currency
2026-01-01 example-vm example-meter 12 1 Hour 1.20
2026-01-01 example-vm example-meter 12 1 Hour 1.20

Retaining both occurrences produces a quantity of 24 and a cost of 2.40. Deduplicating by all exported field values produces a quantity of 12 and a cost of 1.20.

Separate underlying usage intervals could explain this pattern, but the exported fields do not establish that explanation or distinguish the occurrences.

Documentation discrepancy

The Cost Details field documentation states:

“Instead, you can use fields in the file flagged with ¹ to create a unique ID yourself.”

When every exported field is identical, no key derived solely from those values can distinguish the two occurrences.

We are also aware of the documented explanation for multiple records per resource and day. That example involves different values in AdditionalInfo; in this case, additionalInfo and every other exported field match.

Expected behavior

The documented identity fields should distinguish individual records. Alternatively, if distinct source occurrences can legitimately have identical exported values, the documentation should describe that exception and the supported ingestion approach.

This matters because field-based deduplication removes amounts that Azure includes in its reported totals, while simply appending regenerated reports would count previously imported usage again.

Questions for the Azure Cost Management team

Can a completed AmortizedCost report legitimately contain multiple records identical across all exported fields?

If so, what distinguishes the underlying usage records, and is there a supported identifier or additional field available to consumers?

Does the documented guidance for constructing a unique record ID need correction or qualification?

What is the supported approach for preserving legitimate occurrences while processing regenerated or corrected reports idempotently?

A previous report from October 2023 also describes collisions when using the documented identity fields. That case differed in some numeric fields; our observation concerns equality across the entire exported row.

Customer information and diagnostic identifiers have been omitted from this public report. Please advise on an appropriate private channel for supplying additional diagnostic details if required.

Summary

We ingest Azure Cost Details reports into an external reporting system. In an AmortizedCost report requested at billing-profile scope, we found multiple pairs of records whose decoded values are identical across every exported CSV column.

This appears inconsistent with Microsoft’s guidance that a unique record ID can be constructed from selected exported fields.

We would appreciate clarification from the Azure Cost Management team on whether this is expected behavior, a reporting defect, or a limitation in the documented record-identity guidance.

What we verified

The identical records exist inside a single source CSV returned by Azure, before any field mapping, transformation, aggregation, or deduplication.

We compared every exported column, including columns our ingestion pipeline does not map.

Within each pair, all values match, including resource and subscription identifiers, usage date, meter, product, quantity, unit, prices, costs, tags, additionalInfo, priceFactors, and supplementalChargeDetails.

Where additionalInfo contains an instance identifier, that identifier also matches within the pair.

A separately generated, fresh AmortizedCost report for the same billing scope and usage day contains the same identical pairs.

Separately requested Azure Cost Management queries return totals consistent with retaining both occurrences. The fresh report’s overall daily total also matches the corresponding query total at the precision returned by the query API.

These checks establish consistency between Azure’s published outputs. They do not independently establish whether both occurrences represent valid underlying usage.

Simplified synthetic example

All values below are synthetic. This example shows selected columns for readability; the actual comparison covered every source column.

Date Resource Meter Quantity Unit Cost in billing currency
2026-01-01 example-vm example-meter 12 1 Hour 1.20
2026-01-01 example-vm example-meter 12 1 Hour 1.20

Retaining both occurrences produces a quantity of 24 and a cost of 2.40. Deduplicating by all exported field values produces a quantity of 12 and a cost of 1.20.

Separate underlying usage intervals could explain this pattern, but the exported fields do not establish that explanation or distinguish the occurrences.

Documentation discrepancy

The Cost Details field documentation states:

“Instead, you can use fields in the file flagged with ¹ to create a unique ID yourself.”

When every exported field is identical, no key derived solely from those values can distinguish the two occurrences.

We are also aware of the documented explanation for multiple records per resource and day. That example involves different values in AdditionalInfo; in this case, additionalInfo and every other exported field match.

Expected behavior

The documented identity fields should distinguish individual records. Alternatively, if distinct source occurrences can legitimately have identical exported values, the documentation should describe that exception and the supported ingestion approach.

This matters because field-based deduplication removes amounts that Azure includes in its reported totals, while simply appending regenerated reports would count previously imported usage again.

Questions for the Azure Cost Management team

Can a completed AmortizedCost report legitimately contain multiple records identical across all exported fields?

If so, what distinguishes the underlying usage records, and is there a supported identifier or additional field available to consumers?

Does the documented guidance for constructing a unique record ID need correction or qualification?

What is the supported approach for preserving legitimate occurrences while processing regenerated or corrected reports idempotently?

A previous report from October 2023 also describes collisions when using the documented identity fields. That case differed in some numeric fields; our observation concerns equality across the entire exported row.

Customer information and diagnostic identifiers have been omitted from this public report. Please advise on an appropriate private channel for supplying additional diagnostic details if required.

Cost Management
Cost Management

A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.


1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-17T11:31:11.93+00:00

    Do not deduplicate these rows by exported values; retain each physical CSV occurrence, replace previously loaded report partitions rather than appending regenerated reports, and open an Azure billing support request because the public documentation does not explain or guarantee distinguishability for fully identical records.

    What the documentation establishes

    • Cost Details files have no native per-record ID. Microsoft says fields marked ¹ can be combined to create an ID, while also stating that every record in the file should be considered unique.^1^
    • A resource or meter can legitimately have multiple records on one day. However, the documented example attributes this to differences in AdditionalInfo; it does not address records identical across every exported field.^2^
    • Amortized Cost reallocates reservation and savings-plan costs to benefiting resources. That explains why amortized data can contain multiple charge allocations, but it does not establish that two fully identical exported rows are expected or provide a hidden identifier consumers can use.^3^

    Consequently, the available public contract does not answer whether your pairs represent separate underlying usage or a reporting defect. It also exposes no additional supported field that can distinguish them. The documented identity guidance needs clarification if rows can legitimately collide across all exported values.

    Your reconciliation result is operationally decisive: because Azure’s query and report totals include both occurrences, value-based deduplication would understate Azure-reported quantity and cost.

    Idempotent ingestion design

    Treat each generated report as a snapshot for its requested scope, metric, schema version, and time range, not as an append-only event stream:

    1. Store the original file and report metadata unchanged.
    2. Assign each physical row an ingestion-local ordinal, such as:
      • report/run identifier;
      • source file or partition name;
      • row number within that file.
    3. Keep a hash of the decoded row as a fingerprint for diagnostics, but do not use that hash as a uniqueness constraint. Identical hashes can have multiplicity greater than one.
    4. Load the new report into staging.
    5. Validate its totals and row counts against the downloaded source.
    6. In one transaction, replace the previously loaded partition for the exact same scope, metric, schema, and covered period.
    7. Publish the replacement only after validation succeeds.

    For example:

    begin transaction;
    
    delete from cost_detail
    where billing_scope = @scope
      and metric = 'AmortizedCost'
      and usage_date between @start_date and @end_date;
    
    insert into cost_detail (
        billing_scope, metric, report_id, source_file, row_ordinal,
        row_fingerprint, usage_date, quantity, cost, raw_row
    )
    select
        billing_scope, metric, report_id, source_file, row_ordinal,
        row_fingerprint, usage_date, quantity, cost, raw_row
    from cost_detail_stage;
    
    commit;
    

    The key point is that row_ordinal distinguishes physical occurrences only within a particular report snapshot. It must not be treated as a stable Azure identity across regenerated reports.

    For scheduled Cost Management Exports, Azure provides an Overwrite data option, enabled by default for new exports; daily exports then replace the previous day’s exported file with updated data.^4^ This is the clearest documented replacement model. It does not create a row identity, but it can simplify downstream idempotency: ingest each overwritten path as a replacement snapshot rather than appending it.

    Replacement is also important because charges in the current billing period can be rerated until the invoice closes.^5^ Avoid merging regenerated reports solely by row hash: that cannot distinguish a legitimate multiplicity change from a rerating correction.

    Private investigation and documentation clarification

    Open Azure portal → Help + support → Create a support request, selecting the subscription associated with the billing profile and the closest Billing/Cost Management problem classification. Creating the request requires Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope.^6^

    Attach a compressed diagnostic package containing:

    • Cost Details operation/report identifiers and generation timestamps.
    • Billing-profile scope and requested date range.
    • Metric and schema version.
    • Source file/partition names and row numbers.
    • SHA-256 hashes of the original files and affected decoded rows.
    • A redacted extract preserving duplicate multiplicity.
    • Expected versus actual row counts, quantities, and costs.
    • Corresponding Cost Management query request dimensions and returned totals.
    • Confirmation that a fresh report reproduced the same pairs.

    Ask support to confirm specifically:

    1. Whether each occurrence maps to a distinct internal rated-usage or amortization record.
    2. Whether an internal distinction was omitted from the public schema.
    3. Whether the output violates the documented ¹-field identity guidance.
    4. Whether consumers should use report-level replacement as the supported idempotency boundary.

    Until Microsoft makes that determination, preserving both physical occurrences and reconciling their aggregate is the only approach consistent with the published Cost Details totals and the instruction to consider every record unique.


    References

    1. Understand cost details fields
    2. Ingest cost details data
    3. View amortized benefit costs - Microsoft Cost Management | Microsoft Learn
    4. Tutorial: Create and manage Cost Management exports
    5. Understand Cost Management data
    6. Create an Azure support request
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.