Microsoft.Consumption Events API Returns Only One ConsumptionCommitment Event While Lots API Returns Valid MACC Data for MCA Billing Account

For a Microsoft Customer Agreement (MCA) billing account, MACC tracking via the Consumption APIs behaves as follows based on the documented behavior.

1. Events API and MACC history

For MACC, the documented Events API call is:

GET https://management.azure.com/providers/Microsoft.Billing/billingAccounts/<billingAccountName>/providers/Microsoft.Consumption/events?api-version=2021-05-01&startDate=<startDate>&endDate=<endDate>&$filter=lotsource%20eq%20%27ConsumptionCommitment%27

Key points from the documentation:

• The Events API "returns all events that affected your MACC" for the given date range.
• Events are described as invoiced spending that decremented the MACC, with fields such as transactionDate, charges, closedBalance, and invoiceNumber.
• Only SettledCharges events are supported for MACC.

Therefore:

• The Events API is intended to return all MACC-related settlement events within the specified startDate/endDate window, not just the latest event.
• If only one event is returned, it is typically because only one SettledCharges event exists in the specified date range, or because the date range/filter effectively narrows the result to that single event.

2. Required filters / parameters for historical MACC events

The MACC documentation shows the minimum required parameters:

• startDate (required)
• endDate (required)
• $filter=lotsource eq 'ConsumptionCommitment' (to restrict to MACC events)

Example:

GET https://management.azure.com/providers/Microsoft.Billing/billingAccounts/<billingAccountName>/providers/Microsoft.Consumption/events?api-version=2021-05-01&startDate=2024-01-01&endDate=2024-12-31&$filter=lotsource%20eq%20%27ConsumptionCommitment%27

The documentation does not list any additional required filters (such as lotId) to retrieve historical MACC events. Filtering by lotSource is sufficient to get all MACC events for the billing account in the specified date range.

3. Balances API support for MCA billing accounts

For MCA, the documented pattern for tracking credit/MACC-like balances is:

• Use Microsoft.Consumption/lots to retrieve credit or commitment lots and their closedBalance.
• Use Microsoft.Consumption/events to retrieve transactions that affect those lots.

For MCA credit balance (not MACC), the documented REST pattern is:

GET https://management.azure.com/providers/Microsoft.Billing/billingAccounts/<billingAccountId>/billingProfiles/<billingProfileId>/providers/Microsoft.Consumption/lots?api-version=2023-03-01

and events via:

GET https://management.azure.com/providers/Microsoft.Billing/billingAccounts/<billingAccountID>/billingProfiles/<billingProfileID>/providers/Microsoft.Consumption/events?api-version=2023-03-01&startDate=<date>&endDate=<date>

The documentation for MCA focuses on lots and events and does not describe a Microsoft.Consumption/balances endpoint for MCA billing accounts. Instead, it explicitly states that the available balance is computed by aggregating closedBalance across active credits.

Given this, the supported pattern for MCA is:

• Use lots + events to derive balances.
• A dedicated balances endpoint is not documented for MCA.

4. Known limitations for Microsoft.Consumption/events and Microsoft.Consumption/balances with MCA

From the documented MCA behavior:

• Events:
  • Only SettledCharges events are supported for MACC.
  • Events are tied to invoiced spending; if there are few invoices or limited MACC-eligible spend, the number of events will be correspondingly small.
  • Events require startDate and endDate and can be filtered by lotSource = 'ConsumptionCommitment'.
• Balances:
  • For MCA, balance information is exposed via lots (closedBalance fields) and events, not via a separate balances resource.
  • A 404 from a balances endpoint for an MCA billing account is consistent with the absence of documented support for Microsoft.Consumption/balances for MCA.

In practice for MCA MACC:

• Use the Lots API (Microsoft.Consumption/lots) to get MACC commitment metadata and remaining balance (closedBalance).
• Use the Events API (Microsoft.Consumption/events with lotSource eq 'ConsumptionCommitment' and a suitable date range) to retrieve all MACC settlement events.
• Do not rely on Microsoft.Consumption/balances for MCA; instead, compute balances from lots and events.

References:

• Track your Microsoft Azure Consumption Commitment (MACC)
• Track Your Azure credit balance for a Microsoft Customer Agreement
• Manage a Microsoft Azure Consumption Commitment resource under a subscription