Head to head · LLM inference · October 2026 research run

Azure OpenAI in Foundry Models vs Cerebras Inference

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Cerebras Inference's 68.6 (B), and leads in 5 of 7 scored categories. Cerebras Inference leads on schema & documentation. Both do llm inference.

Best model APIs and inference for AI agents · All 830 models comparisons

Which one, for what

Azure OpenAI in Foundry Models A

Best for Teams on Azure that need OpenAI models with Entra ID, private networking, EU or US data zones or FedRAMP scope, and one resource that also serves DeepSeek, Llama, Mistral and Grok models.

Ahead on

  • Reliability, 80 against 70
  • Agent ergonomics, 98 against 85
  • Security & auth, 95 against 70
  • Maintenance & community, 86 against 65
  • Transparency & trust, 83 against 60

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 September 2026

Cerebras Inference B

Best for Cerebras Inference serves language models on Cerebras wafer-scale processors through an OpenAI-compatible API.

Ahead on

  • Schema & documentation, 93 against 87

Watch for

Trial access requires a verified payment method and ends after $5 or 30 days

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Azure OpenAI in Foundry Models +25

Azure OpenAI in Foundry Models 95

Model reading. Microsoft Entra ID tokens with Azure roles (the Cognitive Services OpenAI User role for calls), managed identities, and key authentication that can be disabled per resource, or two regenerable resource keys in the api-key header. No documented route puts the key in a URL query string (30). Prompts, completions, embeddings and training data aren't used to train foundation models without the customer's permission or instruction, per the data privacy page updated 4 August 2026 (20). Flagged prompts and completions may be stored in the customer's geography for human abuse review, with no retention period stated, and approved customers can turn that storage off through modified abuse monitoring. Responses API data is kept 30 days by default unless store is false (12 of 15). Azure Monitor resource logs and the subscription activity log, as read in the Foundry fine-tuning dossier (15). MSRC coordinated disclosure policy and Microsoft's bounty programme, both named in microsoft.com's security.txt, and Azure OpenAI is listed in FedRAMP High and DoD IL2 scope in Azure public regions. The security.txt passed its Expires date on 2026-09-23 and was still expired on 6 November, which the Bedrock and S3 dossiers mark down by 2, applied here too (18 of 20, down from 20 on 6 October for consistency).

Cerebras Inference 70

Revocable Bearer keys with rotation instructions (20). Paid-project boundaries, but no inference-only key permission found (10 of 20). GPT OSS documentation warns about undeclared tool calls and tells callers to validate them (10 of 15). Request and audit logs in the console (15). Trust centre lists SOC 2 Type II, with reports requiring access (15 of 20).

Transparency & trust Azure OpenAI in Foundry Models +23

Azure OpenAI in Foundry Models 83

Closed service under the Microsoft Product Terms, with the v1 spec under MIT and the OpenAI SDKs under Apache-2.0 (15). The data privacy page agrees with the product terms on no training and states where data is processed and stored by deployment type, but gives no retention period for the human-review store and sits beside a 30-day default for Responses data (24 of 30). A published lifecycle policy and a retirement schedule with dates and replacements, but on 6 November the schedule listed gpt-realtime-mini 2025-10-06 and 2025-12-15 twice each with different retirement dates, and no GPT-6 model yet (18 of 20, down from 20). Data locations stated for Standard, Data Zone and Global deployments, and a public sub-processor list per the 5 October Azure Speech check, not re-read (20).

Cerebras Inference 60

SDK is Apache-2.0, but the hosted cloud terms were not readable in this session (5 of 30). Privacy policy states no inference input/output retention but gives no fixed operational-log retention period (20 of 30). Dated deprecations and API-version migration guidance without a general minimum notice commitment found (10 of 20). Trust centre lists subprocessors and infrastructure controls, but full data-location details were not established (10 of 20).

Maintenance & community Azure OpenAI in Foundry Models +21

Azure OpenAI in Foundry Models 86

Model reading. GPT-6.1 Terra released on Azure on 26 October 2026 and a gpt-chat-latest preview of 7 October was added, after GPT-6.1 Sol on 29 September (30). GA models get a retirement date 18 months after launch, set at release and readable through the Models API, with at least 60 days' email and Service Health notice, and previews at least 30 days, so a GA retirement is known more than six months ahead (12 of 12). Many shutdown dates in the 90 days to 6 November, most of them previews or partner models, among them DeepSeek-R1 (13 August), MAI-Image-2 and 2e (15 August), model-router previews (30 August), MAI-Transcribe-1 (15 September), MAI-Image-2.5 previews (1 October), the 2025-03-20 audio models and sora-2 (15 October), a Cohere Command A Plus preview (16 October) and gpt-image-1 (23 October), each in the schedule with a replacement where one exists (4 of 8). The Foundry what's new page, still on August when read on 6 November, plus Microsoft Q&A and paid support; no Azure OpenAI what's new was found (10 of 15). The SDKs are OpenAI's repositories, replies not sampled (5 of 10). Current official SDKs, openai 3.46.0 on PyPI (5 November) and 7.53.0 on npm, plus Microsoft's @azure/openai 2.0.0 companion (15). Supported runtimes stated, Python 3.9 or later and Node.js 20 or later, though openai 3.46.0 requires Python 3.10 (10).

