Claude usage in Microsoft Foundry is eligible for drawdown against Agent Commit Units under the Microsoft Agent Pre-Purchase Plan?

Hello Evgenii Bartenev,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know if Claude usage in Microsoft Foundry is eligible for drawdown against Agent Commit Units under the Microsoft Agent Pre-Purchase Plan?

Claude usage in Microsoft Foundry is not eligible for ACU drawdown. This is because Claude is delivered as a third‑party Marketplace-backed service, and its consumption is billed separately through the Microsoft Marketplace using Anthropic’s pricing model, rather than through Microsoft-metered Foundry usage. - https://platform.claude.com/docs/en/build-with-claude/claude-in-microsoft-foundry

The Microsoft Agent Pre‑Purchase Plan applies only to eligible Microsoft-metered services, such as Microsoft Foundry native models and Copilot Credits-enabled services. It does not extend to third-party Marketplace offerings, even if they are accessible within the Foundry interface. - https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/agent-pre-purchase

Therefore, any usage of Claude models within Foundry will incur separate Marketplace charges and will not consume ACUs, which explains the billing distinction and avoids incorrect cost expectations.

I hope this is helpful! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Hi Evgenii Bartenev,

Yes, Claude usage in Microsoft Foundry is supported, but the billing part can be a bit confusing.

Here is a clear explanation:

Is Claude usage eligible for Azure credits

In most cases, Claude usage is not treated like native Azure services.

• Claude models are provided by Anthropic (a partner), not Microsoft
• Because of this, they are billed through Azure Marketplace and not as first party Azure services [learn.microsoft.com]

That means:

• Azure sponsorship or free credits usually do not apply
• Charges may go directly to your billing method instead of consuming credits [learn.microsoft.com]

How billing actually works

When you use Claude in Foundry:

• Billing follows pay as you go based on token usage
• Pricing comes from Anthropic standard API pricing
• Charges appear under Marketplace billing in Azure [platform.claude.com]

So even though you are using it inside Azure, the billing path is different from Azure OpenAI.

Important requirements to check

Make sure your setup meets these conditions:

• You need a paid Azure subscription with a valid billing method
• Credit only or free subscriptions are not supported for Claude usage [learn.microsoft.com]
• Claude access requires Azure Marketplace enabled on your subscription [learn.microsoft.com]

Also, availability is limited to certain regions.

When Azure credits can be used

Azure credits are typically used only for:

• Azure OpenAI models (like GPT models)
• Microsoft published models

For Claude, credits may only apply in specific enterprise scenarios like certain Azure consumption agreements, but not in standard free or sponsored subscriptions.

Quick way to confirm in your environment

You can check this easily:

• Go to Foundry model catalog
• Look at the Publisher field
• If it shows “Anthropic”, it is billed as partner model
• If it shows “Microsoft”, it uses Azure credits

Reference

• Claude in Microsoft Foundry documentation https://platform.claude.com/docs/en/build-with-claude/claude-in-microsoft-foundry

Summary

• Claude is supported in Foundry
• It is billed via Marketplace as a third-party service
• Azure credits usually do not cover it
• A paid subscription with billing enabled is required

Hope this helps clarify things. Do let me know if you have any further queries.

Thankyou!