Azure credits and third-party APIs don’t mix. Here is what I learned.

The invoice arrived mid-cycle: roughly $1,600, charged directly to the card on file. My Azure credit balance had barely moved. I’d been running Claude via Azure AI Foundry for a few weeks, assumed the startup credits were absorbing the cost, and never saw a warning that they weren’t.

What you see

Unexpected invoice for approximately $1,600 after deploying Claude via Azure AI Foundry

The charge hits the payment method attached to the subscription, not the credit balance. The credit balance stays intact. If you’re watching that balance as your cost guardrail, you’ll miss this entirely. The invoice line item says Marketplace, not Azure AI or anything that maps to what you deployed.

No on-screen distinction between credit-covered and Marketplace-billed models at deployment

Azure AI Foundry presents Claude alongside GPT-4 and other native Azure OpenAI models with no visual separation. The deployment flow for Claude shows no Marketplace label, no credit-eligibility warning, and no billing confirmation prompt. It looks like any other model deployment.

Billing alert fires after the charge clears, not before the session starts

A billing alert configured against total spend will not catch this in time. Marketplace charges accumulate separately from Azure-native spend and only surface when the invoice closes. The alert fires after the fact.

Cost Management dashboard attributes the charge to a Marketplace line item, not an Azure service

Open Cost Management and look at the charge type column. Marketplace charges appear as “Marketplace”, not “Usage”. If you haven’t filtered by charge type before, that distinction is easy to miss.

Microsoft support redirects to Anthropic; Anthropic redirects back to Microsoft

Neither side owns the problem cleanly. Microsoft’s position is that Marketplace vendor charges are between you and the publisher. Anthropic’s position is that billing on the Azure side is Microsoft’s domain. The ticket goes in circles.

Where it happens

Azure AI Foundry model catalogue mixes native Azure models and third-party Marketplace listings without visual separation

Azure OpenAI Service models, published by Microsoft, route through standard Azure billing and are covered by startup credits. Claude models, published by Anthropic, sit in the “Models from Partners and Community” section. That section label is the only signal, and it’s easy to overlook when you’re focused on capability and context window rather than publisher metadata.

The deployment flow for Claude shows no Marketplace label, no credit-eligibility warning, and no billing confirmation prompt

Deploying Claude through Foundry feels identical to deploying GPT-4o. There’s no interstitial screen, no terms acknowledgement specific to Marketplace billing, and no indicator that the charge will bypass your credit balance entirely.

Azure Credits for Start-ups terms exclude third-party branded products and Marketplace purchases, but this exclusion is buried in documentation rather than surfaced in the UI

The exclusion clause in the Azure Credits for Start-ups terms reads: “Startup credits cannot be used for Microsoft Azure support plans, third-party branded products, products sold through Microsoft Azure Marketplace, or products otherwise sold separately from Microsoft Azure.” That’s the policy. It’s accurate. It’s just not shown at the point where the spending decision happens.

Billing alerts configured against total spend do not distinguish Marketplace charges from Azure-native spend

A standard billing alert watches total spend on the subscription. Marketplace charges accumulate in a separate pipeline and won’t trigger a total-spend alert until the combined amount crosses your threshold. By that point, the charge has already cleared.

Find the cause

Confirm the model publisher in Azure AI Foundry

In the Foundry model catalogue, open the model card for the deployed model and check the Publisher field. If the publisher is Anthropic, the model routes through Azure Marketplace billing, not the standard Azure billing pipeline. Microsoft-published models show Microsoft as the publisher and are covered by startup credits. This is the root of the billing split.

Pull the invoice breakdown in Cost Management and filter by Charge Type

In Cost Management, go to Cost Analysis, set the scope to your subscription, and add a filter for Charge Type. Separate “Marketplace” entries from “Usage” entries. The Marketplace entries are the vendor API charges that credits cannot cover. The dollar amount next to those entries is what you owe regardless of your credit balance.

Cross-reference the Azure Credits for Start-ups exclusion clause against the deployed model’s publisher to confirm credit ineligibility

