What Is Azure AI Foundry Pricing? A Plain-English Guide for 2026

Why Your Foundry Bill Looks Nothing Like the Token Price You Calculated

You ran the numbers before launch. Tokens in, tokens out, multiply by the published rate — a tidy monthly estimate you could defend in a budget meeting. Then the first Azure invoice lands, and it's nowhere close.

Part of the confusion starts with the name itself. Azure AI Foundry became Microsoft Foundry on January 1, 2026, but the rebrand didn't change the deeper issue: there is no single "Foundry price." Microsoft's own pricing page is explicit — the platform is free to use and explore, and each service you consume is billed at its own rate, under its own billing model.

That structure is exactly why your spreadsheet fails. Your calculation covers model inference, but inference is only one line item in a stack that quietly accumulates charges underneath it. Practitioner reports describe the pattern bluntly: supporting infrastructure adds 15–40% to monthly bills in private-network enterprise deployments. The most common complaint, echoed across the practitioner community, is some version of "why is my bill double the token cost I calculated?"

The culprits are rarely exotic. They're the ordinary plumbing a production deployment requires:

• Azure AI Search for RAG workloads — typically $150–300/month on its own
• Private endpoints at $8–13/month each, with five or more being common ($40–65/month)
• Blob Storage for data and artifacts at $0.0184/GB/month on the hot tier
• Egress bandwidth at $0.087/GB once you exceed the first 100GB/month

One widely cited cost comparison puts it in concrete terms: a workload of 100M input and 50M output tokens costs roughly $750 on the OpenAI platform directly, but $1,050–$1,350 on Foundry once infrastructure is included. The same token rates, a materially different invoice.

There's also a multiplier effect many teams miss. Evaluation runs bill tokens too — practitioners report that "4M tokens on 20 questions means something is silently multiplying your costs." If your team runs frequent benchmarks, regression tests, or agent evaluations, those costs stack invisibly on top of production traffic.

Is the premium worth it? For workloads that need data residency, private networking, and the unified Azure ecosystem, many enterprises conclude yes. But you can't make that call if the infrastructure line items never appear in your estimate. Model the full stack — tokens plus compute plus plumbing — before you commit to a number.

And if you're building agents on top of Foundry, the same discipline applies downstream: skills and tooling choices affect how many calls your agents make and how many tokens they burn. SkillzBench is building a free directory and MCP connector for exactly that kind of agent tooling — worth a look when planning your stack.

How Foundry Pricing Actually Works: Tokens, Compute, and the 500x Model Spread

There is no single "Foundry price" — and that's the first thing that confounds most budgets. Microsoft states plainly that the Foundry platform itself is free to use and explore, with each service (Foundry Models, Agent Service, Foundry IQ, and others) billed at its own rate. That structure — free platform, per-service consumption — is your starting point.

Two deployment modes drive model costs. Managed Compute gives you dedicated GPU infrastructure (A100, H100, H200, MI300 families) for open-source and custom models, billed per compute hour. Serverless Deployment, by contrast, bills pay-as-you-go per 1M tokens, or through Provisioned Throughput Units (PTUs) with hourly and monthly-reservation tiers — and PTU capacity can flex across multiple models, such as OpenAI and DeepSeek, per Microsoft's models pricing page.

The catalog itself is enormous — 11,000+ models — and pricing varies wildly. Third-party aggregator data from LiteLLM shows list prices spanning roughly $0.06 to $180 per 1M tokens, a ~500x spread. That means model selection, not platform fees, is your single biggest cost lever.

Fine-tuning adds four separate cost components:

• Training, billed per 1M tokens
• Hosting, billed per hour (practitioner reports peg this at ~$120/day regardless of usage, per nOps)
• Input usage per 1M tokens
• Output usage per 1M tokens

At scale, commitment discounts matter more than list prices. Microsoft's Agent pre-purchase plan sells Agent Commit Units (ACUs) upfront in a 1-year metered plan — 20,000 ACUs earns 5% off, 100,000 earns 10%, and 500,000 earns 15% — with one ACU roughly equal to $1 of retail value, usable across Foundry and Copilot Credits. Consulting analysis from EPC Group argues that at Fortune 500 volume, committed-use discounts — not base token rates — are the real differentiator, with Azure offering the most flexible commit structures among the big three clouds.

One critical caveat: Microsoft's official pricing tables are dynamic, and its own disclaimer notes prices are "estimates only" that vary by agreement and exchange rate. Every dollar figure above comes from third-party sources — verify current rates in Microsoft's live pricing calculator before budgeting. If you're building agents on top of Foundry, free agent skills (browseable on SkillzBench's pre-launch directory) can help automate the cost-governance workflows — routing, token caps, per-request estimation — that keep these bills predictable.

