Head to head · LLM inference · October 2026 research run

Azure OpenAI in Foundry Models vs Gemini 4 Neon

Azure OpenAI in Foundry Models scores 81.2 (A) on agent readiness against Gemini 4 Neon's 65 (B), and leads in 6 of 7 scored categories. Both do llm inference.

Best model APIs and inference for AI agents · All 1185 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 45
  • Agent ergonomics, 98 against 93
  • Security & auth, 95 against 55
  • Transparency & trust, 83 against 73

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

Gemini 4 Neon B

Best for Agents doing complex coding, long tool-heavy sessions and document-heavy knowledge work on the paid Gemini API, where Carbon is slower than needed and Hydrogen falls short.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Paid tier only, so an agent can't start on a free key

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 +40

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

Gemini 4 Neon 55

Model reading for gemini-4-neon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Keys bound to a service account and restricted to the Gemini API, with no scopes and a token accepted in the URL (15 of 30, the platform's deduction). Neon is on the paid tier only, and its pricing row says paid content isn't used to improve Google's products; AI Studio use under a Google AI Pro or Ultra plan falls under terms we didn't read, so 15 of 20, as for Carbon. Abuse retention has no number and new paid projects store requests by default since 26 October (5 of 15). Request logs for billed projects (15). security.txt and a reward programme, no certification naming the API (5 of 20). 15 + 15 + 5 + 15 + 5 = 55.

Reliability Azure OpenAI in Foundry Models +35

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

Gemini 4 Neon 45

Model reading for gemini-4-neon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Status page at aistudio.google.com/status with no readable components or history (10 of 20) and no readable incident record (5 of 30). Rate-limit tiers and spend limits published, per-model limits in AI Studio (5 of 15). Backoff guidance for 429 and 503 and SDK retries (15). No SLA (0). The Gemini API release notes and the Google Cloud model page both call Neon generally available from 18 November 2026 (10). 10 + 5 + 5 + 15 + 0 + 10 = 45.

Transparency & trust Azure OpenAI in Foundry Models +10

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

Gemini 4 Neon 73

Model reading for gemini-4-neon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Closed service with clear terms, SDKs Apache-2.0 (15). Paid-tier data isn't used, abuse retention has no number, and request storage is on by default for new paid projects (20 of 30). Deprecations table, with no date for Neon (15 of 20). Data may be cached anywhere Google has facilities; no subprocessor list checked (5 of 20). A DeepMind model card gives the knowledge cutoff, automated safety results and the Frontier Safety Framework outcome, with the full safety report marked coming soon. Every benchmark figure is Google's own. 15 + 20 + 15 + 5 = 55.

Agent ergonomics Azure OpenAI in Foundry Models +5

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.

Gemini 4 Neon 93

Model reading for gemini-4-neon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Function calling, with forced calls by FunctionCallingConfig on the API (20). Structured output, listed as supported on the model page (13 of 15). Implicit caching on prompts of 4,096 tokens or more with cached input 95% off at a published $0.15, explicit caches not supported (15). 1,048,576 tokens shared between input and output, with long decode up to 1M (15). Batch API supported, half price on the platform; Neon's Batch tab wasn't read (10). Python and JavaScript SDKs (10). Error codes with backoff guidance (10 of 15). 20 + 13 + 15 + 15 + 10 + 10 + 10 = 93.

Score by category

CategoryWeightAzure OpenAI in Foundry ModelsGemini 4 NeonEdge
Reliability16%8045Azure OpenAI in Foundry Models +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8785Azure OpenAI in Foundry Models +2
Agent ergonomics13%9893Azure OpenAI in Foundry Models +5
Security & auth14%9555Azure OpenAI in Foundry Models +40
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8683Azure OpenAI in Foundry Models +3
Transparency & trust7%8373Azure OpenAI in Foundry Models +10
Negative events≤1500
TotalA 81.2/100B 65/100

Facts side by side

FactAzure OpenAI in Foundry ModelsGemini 4 Neon
KindModel APIModel API
VendorMicrosoftGoogle
Hosted endpointhttps://<resource>.openai.azure.com/openai/v1https://generativelanguage.googleapis.com/v1beta
TransportsHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0Closed model, used through the Gemini API and Google's apps under Google's terms
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-262026-11-18
Terms last updatedno date givennot read yet
Privacy policy last updated2026-09-012026-10-01
Customer content may train modelsyesyes
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity454k npm/wknone

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.

Gemini 4 Neon

Google's middle Gemini 4 model, between Hydrogen and Carbon, at $3 and $15 per million tokens with a 1M-token shared budget, four thinking levels, function calling, structured output and implicit caching at 95% off. Paid tier only, sampling parameters are ignored, explicit caching isn't supported, no retirement date is stated, and every benchmark is Google's.

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

Gemini 4 Neon

  1. Call generateContent at https://generativelanguage.googleapis.com/v1beta, or the Interactions API, with model gemini-4-neon and an x-goog-api-key on a billed project
  2. Leave thinking_level at high and try medium for interactive work; reserve xhigh for hard multi-step problems
  3. Don't send temperature, top_p or top_k, and declare tools natively rather than asking for raw-text JSON calls
  4. Return every thought_signature unchanged, and never copy one across parallel functionCall parts
  5. Set background to true with max_output_tokens above 65,536 for long outputs, and allow HTTP timeouts of 15 minutes

Questions

Which is better for AI agents, Azure OpenAI in Foundry Models or Gemini 4 Neon?

Azure OpenAI in Foundry Models scores 81.2 (A) on agent readiness against Gemini 4 Neon's 65 (B), and leads in 6 of 7 scored categories.

Do Azure OpenAI in Foundry Models and Gemini 4 Neon need an API key?

Azure OpenAI in Foundry Models takes an API key or an OAuth sign-in. Gemini 4 Neon needs an API key.

Can an agent call Azure OpenAI in Foundry Models and Gemini 4 Neon without installing anything?

Yes. Azure OpenAI in Foundry Models has a hosted endpoint at https://<resource>.openai.azure.com/openai/v1 and Gemini 4 Neon at https://generativelanguage.googleapis.com/v1beta.

Other comparisons with Azure OpenAI in Foundry Models or Gemini 4 Neon

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.