I redeemed a $2,400 Azure credit in September 2026 through the newer Microsoft Partner Center flow for an MAICPP Partner Success Core benefit. Unlike the legacy process, the credit was added directly to an MCA billing profile, and no separate sponsored subscription was created. The subscriptions under that billing profile run Azure DevOps and Microsoft Fabric.
The billing profile shows the credit as active, with roughly $320 consumed and about $2,079 remaining. However, Cost Analysis reports $0.00 at both subscription and billing-account scope. The services appear in the breakdown, but all amounts are zero and Actual cost displays "--".
I understand that Cost Analysis may not display the credit itself, but I expected it to show the underlying usage before credits were applied. The older guidance about Sponsorship subscriptions and the sponsorship portal seems to apply only to the legacy model. Microsoft documentation mentions a Transactions view for MAICPP credits issued after August 1, 2026, but that view is currently blank for me.
Has anyone experienced this with the new billing-profile redemption model? Did the usage eventually appear in Cost Analysis, or did you have to rely on the credit Transactions page, invoice usage CSV, Cost Details or Consumption APIs, or a billing support case? I'd also appreciate advice on setting budgets or alerts so the credit does not get consumed without visibility.
3 Answers
The previous experience with partner credits suggests that detailed consumption may only be available through a downloadable usage file, with the Azure portal showing the remaining balance rather than a complete burn-rate view. Unfortunately, that makes planning difficult. Until the reporting path is confirmed, export usage and balance data regularly and configure whatever billing-profile or subscription budget alerts are available. Also verify that the alerts apply to the actual billing scope receiving the charges, since a subscription-level budget may not capture every service or credit transaction.
The older partner-credit setups had very limited reporting. Usage often had to be downloaded from a Partner Center or partner billing page as a spreadsheet, while Azure Cost Analysis did not provide useful detail. That may explain why some of the older advice points to a separate sponsorship portal, but it does not really answer the newer MCA billing-profile scenario.
For the modernized redemption flow, I would check the credit resource’s Transactions view first, then look for usage or invoice exports associated with the billing profile. The balance page confirms that credit is being consumed, but it may not expose the resource-level charges that Cost Analysis normally provides. If Transactions is blank while the balance continues to decrease, that sounds more like a reporting or entitlement issue than a normal Cost Analysis filter problem.
I would open a billing support case and include screenshots showing the starting credit, current balance, the blank Transactions view, and Cost Analysis at both scopes. Support should be able to confirm whether Azure DevOps and Fabric usage is expected to appear there under this billing model or whether the reporting pipeline is delayed or defective.
That is the frustrating part: this is not a legacy Sponsorship subscription. The credit is attached directly to the billing profile, so the old sponsorship portal does not apply. The balance changes, but there is still no itemized usage visible in Cost Analysis.