Azure AI Foundry Pricing 2026: Full Cost Breakdown (Now Microsoft Foundry)

Microsoft Foundry (formerly Azure AI Foundry until January 1, 2026) pricing operates on a pay-as-you-go token model for most deployments, with provisioned throughput units (PTUs) available for high-volume production workloads. The platform charges per-token costs for model inference, plus separate line items for Azure AI Search, Blob Storage, private endpoints, and networking egress.

Unlike platform.openai.com, which primarily bills for API usage, Microsoft Foundry can add 15-40% to your monthly bill through supporting Azure infrastructure in private-network enterprise deployments.

This guide covers current per-token pricing for GPT, Llama, DeepSeek, Grok, and Claude models on Microsoft Foundry, explains when to use pay-as-you-go versus provisioned throughput with break-even calculations, and documents the hidden infrastructure costs practitioners encounter when moving from evaluation to production.

Has Azure AI Foundry Been Renamed?

Yes. Microsoft renamed Azure AI Foundry to Microsoft Foundry, effective January 1, 2026. The rebrand was announced at Microsoft Ignite on November 18, 2025 and formalized in the January 2026 Product Terms.

The platform name, official documentation URLs, and pricing pages all changed. The official pricing page moved from azure.microsoft.com/pricing/details/ai-foundry/ to azure.microsoft.com/pricing/details/microsoft-foundry/. (This doesn’t impact Azure AI model pricing, deployment types, API endpoints, resource provisioning workflows, and billing structure.)

Microsoft Foundry Pricing: Pay-As-You-Go Token Rates (August 2026)

Microsoft Foundry charges per-token for inference, with separate input and output token rates. Token prices vary by model family, deployment region, and whether you use global-standard or provisioned throughput. The table below shows current pay-as-you-go rates for the most commonly deployed models.

Regional pricing variance: Models deployed in US East, US West 2, and West Europe typically match the global-standard rates above. South Central US, Japan East, and Australia East deployments may cost 10-25% more due to regional data center capacity constraints. Check the official Microsoft Foundry pricing calculator for your specific deployment region.

Fine-tuned models incur a daily hosting charge in addition to per-token inference costs.

Pay-As-You-Go vs Provisioned Throughput: Break-Even Math

Microsoft Foundry offers two pricing models: pay-as-you-go (PAYG) charges per token with variable rate limits, and provisioned throughput units (PTUs) reserve guaranteed capacity at a fixed monthly cost. The decision point: PAYG for spiky, early-stage workloads; PTUs for steady, high-throughput production.

When Pay-As-You-Go Makes Sense

Spiky workloads with unpredictable traffic — If your application sees 10x traffic variance between peak and off-peak (for example, a customer support chatbot handling 1,000 requests per hour during business hours and 100 requests per hour overnight), PAYG avoids paying for unused capacity. You only pay for tokens consumed.

Early-stage applications with unknown usage patterns — During development and early production, traffic volume is unknown. PAYG lets you scale without committing to fixed monthly costs. Practitioners recommend running PAYG for 30-60 days, measuring P95 hourly throughput, then sizing PTUs based on actual demand rather than estimates.

Low-volume inference (under 50 million tokens per month) — Small applications processing 1-2 million tokens per day will never reach PTU break-even. PAYG remains cheaper until sustained throughput crosses the 150-200 million token monthly threshold for GPT-4o or GPT-5 models.

When Provisioned Throughput Makes Sense

Sustained high-throughput workloads — If your application consistently processes 200+ million tokens per month with steady traffic patterns, PTUs deliver 30-70% savings over PAYG. The monthly reservation cost becomes cheaper than per-token charges at scale.

Rate limit intolerance — PAYG deployments enforce hard rate limits (requests per minute and tokens per minute). When you hit the limit, the API returns 429. No queue, no wait. As one Microsoft practitioner notes, "if sustained utilization is above 60-70% of your PTU capacity, monthly reservation already beats PAYGO." PTUs provide reserved throughput and significantly reduce rate-limit variability, although they can still return 429 errors if provisioned capacity is fully consumed.

Production SLA requirements — Enterprises needing guaranteed throughput for customer-facing applications use PTUs to reduce 429 errors during peak load. PAYG rate limits are scoped by subscription, region, model, and deployment type. PTUs provide dedicated capacity.

Break-Even Calculation for GPT-4o and GPT-5

