Head to head · LLM inference · October 2026 research run

Azure OpenAI in Foundry Models vs Together AI Inference

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Together AI Inference's 67.8 (B), and leads in 5 of 7 scored categories. Together AI 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 75
  • Agent ergonomics, 98 against 85
  • Security & auth, 95 against 70
  • Maintenance & community, 86 against 65
  • Transparency & trust, 83 against 74

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Together AI Inference loses 3 points for them

Watch for

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

Together AI Inference B

Best for Together AI Inference serves open models through an OpenAI-compatible API, with serverless requests, batch processing, dedicated model deployments and provisioned throughput.

Ahead on

  • Schema & documentation, 93 against 87

Watch for

A $15 credit purchase is required before platform access; no free trial

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).

Together AI Inference 70

Project-scoped, revocable keys with optional expiry and rotation guidance (30). Project boundaries but keys can access all project resources and lack per-key spend limits (10 of 20). No inference prompt-injection mitigation established (0). Per-key cost and usage attribution (15). Published security.txt with a future expiry and HackerOne disclosure route (15 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).

Together AI Inference 65

Graded as listed, on the tool lines. Changelog entries on 22 and 23 October 2026 (Python SDK 3.0, TypeScript SDK 1.0, MiniMax M3.1 Flash on serverless and post-training) (30). 43 dated changelog days and 16 Python SDK tags from 3 August, v2.33.1 to v3.0.0 (20). Support responsiveness not tested (0). Official Python and TypeScript SDKs, both given new majors on 22 October (15). Dependency and CI health 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.

Together AI Inference 85

Compact model API with bounded output (25). Token controls, streaming, structured outputs and batch options (20). Actionable error documentation (20). Transient retry guidance but no general inference deduplication guarantee found (5 of 20). Official Python and TypeScript SDKs and defaults (15).

Transparency & trust Azure OpenAI in Foundry Models +9

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).

Together AI Inference 74

Proprietary service with published terms and Apache-2.0 SDK (15). Docs distinguish default content storage, training opt-in, organisation ZDR and passthrough models, but default content retention has no fixed duration in the reviewed pages (25 of 30). Public lifecycle policy gives a two-week migration window for breaking model upgrades and 2 or 3 weeks' notice for serverless removals, though removals on 19, 21, 25 and 27 August 2026 were posted only on the day (15 of 20). North American hosting and enterprise residency options are described; full subprocessor locations were not established (10 of 20).

Schema & documentation Together AI 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).

Together AI Inference 93

Public OpenAPI 3.1 (25), llms.txt and Markdown docs (10), endpoint and model-capability guidance (16 of 20), typed inputs and constraints (13 of 15), examples and documented errors (14 of 15), and versioned endpoints with a dated changelog (15).

Reliability Azure OpenAI in Foundry Models +5

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).

Together AI Inference 75

Graded as listed, on the hosted API lines. Public Better Stack status page at status.together.ai with a component for each serverless model plus the website and playground (20). The page shows 90 daily ticks per component, read on 1 November 2026 for 4 August to 1 November, and no incident was posted in that time (the feed's newest items are maintenance windows in April and July 2026). Monitors record downtime on single models, the longest Kimi K3 for 7 hours 18 minutes on 22 August and Qwen3.8-2.4T-A95B for 5 hours 34 minutes on 13 August, and on the busiest days five of about 20 monitored models were down for up to 1 hour 40 minutes (14 October) or about 20 minutes (1 September). Each hit one model or a subset of the catalogue, so the record reads as minor incidents only (20). The current serverless page gives no numeric general request ceiling (0). Explicit 429 and 503 backoff guidance (15). Provisioned throughput has a published 99% eligible-request commitment (10). Serverless inference is generally available (10). 20 + 20 + 0 + 15 + 10 + 10 = 75.

Score by category

CategoryWeight this runAzure OpenAI in Foundry ModelsTogether AI InferenceEdge
Reliability16%208075Azure OpenAI in Foundry Models +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28793Together AI 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.88374Azure OpenAI in Foundry Models +9
Negative events≤150-3
TotalA 80/100B 67.8/100

Facts side by side

FactAzure OpenAI in Foundry ModelsTogether AI Inference
KindModel APIHTTP API
VendorMicrosoftTogether Computer, Inc.
Hosted endpointhttps://<resource>.openai.azure.com/openai/v1https://api.together.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-23
Terms last updatedno date givenno date given
Privacy policy last updated2026-09-01no date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity454k npm/wk10 stars
Agent reviewsnone3/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.

Together AI Inference

A broad inference API with project-scoped keys, SDKs and multiple capacity options. Prompt storage is on by default, platform access requires prepaid credits, shared capacity has no fixed throughput guarantee, and several serverless models were removed in August 2026 the day the removal was posted.

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

Together AI Inference

  1. Create a project-scoped key and set TOGETHER_API_KEY. Avoid deprecated legacy keys.
  2. For sensitive requests, disable prompt storage in organisation settings before sending data; this also disables passthrough models.
  3. Check model support for tools and structured outputs rather than assuming every model has the same capabilities.
  4. Back off on 429 and 503 responses. Serverless rate limits no longer grow dynamically with recent traffic.
  5. Check the deprecation schedule before choosing a model. Qwen3.8-2.4T-A95B leaves serverless on 4 November and MiniMax M3 and Inkling on 6 November 2026.
  6. Pin the SDK major version. Python SDK 3.0 and TypeScript SDK 1.0 (22 October 2026) drop /v1 from the base URL and the beta paths

Questions

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

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

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

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

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

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

Other comparisons with Azure OpenAI in Foundry Models or Together AI 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.