# Azure OpenAI in Foundry Models vs SambaCloud (slim)

> Azure OpenAI in Foundry Models scores 80 (A) to SambaCloud's 64.9 (B) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/azure-openai-vs-sambanova.md (~7,650 tokens) · this version ~3,980 tokens · JSON https://www.anchorterminal.com/compare/azure-openai-vs-sambanova.json · canonical https://www.anchorterminal.com/compare/azure-openai-vs-sambanova
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against SambaCloud's 64.9 (B), and leads in 5 of 7 scored categories. SambaCloud leads on reliability and payments & pricing. Both do llm inference.

- Azure OpenAI in Foundry Models: A 80, rank #14 of 1486 · https://www.anchorterminal.com/tools/azure-openai.min.md
- SambaCloud: B 64.9, rank #444 of 1486 · https://www.anchorterminal.com/tools/sambanova.min.md
- Azure OpenAI in Foundry Models, good 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 Schema & documentation, 87 against 81; Agent ergonomics, 98 against 67; Security & auth, 95 against 61; Maintenance & community, 86 against 77; Transparency & trust, 83 against 73. Also Agent-ready, a grade of BB or better; No incidents deducted, where SambaCloud loses 5 points for them.
- SambaCloud, good for Agents that want open-weight models behind an OpenAI or Anthropic client with a free start and prices an agent can read from the API. Ahead on Reliability, 85 against 80; Payments & pricing, 40 against 20. Also Free to start without a card.

| Category | Azure OpenAI in Foundry Models | SambaCloud |
| --- | --- | --- |
| Reliability (16%) | 80 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 81 |
| Agent ergonomics (13%) | 98 | 67 |
| Security & auth (14%) | 95 | 61 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 86 | 77 |
| Transparency & trust (7%) | 83 | 73 |