According to Microsoft Community Hub (August 2026): If sustained utilization is above 60-70% of your PTU capacity, monthly reservation already beats PAYGO.

Example: An application processing 10 million tokens per day (300 million per month) with GPT-4o at an 80/20 input-to-output split costs approximately $1,200/month on PAYG: $600 for 240 million input tokens and $600 for 60 million output tokens. At 300 million tokens per month, the workload is well above the 150-200 million monthly token range where PTUs typically begin to make economic sense.

The recommendation is to start with PAYG. After 30 days of production traffic, calculate P95 hourly token consumption. If P95 consistently exceeds 60% of the PTU capacity you would purchase, switch to PTUs. Do not guess at capacity needs — size PTUs based on measured demand, not projected growth.

Why Your Microsoft Foundry Bill Is Higher Than You Expected

The most common practitioner complaint on Reddit r/AZURE: "Why is my Foundry bill double the token cost I calculated?" The answer: Microsoft Foundry automatically provisions supporting infrastructure — Azure AI Search, Blob Storage, private endpoints, and networking resources — that bill separately from model inference.

Hidden Cost 1: Azure AI Search

Microsoft Foundry uses Azure AI Search for vector storage and retrieval when you enable Retrieval-Augmented Generation (RAG) features. Dedicated Azure AI Search services bill based on provisioned Search Units (SUs), while Serverless services bill based on Compute Units consumed plus indexed storage. A typical production RAG application with 10GB of indexed documents and 1,000 queries per day costs $150-300/month for Azure AI Search alone, before any model inference costs.

Hidden Cost 2: Azure Blob Storage

Training data, uploaded documents for RAG, evaluation datasets, and fine-tuning data can be stored in Azure Blob Storage. For customer-managed storage, you create or connect an Azure Storage account to the Foundry resource. Storage costs include:

• Hot tier storage: $0.0184/GB/month for the first 50TB
• Write operations: $0.05 per 10,000 operations
• Read operations: $0.004 per 10,000 operations
• Data retrieval: Free for the Hot tier

A production application with 500GB of training data and 1TB of document embeddings costs approximately $27/month for storage plus transaction fees. This cost persists whether you actively train models or not. Old training datasets and abandoned fine-tuning runs accumulate until manually deleted.

Hidden Cost 3: Private Endpoints

Enterprise deployments disable public network access to Microsoft Foundry resources and use private endpoints for secure connectivity. Each private endpoint costs approximately $8-13/month per endpoint (Team400.ai documentation cites ~$13 AUD/month = $8-9 USD).

A production Microsoft Foundry deployment with private networking typically provisions 5+ private endpoints:

• Microsoft Foundry resource: 1 endpoint
• Azure AI Search: 1 endpoint
• Azure Storage: 1-2 endpoints (one for Blob, one for File if using File Search)
• Azure Cosmos DB (if using agent state persistence): 1 endpoint
• Azure Key Vault (for secrets management): 1 endpoint

The total private endpoint cost: $40-65/month for basic security posture. One Microsoft Community Hub post documents the "hidden reason your Foundry Agent can't reach any of your private resources" — misconfigured private endpoints that also drive unexpected costs.

Hidden Cost 4: Networking and Egress

Data transfer out of Azure (egress) from North America and Europe costs $0.087/GB for the next 10TB after the first 100GB/month when routed through Microsoft's Premium Global Network. Applications serving model responses to external clients, exporting training data to on-premises systems, or replicating embeddings across regions incur egress charges.

Hidden Cost 5: Evaluation Runs Silently Multiplying Token Usage

One common complaint is that "every eval run bills tokens, and 4M tokens on 20 questions means something is silently multiplying your costs." Microsoft Foundry's evaluation libraries run multiple model calls per evaluation question to measure consistency, safety, and groundedness. A single 20-question evaluation can consume millions of tokens if the evaluation framework generates synthetic variations, runs multi-turn dialogues, or checks answers against multiple grounding sources.

Review evaluation job configurations before running in production. Limit synthetic variation count, disable unnecessary evaluation metrics, and run evaluations on smaller model tiers (GPT-4o mini instead of GPT-5 Sol) during development.

Microsoft Foundry vs Platform OpenAI: Why the Price Difference?

Practitioners frequently ask: "Why does Microsoft Foundry cost more than platform.openai.com for the same models?" The answer: Microsoft Foundry includes Azure infrastructure costs, while OpenAI bills only for API calls.

OpenAI platform.openai.com pricing (August 2026):