Five Ways to Cut Your Foundry Costs Without Killing Performance

Knowing that Foundry's bill is really "per-token plus compute" changes how you save. The biggest wins come from governing the whole workload, not just picking a cheaper model — and the numbers back that up.

First, budget for infrastructure, not just tokens. In private-network enterprise deployments, supporting services like Azure AI Search, private endpoints, storage, and egress reportedly add 15–40% to monthly bills, and practitioners on r/AZURE commonly ask why their bill is double what they calculated from token rates alone. Model those line items — typical figures include $150–300/month for AI Search and $8–13/month per private endpoint — before you commit to any project budget.

Second, start pay-as-you-go, then size PTUs on real data. Practitioner guidance suggests running PAYG for 30–60 days and measuring P95 hourly throughput before committing. Provisioned Throughput Units break even at roughly 60–70% sustained utilization, and at 150–200M+ monthly tokens, reservations can deliver 30–70% savings. Commit too early and you may pay for capacity you don't use.

Third, route work to cheaper models. With a ~500x price spread across Foundry's 11,000+ model catalog, model choice is your single biggest lever. Microsoft's built-in intelligent model routing dynamically selects the best model per task, and analysis of routing simple classification and extraction workloads to smaller models shows 25–30% spend reduction when around 40% of calls fit that profile.

Fourth, cap outputs and use caching and batching. Limiting a 3,500-token response to 500 tokens cuts that request's output cost by 86%, batch APIs run at roughly 50% off with a 24-hour turnaround, and a 30% semantic-cache hit rate means 30% fewer model calls.

Finally, once usage is predictable, consider commitments: Microsoft's Agent pre-purchase plan discounts Agent Commit Units by 5–15% at the 20K/100K/500K tiers, and consulting analysis argues that flexible commit structures — not base token rates — are the real differentiator at enterprise scale.

A practical tip from the field: build a per-request cost estimator that predicts token counts before each API call, so runaway agents get flagged early. Much of this governance — routing rules, token caps, cost checks — can itself be automated with agent skills; SkillzBench is building a free directory where you can browse, verify, and benchmark skills for exactly these workflows, and its free MCP connector will let your agents use them directly. Join the waitlist to get access at launch.

What This Means for Agent Builders — and How Skills Fit In

If you're building agents on Microsoft Foundry, pricing isn't a background detail — it's an architectural decision. Microsoft treats agents as a first-class part of the platform's economics, from the Foundry Agent Service itself to a dedicated agent cost-optimization guide published by the VP of Product Management for Foundry Models.

The reason is simple: agents multiply token consumption in ways single apps don't. The Agent Service provides orchestration, autonomous action, and hosting for open-source frameworks, and Microsoft even sells Agent Commit Units at 5–15% discounts across tiers of 20,000 to 500,000 ACUs, where one ACU equals roughly $1 of retail value (per Microsoft's pricing page).

The quiet budget killer is evaluation. As one practitioner put it, "every eval run bills tokens, and 4M tokens on 20 questions means something is silently multiplying your costs" — a complaint documented in practitioner reports on Foundry bills. Agent loops, retries, and eval suites can quietly push spend far past your napkin math.

The good news is that cost governance is largely automatable. The same levers Microsoft and practitioners recommend can be encoded as rules your agent pipeline enforces on every request:

• Model routing — Foundry's intelligent routing selects the best model per task, and routing simple classification workloads to cheaper models can cut spend 25–30% when 40% of calls qualify.
• Token caps — limiting a 3,500-token response to 500 tokens cut per-request output cost 86% in one documented example ($0.035 to $0.005).
• Per-request cost estimation — middleware that estimates token counts before the API call, with guardrails for large jobs, is a recommended pattern for catching runaway requests.

That last set of guardrails is exactly where agent skills earn their keep. Skills — reusable instruction packages for tools like Claude Code, Codex, and Cursor — can implement routing rules, enforce token limits, and run cost-estimation checks as part of your normal workflow rather than as manual review. Given that published research has found roughly 26% of skills carry at least one vulnerability, sourcing security-scanned ones matters.

SkillzBench is building a free, independent directory of exactly that: every skill version-pinned, license-checked, security-scanned, and benchmarked in a sandbox to measure real performance Lift, plus a free MCP connector so your agents only see the tools you choose. It's in pre-launch with the waitlist open — worth a look before your next eval run quietly doubles your bill.