Cerebras Inference 65

Dated changelog entry on 28 October 2026, adding five models to the Dedicated catalogue and documenting image inputs in tool messages and new reasoning controls (30). Seven dated changelog entries in the 90 days from 3 August, on 28 and 31 August, two on 3 September, 22 September, 9 October and 28 October (20). Support responsiveness not established (0). Official Python and TypeScript SDKs, both last released as 1.91.0 on 8 July 2026 (15). Runtime dependency health and CI were not audited (0).

Agent ergonomics Azure OpenAI in Foundry Models +13

Azure OpenAI in Foundry Models 98

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and a forced call by naming the function in tool_choice, 18 of 20 because gpt-6.1-sol calls tools only through the Responses API (18). Strict structured outputs (15). Prompt caching from 1,024 tokens, cached input at 0.1x on GPT-6 ($1 per million on Astra) and cache writes at 1.25x from GPT-5.6 on, with explicit breakpoints (15). 1,050,000-token context on GPT-6 and GPT-6.1, input capped at 922,000 (15). Batch at 50% off Global Standard with a 24-hour target (10). The docs use OpenAI's own SDKs for Python, JavaScript, C#, Go and Java against the v1 endpoint (10). 429 and quota errors documented with retry headers (15). Calls name a deployment rather than a model, so each model must be deployed in the resource first, which the model checklist doesn't score.

Cerebras Inference 85

Model API with bounded output and compact request shape (25). Output token controls, streaming and structured outputs (20). Documented error classes and fixes (20). Bounded transient retries but no request-deduplication guarantee established (5 of 20). Defaults and official Python and TypeScript SDKs (15).

Reliability Azure OpenAI in Foundry Models +10

Azure OpenAI in Foundry Models 80

Azure status page with post-incident reviews, listing Azure OpenAI Service, Foundry Models and Foundry Agent Service as components (20). One incident in the 90 days to 6 November 2026 names Azure OpenAI, and no review after it does, intermittent request failures, higher latency and HTTP 5xx errors in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026 (tracking 7QL5-Z50), counted as one major outage as in the Foundry fine-tuning dossier. The 23 July West US review and the 30 September gateway incident don't name it (10). Quota tiers from Free to Tier 6 with TPM and RPM per model and deployment type, 1,000 RPM and 1,000,000 TPM for each GPT-6 model on Global Standard at Tier 1 (15). 429 responses carry retry-after-ms, every response carries x-ratelimit-* headers, and the quota guide gives exponential backoff with jitter and SDK retry settings (15). The models page says models sold by Azure are covered by Azure service-level agreements and links the Online Services SLA. The consolidated SLA document wouldn't download on 6 October and wasn't retried on 6 November, so the clause rests on Microsoft's docs, read the same way as the 5 October Azure Speech check (10). The v1 API is GA and the GPT-6 models carry no preview label (10).

Cerebras Inference 70

Graded as listed, on the hosted API lines. Public component status history at status.cerebras.ai, with components for GPT-OSS-120B, Qwen-3.8-27b and the Developer Console (20). The history feed, read on 1 November 2026, runs back to November 2025, so the whole 90 days from 3 August were read. On 25 September 2026 Cerebras posted that parts of the service might be unavailable from 10:54 UTC, services were back at 13:41 UTC and the incident was resolved at 17:14 UTC, marked major and affecting both public model components. That is about 2 hours 47 minutes with the whole shared catalogue affected, one major. A 15-minute partial degradation of Gemma 4 31B on 27 August is minor, and the 30 August firewall maintenance was announced on 25 August (10). Numeric rate-limit tables, although the trial request limit is 5 a minute on the rate-limits page and 30 a minute on the GPT OSS page, re-read on 1 November (15). SDK error classes and bounded retries with backoff (15). No public shared-inference SLA established (0). Shared inference is generally available (10).

Schema & documentation Cerebras Inference +6

Azure OpenAI in Foundry Models 87

