Home › Claude charges
Unexpected Claude Charges on Azure: Why They Happen and How to Fix Them
If you deployed Claude through Azure AI Foundry and your startup credits didn’t cover it, you are not the first and you are not alone.
The short answer: Claude models in Microsoft Foundry are billed as Marketplace usage, not standard Azure consumption. Microsoft for Startups credits apply to Azure-billed services, so they do not apply to Claude. The charge lands on the card attached to your subscription, and the invoice shows Azure Credit 0 on that line.
Claude charges on Azure are the most common version of this problem.
Why you were charged
Microsoft sells some models directly. Azure OpenAI is the obvious example: it is billed as normal Azure consumption, and your credits apply.
Other models in the same catalog are published by partners and billed through Microsoft Marketplace. Claude is one of them. It is deployable from Foundry, it looks like a Foundry model, and it appears on your Azure invoice — but the billing source is different, so the credits do not apply.
Microsoft states this in its own documentation:
“Startup credits apply to Microsoft Foundry models that are sold and billed directly by Azure. Models billed by third-party providers (including Anthropic), partner services, or available through the Microsoft Marketplace are not eligible.”
— Sponsorship Coverage for Microsoft Foundry Models, updated 22 October 2026
Anthropic is the first provider named in the “not covered” list.
The rule is published. The problem is where it is published.
Check your invoice in 30 seconds
Azure Marketplace Claude charges are the line item to look for. Open the invoice PDF and check these three things:
| What to look for | What it means |
|---|---|
| A SaaS line in the product breakdown | This is the Marketplace charge |
| Azure Credit 0 | Your credits were not applied to this line |
| Publisher listed as Anthropic | Confirms the billing source |
If the SaaS line plus 18% GST equals your invoice total, the entire bill is the Claude charge. Everything else was credited.
That is the signature. It is not a balance problem — it is a coverage problem.
What to do right now
1. Stop the deployment
Pause or delete the Claude deployment in Foundry. The meter runs on tokens, not on your attention.
2. Confirm the line on the invoice
Use the table above. If the uncovered amount matches the Claude usage, you are dealing with a Marketplace charge.
3. Open an Azure support ticket
Go to Azure Help + Support → Create a support request → Billing → Unexpected charges.
The dropdowns do not have a clean category for this. Put your actual issue in the Summary field and choose the closest problem type. If the portal tries to route you to “Resolve inability to sign up,” use Return to support ticket at the top to continue.
4. Ask for a one-time courtesy waiver — in writing
Ask specifically for a one-time billing exception or courtesy credit, not for a standard refund. There is precedent: in one public case, Microsoft offered a $1,000 partial credit as a “special exception.”
It is not a policy. But it has happened, and asking for the right thing matters.
5. Contact Anthropic as well — and keep the reply
Anthropic will most likely tell you that Azure Marketplace billing is handled by Microsoft. Keep that email. It is not a dead end; it is evidence that neither party is taking ownership.
6. Document everything
Invoices, support case numbers, dates, screenshots, and every reply. If you later escalate publicly or formally, the timeline is the case.
7. Plan for payment or a formal dispute
Do not assume a refund. Most founders in the public threads did not get one. Decide early whether you can pay, need a payment extension, or will dispute the charge — because the subscription can be suspended while the case is open.
What to expect from each party
| Party | Typical response |
|---|---|
| Azure Billing | “Marketplace charges cannot be covered by sponsorship credits. Contact the publisher.” |
| Anthropic | “Azure Marketplace billing is handled by Microsoft. We can’t issue refunds.” |
| Microsoft for Startups team | “The current program policy does not support a waiver. Work with Azure Support.” |
That is the loop. It is documented in writing across multiple cases, and it is the single most useful thing to know before you start.
How to avoid it before you deploy
The five-point check
- Open the model card. Read the top panel, not the pricing accordion.
- Check the collection. “Direct from Azure” models are covered. “Models from Partners and Community” are not — that includes every Claude model.
- Open the Pricing section and search for the sentence. If it says “Azure credits cannot be applied,” budget for it.
- Check Cost Management. Filter by Marketplace and by publisher Anthropic. If usage appears there, it is not drawing on your credits.
- Set a budget alert and a hard cap before you deploy.
The tell that most people miss
If your credit balance is not moving while you are generating tokens, that is not a good sign. It is the warning. Marketplace usage does not draw down sponsorship credits, so the balance stays flat while the card accumulates charges.
The one-line rule: If Microsoft bills it directly, credits apply. If a partner bills it through Marketplace, they don’t.
Other founders have hit this
This is not a one-off. On Microsoft’s own community platform, the same invoice appears month after month:
| Date | Founder | Amount |
|---|---|---|
| Jan 2026 | Playpals | ~€1,000 |
| Mar 2026 | Takuya Tominaga (via The Register) | ~$1,600 |
| Mar 2026 | Second case reported by The Register | ~$3,000 |
| Apr 2026 | chrisbaker2000 (Further Inc.) | $17,493 |
| Sep 2026 | sathshrik | ₹70,716.76 |
| Sep 2026 | NethanDevnath-6 | ₹1,47,000 |
| Sep 2026 | Cgriffs | $22,000 |
| Oct 2026 | khalifamanaa (Sampo AI) | $834.74 |
| Oct 2026 | granwel (UK student) | ~£470 |
| Aug 2026 | This case | ₹1,72,565.13 |
The details repeat:
- sathshrik had ₹9.49 lakh of credits still unused when the ₹70,716.76 invoice arrived.
- khalifamanaa: “Nothing in the Foundry deployment flow said Claude is excluded from startup credits, and our earlier OpenAI usage in Foundry was covered, so we assumed Claude would be too.”
- chrisbaker2000: “Microsoft directs us to Anthropic. Anthropic directs us to Microsoft. The Microsoft for Startups team directs us to Azure Marketplace billing. No one takes responsibility.”
For a funded startup this is a painful invoice. For a bootstrapped founder it can be the runway. Several stopped their deployments the moment they saw the charge. One is a university student.
Sources for the table above
- Playpals, Founders Hub billing issue — stuck between Microsoft and ISV, Jan 2026.
- The Register, Founder finds Azure startup credits don’t apply to Claude, 13 Mar 2026.
- chrisbaker2000, $17,493 in Undisclosed Marketplace Charges, 13 Apr 2026.
- sathshrik, How can a Microsoft for Startups user escalate unexpected Claude Marketplace billing?, 14 Sep 2026.
- NethanDevnath-6, Unexpected ₹147K Claude charges despite active Microsoft for Startups sponsorship, 17 Sep 2026.
- Cgriffs, Unexpected $22,000 Azure Marketplace Charge, 18 Sep 2026.
- khalifamanaa, Startup credits didn’t cover Claude in Foundry — $834 charged to card, 14 Oct 2026.
- granwel, Claude on Foundry billed outside my credits as a Marketplace charge, 24 Oct 2026.
- Microsoft Q&A, Azure AI Foundry presents third-party AI models as native Azure services (the $1,000 partial-credit precedent).
- Microsoft Learn, Sponsorship Coverage for Microsoft Foundry Models, updated 22 Oct 2026.
The fix Microsoft could ship
The warning already exists — it is inside a collapsed Pricing section, several screens below the Deploy button. The panel beside the button says “Hosted on Azure” and nothing about credits.
Five placement changes would close the gap:
Billing row
Add one row to Quick facts: Billing — Marketplace (not covered by startup credits).
Deploy line
Put one line above Deploy: “This model is Marketplace-billed. Startup credits do not apply.”
Hosted label
Replace “Hosted on Azure” with Hosted on Azure · Marketplace-billed.
Pricing default
Expand Pricing by default for non-eligible models.
Catalog marker
Add an amber marker in the model catalog list.
None of these is a policy change. All five are front-end work.
Read the full case, with the invoice figures and the UI evidence →
FAQ
Are Claude models covered by Microsoft for Startups credits?
No. Microsoft’s policy page lists Anthropic among the providers whose models are not eligible. All Claude models deployed through Foundry are billed as Marketplace usage.
Why did my credits cover everything except Claude?
Because the other lines were first-party Azure consumption. The Claude line was a Marketplace SaaS subscription. Credits apply to the first, not the second.
Why did Microsoft for Startups Claude charges appear on my card?
Because the Claude deployment was billed through Microsoft Marketplace, not as first-party Azure consumption. Microsoft for Startups credits only apply to services billed directly by Azure.
Can I get a refund for unexpected Claude charges?
It is difficult. Azure Billing typically says Marketplace adjustments are handled by the publisher. Anthropic says Azure Marketplace billing is handled by Microsoft. Some founders have received partial credits; most have not.
Who do I contact first?
Azure Support, under Billing → Unexpected charges. Then Anthropic, and keep the reply. Then the Microsoft for Startups team, for visibility.
How do I check before deploying?
Open the model card, confirm it is in “Direct from Azure” rather than “Models from Partners and Community,” and read the Pricing section for the sentence about Azure credits.
Does this affect Claude on AWS or Google Cloud?
It is a different program with a similar rule. According to Anthropic’s startup program terms, its credits apply to the first-party Claude API only — not to Claude through Bedrock, Vertex AI or Foundry.
Right of reply
The program’s intent is good. The credits are real, and they let founders build things they could not otherwise afford. But goodwill is fragile. When a founder who was supposed to benefit ends up with a bill they cannot pay, part of that goodwill is lost — not because the policy is wrong, but because the warning arrived after the decision. That is the real cost of a disclosure gap.
Microsoft and Anthropic are invited to respond. Any substantive response will be published here in full, with a date.
Corrections are welcome and will be dated.
Related
- Azure AI Foundry Pricing: What Startup Credits Cover — and What They Don’t — the invoice case and the UI evidence.
- Microsoft for Startups: A Founder’s Field Guide — what the program gives you, and what to check before you deploy.
- Best Small Business Tools Stack Under $100 in 2026 — how to keep the rest of the stack inside a budget while you absorb a Marketplace charge.
- Best AI Content Stack for a New Business in 2026 — how to choose AI tools when the billing model matters as much as the output.