Azure OpenAI routing
Connect your Azure OpenAI endpoint and key, then point your apps at TEKIZ.AI Router. You can change deployments or use a backup without updating every client.
Configure Azure OpenAI as an authorized provider route using your
own AZURE_OPENAI_API_KEY and
AZURE_OPENAI_ENDPOINT. TEKIZ.AI does not grant
Azure, OpenAI, or Microsoft subscription access.
Point OpenAI SDKs, Codex, Cursor, Aider, Continue, OpenHands, and
compatible apps at https://api.tekiz.ai/v1. TEKIZ.AI
Router can use Azure OpenAI or another model you connected.
Choose by model profile, Azure deployment name, availability, speed, and input support. Every app can keep one gateway configuration.
export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_tekiz_your_generated_key
export AZURE_OPENAI_ENDPOINT=https://your-resource.openai.azure.com
export AZURE_OPENAI_API_KEY=your_authorized_azure_key
curl "$OPENAI_BASE_URL/chat/completions" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "tekizai/frontier",
"messages": [{"role": "user", "content": "Use the best healthy Azure OpenAI or fallback route"}]
}'
Add more than one authorized key, endpoint, or deployment. TEKIZ.AI Router uses those that are working and pauses only the path that fails.
When Azure OpenAI is rate-limited, TEKIZ.AI can try another key, deployment, provider, local Ollama model, or private model you allowed.
Images, audio, video, and documents are sent only to models that can handle that kind of input.
TEKIZ.AI provides routing, API keys, usage limits, account tools, request history, and backups. It does not include Azure OpenAI access or bypass Azure and OpenAI terms.
Create an API key, copy the hosted quickstart, use the OpenAI-compatible setup, or estimate routing fit.
If your company approves only Azure OpenAI, keep that boundary. TEKIZ.AI can reduce token burn while making better use of existing subscriptions and account billing.