As from December 1, Azure Plan Usage is using the purchase overrides.

Reason

Only common metadata from the purchases going into the SUM rules and Ladders could be preserved. Hence, the conflicting data on purchases, like instance names or custom tags would disappear. In that case, the ladder rules would not always apply properly, as well as the missing data would limit CloudBilling from grouping it on the invoice.

What has been changed?

The purchases under the “Azure Plan” category have changed their pricing rule structure and now utilize overrides as their costs and values. The changes do not affect any customers in a negative way. On the contrary, some of our customers’ specifications are displaying “Azure Plan” products grouped by a required metadata tag, which was impossible before.

How does this functionality work?

For every tenant, the pricing rule structure for “Azure Plan” is now automatically using the purchase overrides as the values to perfectly match with Microsoft pricing and customers’ grouping on the invoices.

How can you start using this functionality?

The functionality has been turned on for every customer by default.