Azure Nonprofit Grant Not Applied to Subscription. Charged Despite Support assurances (Need Refund & Fix)

Question

Hello,

We are a registered nonprofit using the Microsoft Nonprofit Azure Grant ($2000).

Recently we had an issue where the grant was not applied to our production subscription, even though it had been renewed.

After opening a support ticket, Microsoft support confirmed that the problem was due to the subscription being on the MOSP billing platform, while the sponsorship requires MCA.

Support instructed us to approve a subscription conversion from MOSP -> MCA, which we did. Support confirmed they would convert the subscription and attach the sponsorship credit.

However, despite this:

• The subscription has now generated a bill

We have been charged

• The invoice does not appear in the Azure portal, so the normal refund request workflow cannot be used

The nonprofit grant still does not appear to be offsetting the charges correctly

We have:

The invoice number

The order number

The subscription ID

The previous support case ID

What we need help with:

Ensure the Azure nonprofit sponsorship credit is correctly attached to the production subscription

Refund the charges incurred while the sponsorship was supposed to be applied

Confirm billing is correctly configured going forward

Because the invoice does not appear in the Azure portal, we cannot submit a refund request through the normal billing interface.

If a moderator could please escalate this to Azure Billing / Sponsorship support, it would be greatly appreciated.

Thank you.

Answer 1

Hello @James Dougan

What you’re seeing is unfortunately a known limitation of how Azure Nonprofit Sponsorships and billing platforms work, and nothing in your description suggests misconfiguration on your side.

Azure Nonprofit Sponsorships only apply to subscriptions under a Microsoft Customer Agreement (MCA) Subscriptions on the legacy MOSP (Pay‑As‑You‑Go) platform cannot consume nonprofit sponsorship credits. This requirement is documented in Microsoft’s nonprofit and MCA billing guidance.

The MOSP → MCA conversion does not retroactively block usage or charges When a subscription is in the process of being converted, usage continues to accrue and can be billed, even if sponsorship attachment was expected afterward. The sponsorship credit is only applied once it is explicitly attached to the MCA billing profile and subscription by Microsoft’s billing backend. This attachment step cannot be completed by customers.

Invoices generated during conversion may not appear in the Azure portal Charges generated during backend billing transitions (MOSP → MCA or sponsorship attachment) can result in off‑portal invoices. In those cases, the standard Azure portal refund workflow is unavailable, by design.

Because this involves:

• Sponsorship credit attachment
• MCA billing backend
• An invoice that does not surface in the Azure portal

This must be handled by Azure Billing / Sponsorship Support. There is no customer‑side fix.

Specifically, Microsoft support needs to:

Manually attach the Azure Nonprofit Sponsorship Ensure the $2,000 Azure grant is correctly linked to:

• The correct MCA billing account
  • The correct billing profile
    • The intended production subscription.
    Apply a billing adjustment or refund Charges incurred after the sponsorship renewal but before correct attachment are eligible for manual credit or refund, handled internally by the billing team since the invoice is not visible in the portal. Validate future billing configuration Confirm the subscription is now fully under MCA and consuming sponsorship credits going forward, to prevent further charges.

Please raise support ticket using below link:

Link: submit a support request through our Contact Us form.

Just checking in to see if the below answer helped. If this answers your query, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query, please do let us know

Thanks,
Suchitra.

Answer 2

The scenario involves two separate but related issues: attaching the nonprofit Azure sponsorship to the correct subscription (now on MCA) and resolving/crediting charges that occurred while the grant should have been applied. Both require direct Microsoft support intervention; self-service options are limited, especially since the invoice is not visible in the Azure portal.

Based on the available guidance, the following actions are supported:

