Skip to main content
Skip table of contents

Azure Consumption Usage Report

Azure Usage Reports

The Azure Usage Report provides a detailed summary of the Azure resources utilized during a billing cycle.

  1. Navigate to My Services > Microsoft Azure > Usage Report

  2. There are two options: Export Instantly and Schedule Report

  3. Export Instantly - Choose the period for which you’d like to export the usage report and send to your email.

    Screenshot 2025-05-07 at 15.42.19.png
  4. Schedule Reports - Schedule the subscription usage report to run periodically and send the results to your email.

    Screenshot 2025-05-07 at 15.47.19.png

Consumption Usage Report on Organization Level

Roles →

Broker Admin roles

Key Account Manager roles

Sales Agent role

Organization Admin

OrganizationId

(tick)

(tick)

(tick)

(tick)

OrganizationName

(tick)

(tick)

(tick)

(tick)

MicrosoftCustomerId

(tick)

(tick)

(tick)

(tick)

CloudmoreCustomerNumber

(tick)

(tick)

(tick)

(tick)

ProductName

(tick)

(tick)

(tick)

(tick)

ProductId

(tick)

(tick)

(tick)

(tick)

Sku

(tick)

(tick)

(tick)

(tick)

SkuName

(tick)

(tick)

(tick)

(tick)

CustomerCountry

(tick)

(tick)

(tick)

(tick)

SubscriptionId

(tick)

(tick)

(tick)

(tick)

SubscriptionDescription

(tick)

(tick)

(tick)

(tick)

EntitlementId

(tick)

(tick)

(tick)

(tick)

EntitlementDescription

(tick)

(tick)

(tick)

(tick)

ChargeStartDate

(tick)

(tick)

(tick)

(tick)

ChargeEndDate

(tick)

(tick)

(tick)

(tick)

Quantity

(tick)

(tick)

(tick)

(tick)

UnitPrice

(tick)

(tick)

(tick)

(tick)

Total

(tick)

(tick)

(tick)

(tick)

InvoiceCurrency

(tick)

(tick)

(tick)

(tick)

BillingProvider

(tick)

(tick)

(tick)

(tick)

PublisherName

(tick)

(tick)

(tick)

(tick)

MeterCategory

(tick)

(tick)

(tick)

(tick)

MeterSubCategory

(tick)

(tick)

(tick)

(tick)

MeterId

(tick)

(tick)

(tick)

(tick)

MeterName

(tick)

(tick)

(tick)

(tick)

MeterRegion

(tick)

(tick)

(tick)

(tick)

MeterType

(tick)

(tick)

(tick)

(tick)

UsageStartDate

(tick)

(tick)

(tick)

(tick)

UsageEndDate

(tick)

(tick)

(tick)

(tick)

ChargeType

(tick)

(tick)

(tick)

(tick)

Tags

(tick)

(tick)

(tick)

(tick)

ResourceName

(tick)

(tick)

(tick)

(tick)

ResourceGroup

(tick)

(tick)

(tick)

(tick)

Azure Usage Charts

This provides an interactive visual overview of their usage data directly on the platform, eliminating the need to download detailed reports. The charts are divided into two sections:

  1. Split by Subscription: Shows how costs for each subscription are changing over time.

  2. Split by Meter Category: Displays which resource types are driving the highest costs and how these costs are evolving.

Azure Usage in General 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 that.

The Azure Plan container represents the billing relationship and ensures that any billing from any subscription below the Azure Plan container would be 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 they need.

In the Microsoft billing reconciliation file, only the Azure Plan container is available, not the individual subscriptions. As Cloudmore bases our billing on the Microsoft reconciliation data to ensure complete alignment with the Microsoft invoice, we don't get the data needed to understand what 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 very clear that the usage data is not billing data. This is true as some usage data will be billed the month thereafter, and costs do not match exactly the billing file because of rounding, incentives, and other affecting items.

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 hard to do as the usage data does not always match. Cloudmore will not match any data that we are not confident matches the data from the usage file. The reason for this is not to falsely put an Azure cost under the wrong subscription. As a backup logic, any data that can't be matched will remain in the Azure Plan container.

When data is matched, we try 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 we can't match it with confidence.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.