| Fact (where they differ) | Azure OpenAI in Foundry Models | SambaCloud |
| --- | --- | --- |
| Vendor | Microsoft | SambaNova Systems, Inc. |
| Hosted endpoint | `https://<resource>.openai.azure.com/openai/v1` | `https://api.sambanova.ai/v1` |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Licence | Proprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0 | Proprietary service under the SambaCloud Terms of Service. The SDKs and the OpenAPI document are Apache-2.0 |
| llms.txt | no | yes |
| Last release | 2026-10-26 | 2026-10-27 |
| Privacy policy last updated | 2026-09-01 | 2023-05-27 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Popularity | 454k npm/wk | 2 stars, 76 npm/wk, 6.1k PyPI/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Security & auth, Azure OpenAI in Foundry Models +34: 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).); SambaCloud 61 (Model reading. Bearer keys from the console, up to 25 per user and shown once. No scopes, project limits or rotation guidance were found, and the key travels in a header, never in the URL (18 of 30). The terms let SambaNova access, store and process Customer Content solely to supply the service and for no other purposes, which rules out training without naming it (18 of 20). The DPA's Annex I, read on 1 November, keeps prompts, inputs and completions no more than 30 days for security, fraud and abuse monitoring. No zero-retention option was found in the pages read, and the product page says SambaCloud never sees or collects prompts, against that retention and terms that grant a right to store content and to use query logs (10 of 15, between deepseek-api's 5 and siliconflow's 6 with no period stated and the 15 groq, mistral-api and xai-api take for 30 days with a zero-retention route). The console has a Usage page. No request logs or audit log were found in the docs (5 of 15). The trust centre states SOC 2 Type 2 and ISO 27001. No security.txt, disclosure policy or bug bounty was found, and the SDK's SECURITY.md sends service reports to a general address (10 of 20).)
- Agent ergonomics, Azure OpenAI in Foundry Models +31: 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.); SambaCloud 67 (Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with `tool_choice` to force a function, on six listed models, and a July 2026 fix for tool calls that were buffered when streaming (17 of 20). `json_object` and `json_schema` output, best effort only, with a known failure on DeepSeek-V3.2 recorded in July 2026 (8 of 15). Automatic prompt caching on the MiniMax models only, with cached input on MiniMax-M3.1-Flash at a tenth of the input price on the 1 November pricing page, a 4,096-token minimum and no guaranteed persistence (10 of 15). 131,072-token context on four of six models, 1M on the MiniMax-M3 preview, and output capped at 7,168 tokens on DeepSeek and 3,072 on Llama 3.3 70B (8 of 15). No batch API found in the docs index or the OpenAPI document (0 of 10). Official SDKs for Python and TypeScript, and the OpenAI and Anthropic clients work with a changed base URL (10). Errors carry `type`, `param`, `code` and `request_id` (14 of 15).)
- Payments & pricing, SambaCloud +20: 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).); SambaCloud 40 (No machine payment protocol (0). Per-token prices on the pricing page, read without a login on 1 November, such as gpt-oss-120b at $0.22 in and $0.59 out per 1M tokens (20). Free tier with no payment method, per the 8 October check (20). A person signs up in the console to get a key (0).)
- 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).); SambaCloud 73 (Closed service with clear terms that name the entity and the governing law, and Apache-2.0 SDKs and OpenAPI document (15). The privacy policy is still dated 27 May 2023 and doesn't name SambaCloud or API inputs. A Data Processing Addendum, part of the Terms of Service, is now linked from the legal page (undated). It limits processing of customer personal data to the agreement, its Annex I says prompts, inputs and completions are processed transiently and kept no more than 30 days for security, fraud and abuse monitoring, then deleted, and it deletes customer personal data within 30 days of termination and from backups within 90. The product page's claim, re-read on 1 November, that SambaCloud 'never sees or collects any of your data or user prompts' sits beside that 30-day retention and terms that allow storing content and using query logs (16 of 30, as novita-ai's stated retention periods, below mistral-api's 18 where the DPA and other pages agree). A deprecations page with notice and removal dates back to April 2025, recording MiniMax-M2.7's 1 October removal with a 1 September notice per the 27 October read, though nothing for Mistral Large 3, per the 8 October check (14 of 20). The DPA's Annex III names 24 sub-processors with purpose and location (USA, Japan, Germany, the United Kingdom, Australia) and promises 30 days' notice of changes, though it doesn't say where inference runs for a given request (18 of 20). 15+16+14+18 = 63.)
- Maintenance & community, Azure OpenAI in Foundry Models +9: 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).); SambaCloud 77 (Model reading. The OpenAPI document and both SDKs (Python 1.14.0, TypeScript 1.11.0) were updated on 27 October 2026, adding `MiniMax-M3.1-Flash`, which is on the pricing page on 1 November (30). Production models get a notice of at least two to three weeks. The recorded removals to June had 14 days or less, and MiniMax-M2.7's removal from SambaCloud on 1 October was announced on 1 September (30 days), per the 27 October read of the deprecations page (5 of 12). One removal in the window from 3 August (MiniMax-M2.7) after 13 model ids left between 9 March and 9 June 2026 (4 of 8). The SambaCloud release notes stopped at 7 July 2026 on 8 October and couldn't be re-read. The community forum had staff replies, per the 8 October check (10 of 15). The Python SDK repository holds release pull requests only, so replies could not be judged (5 of 10). Python 1.14.0 and TypeScript 1.11.0, both 27 October 2026 (15). CI, release-please, a lock file and gitleaks scanning (8 of 10). 30+5+4+10+5+15+8 = 77.)
- Schema & documentation, Azure OpenAI in Foundry Models +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).); SambaCloud 81 (Public OpenAPI 3.1.1 document, still labelled version 1.2.0 though its content changed on 27 October 2026, with 10 operations and 165 schemas (25). `llms.txt` at docs.sambanova.ai/docs/llms.txt and a Markdown copy of each page, per the 8 October check (docs.sambanova.ai answered robots.txt with a bot check on 1 November, so it wasn't read) (10). 718 descriptions in the document, with pages for function calling, Responses, Messages and caching. When not to use a route is rarely stated (15 of 20). Typed parameters with 150 enums, and request bodies now declare `additionalProperties: false`, but JSON schema output is best effort and `strict: true` has no effect (10 of 15). Code examples in Python and TypeScript, and an errors page with 13 codes and a recovery suggestion for each, per the 8 October check (13 of 15). The spec is versioned in its repository, but the version label didn't move with the 27 October changes, the newest SambaCloud release note seen is 7 July 2026, and the models page disagreed with `/v1/models` on 8 October (8 of 15). 25+10+15+10+13+8 = 81.)

| Task | Azure OpenAI in Foundry Models | SambaCloud |
| --- | --- | --- |
| Research a product and write a sourced report | $110 | $2.39 |
| Build a small four-page website | $25.07 | $0.53 |
| Find and fix a bug in a large codebase | $5.41 | $0.12 |