🐛 Problem

The following gaps have been reported when comparing Cost Management FOCUS 1.0 exports with the specification. This is not an exhaustive list. This is only covering what issues have been reported. If you notice any gaps, please leave a comment so we can add it to the list.

FinOps toolkit issues

• CommitmentDiscountStatus is null for FOCUS 1.0 preview unsed savings plan charges.
• ServiceCategory is "Other" for unused savings plan charges. Need to confirm service mapping.

Cost Management issues

• BillingAccountType should be prefixed with x_.
• ChargeDescription is null for unused savings plan charges.
• ConsumedQuantity is 0 for unused savings plan charges. Spec does not indicate how to handle this. Should be null if not available.
• ConsumedUnits is "Units" for unused savings plan charges.
• ContractedCost is 0 for unused savings plan charges. Should not be 0 and should be null if not available.
• ContractedUnitPrice is 0.001 for unused savings plan charges. (This may be a test account issue.)
• EffectiveCost is 0 for unused savings plan charges. Should not be 0 and should be null if not available.
• InvoiceIssuerName is "Microsoft" for partners who resell Microsoft Cloud services. This is an unclear aspect of the spec.
• ListCost is 0 for unused savings plan charges. Should not be 0 and should be null if not available.
• ListUnitPrice is 0 for unused savings plan charges. Should not be 0 and should be null if not available.
• PricingQuantity is 0 for unused savings plan charges. Spec does not indicate how to handle this. Should be null if not available.
• PricingUnits is "Units" for unused savings plan charges.
• PublisherName is null for unused savings plan charges.
• ServiceName is null for unused savings plan charges.
• SkuId is null for unused savings plan charges.
• SkuPriceId is -2 for unused savings plan charges.
• SubAccountName is "Unassigned" for unused savings plan charges. Should be null.
• SubAccountType should be prefixed with x_.

Known gaps that are in line with the FOCUS spec

• AvailabilityZone should be specified when applicable

🙋‍♀️ Ask for the community

We could use your help:

1. Please vote this issue up (👍) to prioritize it.
2. Leave comments if you've found an issue that should be added to the list.