I'm using the Microsoft partner Azure credit benefit through the newer Partner Center redemption model. In September 2026, I redeemed a $2,400 credit through Partner Center, and the credit was applied directly to an MCA billing profile. No separate sponsored subscription was created; the credit applies to the subscriptions under that billing profile.
The subscription runs Azure DevOps and Microsoft Fabric. The billing profile's Payment methods > Azure credits section shows the credit as active, with roughly $320 consumed and about $2,079 remaining. However, Cost Analysis shows $0.00 at both subscription and billing-account scope. The services appear in the breakdown, but every amount is 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 the credit was applied. The balance is definitely decreasing, yet there is no detail showing which resources or services are consuming it.
The older guidance about Sponsorship subscriptions and the sponsorship portal appears 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 credit model? Did Cost Analysis eventually begin showing usage, or did you have to rely on the credit Transactions page, invoice usage CSV, Cost Details or Consumption APIs, or a billing support case? If you contacted support, was this considered expected behavior or a reporting bug? I'd also appreciate suggestions for setting budgets or alerts so the credit doesn't get consumed without visibility.
4 Answers
Fabric or DevOps can sometimes make billing visibility confusing, but this doesn’t sound like a simple free-tier situation. Since both services appear in the Cost Analysis breakdown while every amount remains $0.00, it looks more like a reporting or billing-scope issue than a service being free. I’d open a billing support ticket and include screenshots of the declining credit balance, the empty Transactions view, and Cost Analysis at both scopes.
The older partner-credit experience had very limited reporting. Usage usually had to be downloaded through the partner billing area as an Excel or CSV file, rather than viewed normally in Azure Cost Analysis. That may still be part of what’s happening here, although the new billing-profile model is different from the old sponsored-subscription setup.
That legacy workaround doesn’t seem to apply in this case. The new redemption model puts the credit directly on the MCA billing profile, so there is no sponsored subscription or separate sponsorship portal to inspect. The balance is decreasing, but the Transactions view is blank and Cost Analysis remains at zero.
Until the reporting issue is resolved, I’d monitor the credit balance manually and set up whatever subscription-level budgets or Azure Monitor cost alerts are available. Those alerts may not perfectly track the partner credit itself, but they can still warn about rising usage. For an authoritative per-resource breakdown, the invoice usage CSV or Cost Details/Consumption data may be more useful than the zeroed-out Cost Analysis view. A billing case is likely necessary if all of those sources are empty too.
The new model appears to expose the remaining credit balance more clearly, but that doesn’t necessarily mean it provides full cost analysis. The credit Transactions page is probably the intended source for detailed consumption for newer MAICPP credits. If it remains empty despite the balance changing, that strongly suggests the transaction feed has not been populated correctly or the reporting integration is incomplete.
The legacy sponsorship guidance shouldn’t be used as the solution here. This credit was redeemed after the new Partner Center flow was introduced, so the old sponsored-subscription portal does not contain anything for it.
I’m not using a free tier in this case. The subscription includes Fabric and roughly 100 Azure DevOps Basic licenses, and the credit is definitely being consumed. The missing part is the usage detail, not the deduction itself.