1. Escalate through Microsoft nonprofit support (program-level + sponsorship context)
   Because this is specifically about a nonprofit Azure grant (sponsorship) not being applied correctly after a platform conversion (MOSP → MCA), and there is a prior support case, the appropriate escalation path is the Microsoft Nonprofit Support channel:
   1. Go to the Contact Us page for nonprofits: https://nonprofit.microsoft.com/contactus
   2. Select an issue type aligned with Azure grant / sponsorship / billing.
   3. In the description, include:
      • The Azure subscription ID (production subscription).
      • The previous support case ID where support instructed the MOSP→MCA conversion and confirmed the sponsorship would be attached.
      • The invoice number and order number for the charges that were generated.
      • A clear statement that the Azure nonprofit sponsorship credit is not being applied and that the invoice is not visible in the Azure portal, so standard refund workflow cannot be used.
   4. Explicitly request:
      • Attachment of the nonprofit Azure sponsorship to the correct MCA billing profile/subscription.
      • Credit/refund of charges incurred during the period the sponsorship should have been applied, referencing the earlier support assurances.
      • Confirmation that billing is correctly configured going forward (subscription on MCA, sponsorship correctly mapped, no unintended Pay-As-You-Go exposure).
   This Contact Us form is the official and primary support channel for nonprofit-related issues, including grant activation, billing anomalies, and sponsorship misconfiguration.
2. Confirm the sponsorship and billing ownership are aligned within the same tenant
   The documentation emphasizes that Azure nonprofit grants (sponsorships) and billing ownership must be correctly aligned within the same tenant and billing profile to avoid conversion to Pay-As-You-Go and unexpected charges:
   • Nonprofit Azure grants are $2,000 USD per year and must be renewed annually; renewal does not automatically fix billing profile or platform mismatches.
   • If the grant is not attached correctly, usage can convert to Pay-As-You-Go, and charges are applied to the payment instrument on the billing profile.
   • Within the same tenant, it is possible to transfer billing ownership or product ownership so that the sponsorship credit applies to the correct subscription and billing profile. This is done using the Product Transfer Request Tool documented for MCA billing ownership changes.
   In the support request, ask the agent to:
   • Verify that the Azure sponsorship is active and renewed for the tenant.
   • Confirm that the production subscription’s billing profile is the one associated with the nonprofit sponsorship.
   • Use the product/billing ownership transfer process if necessary to move the subscription under the correct MCA billing profile that carries the sponsorship, while staying within the same tenant.
   • Ensure that the sponsorship is not left on a different subscription or profile, which would cause the production subscription to bill as Pay-As-You-Go.
3. Address the non-portal invoice and refund/credit explicitly
   Because the invoice does not appear in the Azure portal, normal self-service refund workflows are not available. The nonprofit and billing support teams must handle this manually. In the Contact Us ticket and any Azure billing support case they open on your behalf, request that they:
   • Locate the invoice using the invoice number, order number, and subscription ID.
   • Confirm that the charges correspond to the period after the MOSP→MCA conversion and during which support had indicated the sponsorship would be attached.
   • Apply a credit or refund for those charges, given that they resulted from the sponsorship not being applied as previously committed.
   • Ensure that any Pay-As-You-Go conversion that occurred during the transition is reversed or corrected where appropriate.
4. Prevent future issues with sponsorship and billing configuration
   Once support has corrected the mapping and addressed the charges, request explicit confirmation and documentation of the final configuration:
   • The Azure grant (sponsorship) is active and visible as a $2,000 annual credit for the current grant year.
   • The production subscription is billed under the MCA billing profile that is linked to the nonprofit sponsorship.
   • No other billing account or profile is inadvertently charging the same subscription as Pay-As-You-Go.
   • Any required billing ownership transfer has been completed and recorded, so that future renewals and sponsorship changes do not break the mapping.
   To avoid similar issues going forward, the nonprofit guidance recommends:
   • Regularly reviewing Azure usage and costs with Cost Management tools to ensure charges are being offset by the grant where expected.
   • Keeping nonprofit tenant and contact information current in the Nonprofit Hub so that renewal and sponsorship communications reach the right admins.
   • Using the Contact Us form promptly if any future discrepancy between sponsorship credits and billing is detected.

Because moderators and peers cannot access billing systems or sponsorship records, only Microsoft support (nonprofit + Azure billing) can attach the sponsorship to the correct MCA subscription and issue credits/refunds. The Contact Us channel is the required escalation path, and the details already collected (invoice number, order number, subscription ID, prior case ID) are exactly what support will need to resolve this.

---

References:

• Microsoft Nonprofit Support
• Renew your Azure grant
• Activate your Azure grant
• Tenant modification
• Grant usage and recurring notifications
• I have an Azure Credit of 11000$$, but I have 2 billing accounts. The bill doesn't come to the right place. - Microsoft Q&A