Overview
This document explains how Azure Plan Consumption items can be grouped and categorized in the Billing Report. It explains the logic that Cloudmore uses to match the Azure Consumption Report to the General Billing Report as closely as possible.
Enabling Azure Data in Billing Report
-
Enable Azure Plan invoice based usage data - This is the main control that starts matching Azure usage data to the Billing Report. Starting from the day this checkbox is checked, the usage data will be matched. This cannot be done retroactively. The period start shows when the checkbox was actually checked. The period end shows the current date.
-
Show Azure entitlements in billing - This checkbox controls whether Azure Plan Consumption is grouped under subscriptions (entitlements) in the Billing Report. This setting can be used to either group entitlements or not, depending on your needs.
-
Pass Azure plan consumption 100% discount to organisations - This checkbox controls whether brokers pass the full Azure plan discount directly to their organizations.
-
When enabled, the organization receives the full 100% discount.
-
When disabled, normal pricing applies.
-
It is unchecked by default for new brokers, but enabled for existing brokers to maintain compatibility and prevent breaking changes.
-
Azure Usage Data Matching in Billing Report
When you create your first Microsoft Azure subscription under the New Commerce Experience (NCE), two items are created: a Microsoft Azure Plan container and an Azure subscription underneath it.
The Azure Plan container represents the billing relationship and ensures that any billing from any subscription below the Azure Plan container is invoiced to the CSP partner.
The Azure subscription allows customers to split their consumption into several logical units. By default, a single subscription is created, but customers can create as many logical subscriptions as needed.
In the Microsoft billing reconciliation file, only the Azure Plan container is available, not the individual subscriptions. Since Cloudmore bases billing on the Microsoft reconciliation data to ensure complete alignment with the Microsoft invoice, we do not get the data needed to understand which billing lines belong to each Azure subscription.
Microsoft also provides usage data with additional details to help you understand your billing. Microsoft has made it clear that the usage data is not billing data. Some usage data will be billed the month thereafter, and costs do not match exactly due to rounding, incentives, and other factors.
Matching Logic
As a workaround, Cloudmore has built logic that tries to match the billing reconciliation file with data from the usage file. This logic has proven to be complex, as the usage data does not always match. Cloudmore will not match any data that cannot be matched with confidence, in order to avoid falsely putting an Azure cost under the wrong subscription. Any data that cannot be matched will remain in the Azure Plan container.
When data is matched, Cloudmore attempts to match on entitlementId (Azure Plan container ID), productId + SkuId, and quantity. The cost will be assigned to the correct subscription if a precise match is found. It will remain at the Azure Plan level if the match cannot be made with confidence.