Pull up the Azure Credits for Start-ups terms and match the exclusion clause against Anthropic’s publisher status in Foundry. Anthropic-published models are third-party branded products sold through Azure Marketplace. They meet every condition in the exclusion clause. Credits do not apply.

Check whether a Microsoft forum moderator answer was the source of the assumption that credits would apply

This is worth doing. A Microsoft Q&A forum moderator initially stated that startup credits would cover Claude charges until the credit balance was exhausted, after which pay-as-you-go rates would apply. That answer was later corrected. If your assumption came from that thread, document the original answer and the correction date. You’ll need it when contacting Anthropic.

Verify that no spend limit or Marketplace purchase restriction was set on the subscription before deployment

Check your subscription’s policies in the Azure portal under Policy > Assignments. If no policy blocked Marketplace purchases before you deployed Claude, there was nothing to stop the charge. That’s a configuration gap to close going forward.

Fix

Block Marketplace purchases at the subscription level using Azure Policy

Go to Policy > Definitions and assign the built-in policy “Not allowed resource types” or use the Marketplace-specific deny policy to block unsanctioned Marketplace purchases at the subscription level. Set the effect to “Deny”. This prevents any new Marketplace deployments from going through if they’re outside your approved list. Test the assignment on a non-production subscription before applying it to your main one.

Set a separate billing alert scoped to Marketplace charge type

In Cost Management, create a budget alert and scope it specifically to Marketplace charges rather than total spend. Set the threshold low, at £50 or less, so it catches activity before it compounds. A Marketplace-specific alert fires independently of your Azure-native spend alert and gives you visibility into vendor API charges as they accumulate.

Before deploying any model in Azure AI Foundry, check the publisher field

This is the simplest check and the one that would have prevented the $1,600 charge. In the Foundry model catalogue, expand the model card before deploying. If the publisher is not Microsoft, treat it as a Marketplace charge that startup credits will not cover. Budget for it separately or choose a Microsoft-published model instead.

Contact Anthropic directly to request a refund review

Raise a support case with Anthropic’s billing team. Include the invoice, the Cost Management export filtered by Marketplace charge type, and a copy of the original Microsoft forum moderator answer that stated credits would apply. The moderator’s answer was later corrected by Microsoft, which is relevant context for a dispute. Anthropic has discretion on refunds for edge cases; the forum post gives you documented grounds to request one.

Tag Marketplace resources explicitly in your resource group

Add a tag such as billing-type: marketplace to any resource group containing Marketplace-sourced deployments. Cost Management can then filter by tag, keeping Marketplace spend separate from credit-covered spend in every report and dashboard you run.

Check it’s fixed

Redeploy a low-volume test request through Azure AI Foundry and confirm the Cost Management charge type

Deploy a single low-volume request using a Microsoft-published model such as GPT-4o and confirm that the Cost Management charge type shows as “Usage”. Then check a Marketplace model and confirm it shows as “Marketplace”. This validates that your Cost Management view is correctly separating the two billing pipelines before you rely on either.

Verify the Marketplace-specific billing alert fires correctly on a small test transaction

Temporarily set the Marketplace billing alert threshold to £1 and run a minimal test request through a Marketplace-billed model. Confirm the alert fires within the expected period, typically within 24 hours given Cost Management’s ingestion delay. Reset the threshold to your intended value after the test completes.

Confirm the Azure Policy assignment blocking unsanctioned Marketplace purchases shows as compliant

In Policy > Compliance, check that the policy assignment targeting your subscription shows as “Compliant” and that no existing Marketplace resources are flagged as non-compliant unless intentionally exempted. A non-compliant state means the policy is reporting but not enforcing; check that the policy effect is set to “Deny”, not “Audit”.

Review the next invoice cycle

When the next invoice closes, check Cost Management for any Marketplace line items. If the policy is enforced correctly and no Marketplace deployments were explicitly approved, the Marketplace section of the invoice should be empty. Any entry there means something slipped through the policy and needs investigating.