Why companies look for an alternative to Azure OpenAI
From Azure OpenAI’s own pricing and documentation, checked 7 November 2026:
- Quota is rationed: quota is assigned per region, per model, per deployment type in tokens per minute, and at the limit further requests get HTTP 429. Increases go through a form and are subject to review and approval.
- Where data is processed depends on the deployment type: Global types may process in any Azure region, Data Zone types stay in the EU data zone, and Microsoft can add regions to a data zone without prior notice.
- Claude is a separate product: in Foundry, Anthropic is the seller and operator and acts as an independent data processor, and for the Anthropic-hosted version data might be processed outside your selected Azure geography. In Europe, Claude Global Standard is listed in Sweden Central only, and Data Zone Standard is not available.
- Budgets do not stop spend: Azure budget notifications fire when thresholds are exceeded, but resources aren't affected and your consumption isn't stopped.
- Reserved capacity is bought by the hour: Provisioned Throughput is billed hourly per PTU regardless of tokens consumed, and reservations don't guarantee capacity.
- Modified abuse monitoring is gated: it is available only to customers and partners managed by a Microsoft account team or under an eligible program.
What Standard Compute does differently
A single API gives you frontier and open-source models, and it routes each step to the cheapest model that can do it and the cheapest provider fast enough to serve it.
On Azure you size deployments and pay for each model at its own rate. On Standard Compute routine steps go to a model priced for that work and the hard step goes to GPT, Claude or Gemini, each served by the cheapest provider that meets the latency and tokens-per-second bar. You pay a flat monthly plan per person or app, and there is no regional quota to request.
Control is set once for the company, with Microsoft Entra ID as the front door:
Processing in Europe
Set a Europe rule for your company, a team or a single key, and every request, including retries and fallbacks, is served only by approved European inference endpoints. If no European endpoint can serve it, the request is refused before your prompt is sent. Our EU gateway terminates TLS and runs in Finland, and your account data is stored in Frankfurt.
Zero data retention
Turn on zero data retention for your company, a team or a key, and every request is routed only to inference endpoints that commit to keeping no copy of your data. Teams and keys inherit the requirement and can never switch it off underneath you.
No training
Standard Compute never trains on your prompts or outputs. With a region rule or zero retention turned on, every request goes only to providers that commit not to train on it.
Single sign-on
Connect Microsoft Entra ID or any SAML identity provider so your people sign in with their work accounts. Employees sign in to Claude Desktop and Claude Code with their Microsoft work account through our EU gateway, and access follows your Entra groups through SCIM provisioning.
Teams and keys
Organize your company into teams, invite colleagues by email, and give every person and every app its own key, all under one company account.
Budgets
Every person and app gets a fixed monthly budget that never overruns, and you can set spending caps per key and for the whole company. Optional top-off from a prepaid company balance keeps critical agents running.
Allow-lists
Choose exactly which inference providers may handle your data, for the whole company, a team or a single key. New providers are never added without an admin's approval, and fallbacks can never route around your list. Decide which models each key can use.
Audit
Every admin change is recorded with before and after values, and you can export a record of every request showing the model, the provider that served it and the region rule in force, kept for 12 months.
Contract
Sign our Data Processing Agreement in the dashboard. It commits us to no training on your data, no retention of your content, and breach notification within 72 hours. We publish every sub-processor and give you 14 days' notice before adding a new one.
Standard Compute and Azure OpenAI compared
| Standard Compute | Azure OpenAI | |
|---|---|---|
| Pricing | Flat monthly plan per person or app with no per-token surprises; Stripe invoices with your company name and VAT number | Per token per deployment, or Provisioned Throughput billed hourly per PTU |
| Capacity | No regional quota to request; failover to another approved provider of the same model | TPM quota per subscription, region, model and deployment type; increases reviewed |
| Cost routing | Each step goes to the cheapest model that can do it and the cheapest provider fast enough to serve it | You choose the deployment per request |
| Models | Claude, GPT, Gemini and open models (GLM, DeepSeek, MiniMax, Kimi) through one API | OpenAI models; Claude sold by Anthropic as a non-Microsoft product through Azure Marketplace |
| Processing in Europe | Europe rule per company, team or key; retries and fallbacks stay on approved European endpoints; refused before sending if none qualifies | Data Zone EU or regional deployments; Global may process in any Azure region |
| Claude in Europe | Claude Opus, Sonnet and Haiku 5.5 available under a Europe rule | Global Standard in Sweden Central; Data Zone Standard not available in Europe |
| Zero data retention | Per company, team or key; lower levels cannot switch it off | Modified abuse monitoring for managed customers or eligible programs |
| Single sign-on | SAML SSO, Microsoft Entra ID included; Claude Desktop and Claude Code sign-in with a Microsoft work account, SCIM from Entra | Microsoft Entra ID with role-based access; key-based auth can be disabled |
| Spend limits | Fixed monthly budget per key; requests are refused once it is used; caps per key and per company | Budget alerts; consumption isn't stopped |
| Teams and keys | Teams, roles, a key per person and per app | Azure RBAC roles per resource; API keys per resource |
| Provider and model allow-lists | Provider allow-list per company, team or key; new providers need an admin; models chosen per key | The deployments you create and Azure RBAC on each resource |
| DPA | Signed in the dashboard | Microsoft Products and Services Data Protection Addendum, an addendum to the Product Terms |
When Azure OpenAI fits
Azure OpenAI fits when all AI spend must sit on your Microsoft agreement, you mainly use OpenAI models, and your approved quota covers your peak load.
Moving from Azure OpenAI to Standard Compute
Standard Compute’s API runs on stdcmpt.com. https://eu.stdcmpt.com is our EU gateway in Finland.
- Connect Microsoft Entra ID or your SAML identity provider so your people sign in with their work accounts, and set up Claude Desktop and Claude Code sign-in with Microsoft work accounts.
- Create a company workspace and set the rules once for the company: a Europe rule, zero data retention, and the providers and models you approve. Teams and keys inherit them.
- Create a key for each person and each application, each with its own monthly budget.
- Change the client base URL from your resource endpoint to
https://eu.stdcmpt.com/v1and replace deployment names with model IDs. The v1 Azure OpenAI API already uses the plainOpenAI()client, so the code change is the base URL, the key and the model. - Point Claude Code and Claude Desktop at the EU gateway.
# Before: Azure OpenAI v1 API
client = OpenAI(
base_url="https://YOUR-RESOURCE.openai.azure.com/openai/v1/",
api_key=os.environ["AZURE_OPENAI_API_KEY"],
)
client.chat.completions.create(model="YOUR-DEPLOYMENT", messages=messages)
# After: Standard Compute EU gateway
client = OpenAI(
base_url="https://eu.stdcmpt.com/v1",
api_key=os.environ["STANDARD_COMPUTE_API_KEY"],
)
client.chat.completions.create(model="standardcompute", messages=messages)
# or pin a model: "anthropic/claude-sonnet-5.5"# Claude Code adds /v1/messages itself
export ANTHROPIC_BASE_URL=https://eu.stdcmpt.com
export ANTHROPIC_AUTH_TOKEN=YOUR_STANDARD_COMPUTE_KEY
claudeQuestions
Azure OpenAI doesn't cover Claude the way we need. How do we get GPT and Claude under one contract with Entra SSO?
Standard Compute gives you GPT, Claude, Gemini and open models through one API under one DPA, and your people sign in with Microsoft Entra ID. Employees can sign in to Claude Desktop and Claude Code with their Microsoft work account, with access following your Entra groups through SCIM.
Azure OpenAI keeps returning 429s and our TPM quota is maxed. What are the options besides requesting more quota?
Route through Standard Compute: there is no regional quota to request, keys run until their monthly budget is used, and if a provider goes down, your request fails over to another approved provider of the same model automatically.
Is there a GDPR-friendly alternative to Azure OpenAI with higher limits that keeps data in Europe?
With a Europe rule on your company, a team or a key, every request, including retries and fallbacks, is served only by approved European inference endpoints, and a request no European endpoint can serve is refused before your prompt is sent.
Can we put hard spending limits on AI usage per team member?
Every person and app gets its own key with a fixed monthly budget, requests are refused once it is used, and you can set spending caps per key and for the whole company.
How do we migrate from Azure OpenAI?
Connect Entra ID, set your rules, then change the base URL from https://YOUR-RESOURCE.openai.azure.com/openai/v1/ to https://eu.stdcmpt.com/v1, use a Standard Compute key and replace deployment names with model IDs.
Azure APIM as an LLM gateway vs a dedicated one like Portkey or LiteLLM: we're on Azure but also use Claude. Which fits?
Standard Compute is the dedicated gateway with GPT and Claude already behind one OpenAI-compatible API, so there are no model contracts or deployments to wire into APIM: each step goes to the cheapest model and provider that can do it, with per-key budgets, provider allow-lists and Entra SSO. An existing APIM route can use https://eu.stdcmpt.com/v1 as its backend while you move teams over.
Set up your company
Create a company workspace, invite your team and set your rules from the dashboard. Security questionnaires and procurement questions go to contact@standardcompute.com.
Create a company workspaceor write to contact@standardcompute.com
Sources (checked 7 November 2026)
- Manage Azure OpenAI quotalearn.microsoft.com
- Quotas and limitslearn.microsoft.com
- Deployment typeslearn.microsoft.com
- Claude models in Foundrylearn.microsoft.com
- Claude models: data and privacylearn.microsoft.com
- Models from partners: regionslearn.microsoft.com
- Create and manage budgetslearn.microsoft.com
- Provisioned throughputlearn.microsoft.com
- Limited accesslearn.microsoft.com
- Configure Entra ID authenticationlearn.microsoft.com
- Microsoft Products and Services DPAwww.microsoft.com
- API version lifecycle (v1 API)learn.microsoft.com