Azure AI Foundry
cloud_hosted
Getting credentials
api-key
api_key via header (header api-key)
Environment: AZURE_OPENAI_API_KEY
Foundry resource → Keys and Endpoint. 32-char hex keys.
entra
entra_bearer via header (header Authorization: Bearer)
Microsoft Entra token with scope https://ai.azure.com/.default; SDKs refresh automatically. Roles like 'Cognitive Services OpenAI User'.
Endpoints
| ID | URL | Protocol | Auth |
|---|---|---|---|
| v1-responses | https://{resource}.openai.azure.com/openai/v1/responses | openai-responses | any |
| v1-chat-completions | https://{resource}.openai.azure.com/openai/v1/chat/completions | openai-chat | any |
API surfaces
textstreamingembeddingsfilesbatchfine_tuning
Quirks
- The v1 route needs no api-version query param and works with unmodified OpenAI SDKs (set OPENAI_BASE_URL). Classic route uses deployment names + api-version; responses include content_filter_results. (docs)
Models offered
| Model | Wire ID | Endpoint | Status | Reasoning |
|---|---|---|---|---|
| openai/gpt-5-6 | gpt-5.6 | v1-responses | ga | effort · default on · returns reasoning_summary · round-trips encrypted_content |