Azure OpenAI in Foundry Models vs Jais 3

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

Jais 3 31

Read as software the owner runs. No account or key, ungated downloads, and server authentication is the owner's to add (12 of 30). A model that calls whatever tools the operator wires in. The cards rule high-stakes decisions without human oversight out of scope, but nothing in the model or template enforces approval (6 of 20). The template renders tool results in their own tool role, but string results go in as raw text (only non-string content is serialised with tojson), no escaping of special-token sequences in caller or tool text was found, and no injection guidance or results are published (4 of 15). No call log of its own. Visibility depends on the serving stack (5 of 15). Every launch command passes --trust-remote-code, so modeling_k2_horizon.py from the repository runs on the host. We read it and found only torch and transformers imports. No security.txt on ifm.ai (404 on 17 October, not re-read), no security contact on the cards and no safety evaluation found. Since 25 October the cards link a technical report on ifm.ai, which answered a Cloudflare bot check on 4 November, so what it covers is unread (4 of 20). 12 + 6 + 4 + 5 + 4 = 31.

Azure OpenAI in Foundry Models 20

No x402, MPP or L402 (0). Per-1M-token prices are public in the Azure Retail Prices API without a login, while the pricing page fills its table with JavaScript and showed GPT-6 prices as pending on 6 October (20). The quota tiers include a Free tier, but an Azure subscription needs a payment method (0). A person signs up for Azure in a browser and creates a resource and a deployment before the first call (0).

Jais 3 60

Self-hosted rule. Apache-2.0 weights with nothing to buy and no hosted option from the makers (20). Free to run with no card (20). Downloads are ungated and anonymous, so an agent can fetch the weights with no sign-up (20). No payment protocol (0). 20 + 20 + 20 + 0 = 60.

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

Jais 3 54

Read for a model the owner serves. No specification of its own. The contract is the Jinja chat template, which validates tool JSON Schemas (required fields must exist in properties) and rejects unknown options, plus the OpenAI-compatible servers in vLLM and SGLang with the k2_horizon parsers (10 of 25). The cards are Markdown on Hugging Face, and SGLang's docs have an llms.txt, but no llms.txt or Markdown docs from IFM were found and ifm.ai couldn't be read (5 of 10). Each card states intended use, four out-of-scope uses, limitations and per-size serving advice (15 of 20). reasoning_effort and tool_call_format are enums enforced with errors, and tools take JSON Schema. The 375B card describes low as no reasoning and omits medium, which the template accepts, and structured output isn't documented (10 of 15). Python examples for a reasoning call and a tool loop, commands for five runtimes, and named template errors, but no error reference for a served model (11 of 15). No changelog or version scheme. Training-stage branches and public commit history (3 of 15). 10 + 5 + 15 + 10 + 11 + 3 = 54.

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.

Jais 3 65

Model reading of the checklist (tool use, structured output, caching, context, throughput, defaults and SDKs, errors). OpenAI-format tools come back as tool_calls in three selectable wire formats, with a multi-turn loop example. Forced tool_choice and parallel calls aren't documented (15 of 20). JSON mode and schemas only through each runtime's guided decoding, not documented by the makers (5 of 15). Prefix caching is the runtime's, and SGLang's page covers HiCache (7 of 10). 524,288 tokens on five of six models, 131,072 on the 0.9B (14 of 15). Uno adapters claim 2.15 times faster decoding for 0.9B to 32B but need IFM's own engine. SGLang lists n-gram speculative decoding and PD disaggregation. No batch mode of its own (7 of 10). Any OpenAI SDK works against a local server, and the 0.9B to 7B fit one GPU. But the cards ask for high effort and 32,768 output tokens on every request, the template inserts an identity system prompt when none is sent, and earlier assistant turns must carry a string thinking field (8 of 15). The template raises named errors for bad options, string-encoded tool arguments and malformed schemas. Server errors are the runtime's (9 of 15). 15 + 5 + 7 + 14 + 7 + 8 + 9 = 65.

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

Jais 3 48

Read with the local-software lines, since the owner serves the weights. Ungated weights on Hugging Face with stated runtimes (vLLM 0.30.0 or later, SGLang 0.5.20 or later, Transformers validated at 5.15.0, mlx-lm with shipped model code), but every launch command trusts remote code. The GGUF card still says to build llama.cpp from master or wait for a release, though llama.cpp's own tags carry K2 Horizon support from b11454 (6 October 2026) (16 of 20, held). No CI or test suite of the makers' was found, and the code repository is 'coming soon'. SGLang's cookbook reports a validation pass of the tool-call parser on all six checkpoints, and IFM's MLX cards describe conversion checks against the PyTorch code (3 of 25). No crash reports. On 4 November the six main repositories held seven discussions, six of them closed citation updates and one open MoVA-36B-A4B thread from 26 October with no reply yet. Two template fixes for OpenAI-style message history landed on 14 October, before the launch (15 of 25). No changelog or version tags, only public commit messages (2 of 15). Released as named final checkpoints with no preview label, though mlx-lm v0.32.2 still has no K2 Horizon model code of its own (12 of 15). 16 + 3 + 15 + 2 + 12 = 48.

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

Jais 3 55

Apache-2.0 in every card's metadata, with staged training checkpoints as branches and training logs linked on Weights & Biases (not opened). There is no LICENSE file and the code repository is still 'coming soon'. A technical report is linked from 25 October but sits behind a bot check, so its data description is unread (24 of 30). Inputs stay on the owner's hardware because nothing is hosted, but no statement says so and no privacy document governs the weights (15 of 30). No deprecation policy, dated notices or version scheme (0 of 20). Safetensors weights carry no code, and the remote modelling and configuration code we read imports only torch, transformers and huggingface_hub, with no network calls. No telemetry statement (12 of 20). 24 + 15 + 0 + 12 = 51.