Azure OpenAI in Foundry Models vs Cohere Chat API (Command models)

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

Cohere Chat API (Command models) 55

Model reading. Bearer keys of two kinds, trial and production. Team roles are Owner and User, only Owners delete production keys, and a production key is shown in full once. No scopes, expiry or per-model restriction was found (18 of 30). Paying customers can switch training off under Data Controls, which implies it is on until they do, trial keys fall under the website terms, and the SaaS agreement grants an irrevocable right to use API data to improve the services and share it with third parties (8 of 20). Logged prompts and generations are deleted after 30 days unless flagged, and zero data retention needs approval (12 of 15). The dashboard shows usage history, and no customer audit log was found (2 of 15). The trust centre lists SOC 2 Type II, ISO 27001, ISO 42001, UK Cyber Essentials, penetration tests on request and a responsible disclosure policy with a bug bounty, per the 9 October check. cohere.com/.well-known/security.txt still answers 404 on 2 November and no public advisories were found, so the line takes 15, as cohere-embed and cohere-north read the same programme (15 of 20).

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.

Cohere Chat API (Command models) 72

Model reading. Function calling with tool_choice REQUIRED or NONE and strict_tools, which the reference marks beta (17 of 20). response_format takes json_object or a JSON Schema, with limits documented and no support in RAG mode (13 of 15). The usage object reports cached_tokens, and no guide or price for prompt caching was found (5 of 15). Context is 256,000 tokens on Command A and Command A Reasoning and 128,000 on Command A+ (10 of 15). /v2/batches runs a batch from an uploaded dataset, with no price or discount found (6 of 10). Official SDKs for Python, TypeScript, Java and Go (10). Error messages are specific and readable, with no stable error codes (11 of 15).

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

Cohere Chat API (Command models) 35

No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (0). The docs say Command models are billed per input and output token. The pricing page, read on 2 November 2026, now carries per-unit prices in its own page data, Command R at $0.15 input and $0.60 output and Command R7B at $0.0375 and $0.15 per million tokens, with Command R+ 08-2024 at $2.50 and $10.00 among legacy prices and Command A+ shown as free. No price is published for Command A, Reasoning, Vision or Translate, so the line takes 15 rather than the full 20 (15 of 20). A trial key is created at sign-up and is free with no card (20). Sign-up is in a browser, and a production key needs an Owner to complete a Go to Production form (0).

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

Cohere Chat API (Command models) 72

Model reading. The last dated release on the Chat endpoint is still North Small Translate on 9 September 2026, 54 days before this check. The last Command model is Command A+ on 20 May 2026. Rerank 5 (21 October) and Embed 5 (30 September) aren't chat changes, so we score the 90-day band (20 of 30). The deprecations page defines Active, Legacy, Deprecated and Shutdown and promises email notice, with no minimum notice period (6 of 12). No chat model was retired or announced for retirement in the last 90 days. The newest entry on the page is still two Aya models retired on 4 April 2026 (8 of 8). Dated changelog with four entries since 4 August (27 August, 9 September, 30 September, 21 October), one of them for a chat model (12 of 15). SDK issue replies not sampled (5 of 10). Python SDK 7.2.0 and 7.3.0, TypeScript 8.2.0 (19 October) and 8.3.0, and Go v2.20.0 tagged on 21 October 2026, Java at 1.12.0 (15). The Python SDK is generated from the OpenAPI file and has a CI workflow, whose runs we did not read (6 of 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).

Cohere Chat API (Command models) 67

Hosted lines. status.cohere.com (incident.io) lists each Command model and the endpoints as components (20). Its feed, read on 2 November 2026, shows two incidents in the 90 days from 4 August. 'Multiple Endpoint Disruptions' on 1 September 2026, from 15:41 to 19:47 UTC, degraded the embeddings endpoint, embed-v4.0, two rerank models and command-a-reasoning-08-2025 during a Google Cloud outage, rated minor and partial, and docs loading failed on 5 August. Nothing has been posted since 1 September, so minor incidents only (20). Chat limits are published per model, 20 requests a minute and 1,000 calls a month on a trial key and 500 a minute on a production key for Command A, R, R+ and R7B, while the four newest variants say contact sales (12 of 15). The errors page documents 429 with example messages that say to wait and try again later and links to the rate limits, with no Retry-After header, backoff timing or idempotency key, the reading cohere-embed takes of the same page (8 of 15). cohere.com/slo is titled Service Level Objective and its text is script-drawn, so it was unread and scores as absent (0). The v2 chat endpoint is the default docs version, but the sample response on the chat guide still carries is_experimental and the newest models are not open to production keys (7 of 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).

Cohere Chat API (Command models) 75

Closed service under a published SaaS agreement, MIT SDKs, and the docs say Command A+ weights are on Hugging Face under Apache 2.0, which we did not open (15 of 30). The Enterprise Data Commitments (5 December 2025) and the privacy policy (1 May 2026) agree on 30-day retention and a training opt-out. The SaaS agreement (8 April 2025) does not mention the opt-out and grants an irrevocable right to use and share API data, and the DPA is sent on request (16 of 30). Deprecations page with dated history back to 2024 and lifecycle terms, no minimum notice, and nothing newer than 4 April 2026 on 2 November, read at 15 as cohere-embed reads the same page (15 of 20). The trust centre names nine sub-processors with a location for each, all in the US, and Google Cloud US-Central as the data location, read at 20 as cohere-embed reads the same list (20 of 20).