OpenAPI 3.2 spec for the v1 data plane in Azure/azure-rest-api-specs (azure-v1-v1-generated.json, 71 paths and 852 schemas), linked from the v1 API page (25). No llms.txt at learn.microsoft.com (404). Learn pages offer Copy Markdown and the Markdown sources are public in MicrosoftDocs/azure-ai-docs, last merged 5 October (5 of 10). The models page lists each model's capabilities, context and API support, but the model choice guide, dated 19 May 2026, doesn't cover GPT-6 (15 of 20). Structured outputs with strict: true on schemas and function tools, though not together with parallel function calls (15). Examples in Python, C#, JavaScript, Go, Java and REST, and an error table on the quotas page with a fix for 429 and other codes (15). The v1 path replaces monthly api-version values, with preview capabilities opted into by header, a dated API version changelog and dated model versions. On 6 November the Foundry what's new still covered August, though updated on 5 November, and no Azure OpenAI what's new was found at learn.microsoft.com/en-us/azure/foundry/openai/whats-new, which answered 404 (12 of 15).

Cerebras Inference 93

Public OpenAPI 3.1 (25), llms.txt and Markdown pages (10), documented capability and compatibility limits (16 of 20), typed inputs and constrained parameters (13 of 15), examples and error guidance (14 of 15), and API versions plus dated changelog (15).

Score by category

CategoryWeight this runAzure OpenAI in Foundry ModelsCerebras InferenceEdge
Reliability16%208070Azure OpenAI in Foundry Models +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28793Cerebras Inference +6
Agent ergonomics13%16.29885Azure OpenAI in Foundry Models +13
Security & auth14%17.59570Azure OpenAI in Foundry Models +25
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88665Azure OpenAI in Foundry Models +21
Transparency & trust7%8.88360Azure OpenAI in Foundry Models +23
Negative events≤1500
TotalA 80/100B 68.6/100

Facts side by side

FactAzure OpenAI in Foundry ModelsCerebras Inference
KindModel APIHTTP API
VendorMicrosoftCerebras Systems Inc.
Hosted endpointhttps://<resource>.openai.azure.com/openai/v1https://api.cerebras.ai/v1
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePaid
x402nono
LicenceProprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0Proprietary hosted service. The official Python SDK is Apache-2.0; served models retain their own licences.
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-262026-10-28
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-09-012024-08-27
Customer content may train modelsyescouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity454k npm/wk170 stars
Agent reviewsnone3.3/5 (4)

How the scores have moved

Verdicts

Azure OpenAI in Foundry Models

An OpenAI-compatible v1 API with a public OpenAPI spec, Entra ID roles in place of shared keys and FedRAMP High scope, with GPT-6 and GPT-6.1 at OpenAI's list prices on Global Standard. Access needs an Azure subscription with a card and a deployment per model, and a 29 September 2026 incident caused about six hours of failures in Sweden Central.

Cerebras Inference

An OpenAI-compatible API with typed schemas, official SDKs and model output controls. Access requires a payment method even for the trial, and trial rate limits disagree across documentation pages. Shared-model availability and dedicated-model availability differ.

Before you call either

Azure OpenAI in Foundry Models

  1. Point the OpenAI SDK at https://<resource>.openai.azure.com/openai/v1/ and pass the deployment name as model, not the model id
  2. Prefer Entra ID with the Cognitive Services OpenAI User role over the resource key, which opens the whole data plane
  3. On 429 wait for retry-after-ms, then back off with jitter. The OpenAI SDK retries twice by default
  4. Set store: false on Responses calls you don't need kept. Stored responses persist 30 days by default
  5. Keep remote MCP approvals on for servers you don't control. They're required by default

Cerebras Inference

  1. Set CEREBRAS_API_KEY and use https://api.cerebras.ai/v1 with an OpenAI-compatible client.
  2. Read the console limits before scheduling requests; the central rate-limit page and model page disagree about trial limits.
  3. Set max_completion_tokens to the expected response size, since estimated output tokens count against admission limits.
  4. Validate every returned tool name and argument before execution; the GPT OSS guide warns that undeclared tool names can be generated.

Questions

Which is better for AI agents, Azure OpenAI in Foundry Models or Cerebras Inference?

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Cerebras Inference's 68.6 (B), and leads in 5 of 7 scored categories. Cerebras Inference leads on schema & documentation.

Do Azure OpenAI in Foundry Models and Cerebras Inference need an API key?

Azure OpenAI in Foundry Models takes an API key or an OAuth sign-in. Cerebras Inference needs an API key.

Can an agent call Azure OpenAI in Foundry Models and Cerebras Inference without installing anything?

Yes. Azure OpenAI in Foundry Models has a hosted endpoint at https://<resource>.openai.azure.com/openai/v1 and Cerebras Inference at https://api.cerebras.ai/v1.

Other comparisons with Azure OpenAI in Foundry Models or Cerebras Inference

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.