• GPT-4o: $2.50 input / $10.00 output per 1M tokens
• No separate charges for networking, storage, or infrastructure

Microsoft Foundry pricing (August 2026):

• GPT-4o: $2.50 input / $10.00 output per 1M tokens (same token rate)
• Additional charges: Azure AI Search ($150-300/month), Blob Storage ($20-50/month), private endpoints ($40-65/month), egress ($50-200/month)

Total cost comparison: 1 million API calls consuming 100 million input tokens and 50 million output tokens costs $750 on OpenAI ($250 input + $500 output). The same workload on Microsoft Foundry costs $750 for tokens plus $300-600 for infrastructure, totaling $1,050-1,350. Microsoft Foundry is 40-80% more expensive for workloads that require private networking and enterprise security.

When Microsoft Foundry is worth the premium:

1. Data residency requirements — Regulated industries (healthcare, finance) that cannot send data outside Azure for compliance reasons must use Microsoft Foundry

2. Unified Azure ecosystem — Applications already using Azure Cosmos DB, Azure Functions, and Azure Monitor benefit from single-pane-of-glass observability

3. Private networking — Enterprises with strict network security policies that prohibit public internet access to AI services

Cost Optimization Tips for Microsoft Foundry

For organizations spending $5,000+ per month on Microsoft Foundry, the top strategies for reducing cost include:

1. Start with PAYG, Measure, Then Decide on PTUs

Do not pre-purchase PTUs based on projected traffic. Run PAYG for 30-60 days, measure actual token consumption with proper AI cost attribution, then size PTUs based on P95 hourly demand. Overprovisioned PTUs waste money — you pay for capacity whether you use it or not.

2. Use Model Tiers Strategically

GPT-5.6 Sol costs roughly 30x more for input tokens and 45x more for output tokens than GPT-4o mini ($5/$30 vs $0.165/$0.66). Route simple queries (classification, summarization) to mini models. Reserve premium Azure AI foundry pricing tiers for complex reasoning tasks. Azure OpenAI cost optimization strategies apply equally to Microsoft Foundry deployments.

3. Clean Up Abandoned Fine-Tuned Models

Fine-tuned models cost £95/day ($120 USD) for hosting whether they serve traffic or not. Review deployed fine-tuned models monthly and delete any that are no longer in use. One practitioner on Reddit accumulated $500 in hosting fees for two abandoned models over a single week.

4. Monitor Private Endpoint Count

Each private endpoint costs $8-13/month. Review your network topology quarterly and consolidate endpoints where possible. If two services can share a subnet, they may share a single private endpoint rather than provisioning two.

5. Set Up Azure Cost Monitoring Alerts

Microsoft Foundry costs can spike rapidly due to runaway inference loops or misconfigured evaluation jobs. Configure Azure Cost Management alerts to notify when daily spend exceeds $50 or when monthly spend crosses 110% of budget. Early detection prevents $1,000+ surprise bills.

6. Enable GenAI Cost Attribution Across Cloud and AI Spend

Organizations running multi-cloud or hybrid AI infrastructure need unified visibility. nOps provides AI cost drivers tracking across Azure, AWS Bedrock, and OpenAI API spend, correlating infrastructure costs (VMs, storage, networking) with model inference costs in a single dashboard. This prevents blind spots where you optimize Azure VM costs but miss that 40% of your AI budget goes to underutilized fine-tuned models.

Understand & Reduce Azure Costs with nOps

Platforms like nOps provide unified AI cost drivers visibility across Azure infrastructure and model inference spend, with cloud cost anomaly detection surfacing optimization opportunities that Microsoft's native Azure cost monitoring tools do not expose. nOps includes:

Unified visibility across AI and cloud spend. Get all of your spending from Azure, AWS, GCP and AI tools all in one place, with cost allocation by model, application, customer, or business unit to understand what is driving spend and where optimization will have the greatest impact.

Commitment Management for more savings and less risk.  We implement commitment layering at a granularity no human team can replicate. Customers typically save ~20% by switching to nOps — and with results-based pricing, you pay only when you get better results.

We’ve talked to companies that can save millions on their cloud bills by switching to nOps from competitors. Book a free savings analysis to quantify exactly how much more you can save for no work on your part.

nOps manages $4B+ in cloud spend and was recently rated #1 in G2’s Cloud Cost Management category.

Frequently Asked Questions

Let’s dive into a few FAQ about Azure AI Foundry models pricing.