Azure OpenAI in Foundry Models vs DeepSeek API

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

DeepSeek API 35

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Model reading. One Bearer key per balance, no scoping found (20 of 30). The privacy policy, last updated 10 February 2026, says personal data is used to train models, with an opt-out by email to privacy@deepseek.com (0 of 20). Data kept for as long as needed to provide the services, with no period stated and no zero-retention route (5 of 15). Per-call logs or audit logs not found (5 of 15). Security programme 5 of 20 (was 0). The www.deepseek.com footer carries a Report Security Issue address, security@deepseek.com, per the 21 October reading used for DeepSeek's open-weight listings and its Search and Fetch API listing. No security.txt (404 on 17 October), disclosure policy, certification or bug bounty found. 20 + 0 + 5 + 5 + 5 = 35.

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

DeepSeek API 46

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Model reading. V4.1 Flash was upgraded to DeepSeek-V4.1-Flash-1017 on 17 October under the same deepseek-flash name and price, posted on the updates page the same day, 19 days before this check (30). Later updates entries are unread. No stated notice policy. deepseek-chat and deepseek-reasoner got three months, announced on 24 April for 24 July. One dated notice with no stated period partly meets the line, and the earlier partial award is held (4 of 12). Model churn covers the V4 Flash retirement on 10 September and the V4 Pro shutdown set for 14 September, announced on 13 August and withdrawn on 10 September. The 24 July shutdown has left the 90-day window. A retirement and a withdrawn shutdown inside it keep churn at the bottom of its range (0 of 8). Dated updates page, and the docs list api-service@deepseek.com and a Discord server for support. We didn't test whether either answers (12 of 15). No official SDKs or SDK repository (0 of 15, 0 of 10). 30 + 4 + 0 + 12 + 0 + 0 = 46.

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

DeepSeek API 49

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). No OpenAPI document and no llms.txt found (0 and 0). API reference covers both the OpenAI and Anthropic formats. The chat completion reference, read on 2 October, describes each parameter with its range and default, such as max_tokens from 1 to 393,216 with 8K by default without thinking, but says little on when not to use one (14 of 20). Strict tool calls are documented, in beta at the /beta base URL, with a JSON Schema subset (object, string, number, integer, boolean, array, enum, anyOf, $ref) where every property must be required. JSON output mode carries no schema guarantee (10 of 15). The error codes page lists seven codes, each with a cause and a fix, but no example bodies (10 of 15). Dated updates page that names model changes (15). 0 + 0 + 14 + 10 + 10 + 15 = 49.

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.

DeepSeek API 70

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calls through both request formats, and the API reference documents tool_choice as none, auto, required or a named function (20 of 20). Strict schema-enforced tool calls in beta, JSON output without a schema guarantee (10 of 15). Disk cache on by default with cheaper hits, per the listing (15). 1M-token context and up to 384K output (15). No batch API documented (0). No official SDKs, you use the OpenAI or Anthropic client (0). Seven error codes with a fix for each, 402 for an empty balance (10 of 15). 20 + 10 + 15 + 15 + 0 + 0 + 10 = 70.

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

DeepSeek API 60

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Status page at status.deepseek.com, run on Flashduty, with per-API components and a readable feed (20). The recorded feed lists 36 incidents from 22 July to 15 October. Four touch only web search, 27 are degraded performance, and five are partial unavailability, one of them (12 October) the web chat only. Of the four that hit the API, 28 July (7 minutes) has left the 90-day window and 2 September lasted 31 minutes. 14 September (18:30 to 21:30 UTC) left the V4.1 Flash API and chat partly unavailable for three hours, and 15 October (00:11 to 05:04 UTC) left the V4 Pro and V4.1 Flash APIs and chat partly unavailable for 4 hours 52 minutes. Two majors in 90 days sit between one (10) and several (0), so 5. 16 October to 5 November is unread and earns nothing beyond the recorded award (5). Concurrency caps published per account, 2,500 on Flash and 500 on V4 Pro, and requests that haven't started inference after 10 minutes are closed (15). The rate-limit and error pages document 429, and advise a brief wait and retry on 500 and 503, with no Retry-After header, backoff schedule or statement that a retried call is safe (10 of 15). No SLA found (0). V4 Pro and V4.1 Flash are GA (10). 20 + 5 + 15 + 10 + 0 + 10 = 60.

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

DeepSeek API 65

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Closed service with clear terms under PRC law. The model weights are published, which doesn't change the hosted service (15). The privacy policy of 10 February 2026 is consistent on training by default and storage in the PRC, but publishes no retention period and no DPA (10 of 30). Dated notices on the updates page, undercut by a shutdown announced and withdrawn within a month and a reroute with no prior entry (10 of 20). Data location disclosed as the PRC, third parties named only by category (10 of 20). 15 + 10 + 10 + 10 = 45.