Skip to content

docs: add Azure AI Foundry provider guide#68502

Closed
monasprox wants to merge 4 commits intoopenclaw:mainfrom
monasprox:docs/azure-ai-foundry
Closed

docs: add Azure AI Foundry provider guide#68502
monasprox wants to merge 4 commits intoopenclaw:mainfrom
monasprox:docs/azure-ai-foundry

Conversation

@monasprox
Copy link
Copy Markdown

Summary

Adds documentation for using Azure AI Foundry models with OpenClaw, covering both Anthropic (Claude) and OpenAI (GPT) model families.

What's included

  • docs/providers/azure-ai-foundry.md — full provider guide following existing doc conventions

Content covers:

  • Two adapter paths: anthropic-messages for Claude, azure-openai-responses for GPT
  • Step-by-step setup with tabbed layout (Anthropic / OpenAI)
  • Auth configuration — correct auth-profiles.json setup (type "token", not "api-key")
  • Base URL gotcha — explains why /anthropic/ must NOT include /v1 (adapter auto-appends)
  • Adapter comparison table — side-by-side feature comparison
  • Troubleshooting — common issues (404 DeploymentNotFound, missing auth, context overflow, double-path URLs)
  • Environment variables reference

Motivation

Azure AI Foundry is increasingly popular for enterprise deployments. The existing docs cover direct API providers (Anthropic, OpenAI, Bedrock) but not Azure AI Foundry as an intermediary host. This guide fills that gap based on hands-on production experience.

Testing

Verified working with:

  • claude-sonnet-4-6 via anthropic-messages adapter on Azure AI Foundry
  • OpenClaw v2026.4.14 (323493f)
  • Auth via auth-profiles.json with type: "token" storage

Checklist

  • Follows existing provider doc format (frontmatter, Tabs, Steps, Accordion)
  • No code changes — docs only
  • Covers both Anthropic and OpenAI adapters
  • Includes troubleshooting for common pitfalls

Covers both Anthropic Claude and OpenAI GPT models via Azure AI Foundry.
Includes adapter comparison, auth setup, troubleshooting, and env vars.
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex rate limits. Please try again later.

@openclaw-barnacle openclaw-barnacle Bot added docs Improvements or additions to documentation size: XS labels Apr 18, 2026
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 18, 2026

Greptile Summary

This PR adds a new docs/providers/azure-ai-foundry.md guide covering both the anthropic-messages (Claude) and azure-openai-responses (GPT) adapter paths for Azure AI Foundry. The content is well-structured and follows existing provider doc conventions, but docs/providers/index.md was not updated, so the new page is unreachable from the provider directory listing.

Confidence Score: 4/5

Safe to merge after adding the provider index entry; the missing link makes the page entirely undiscoverable.

One P1 finding: the page is not linked from docs/providers/index.md, so users browsing the provider directory will not find it. No code changes are included, so no runtime risk. Score is 4 rather than 5 because the P1 discovery issue should be addressed before merging.

docs/providers/index.md (needs an Azure AI Foundry entry added alphabetically)

Prompt To Fix All With AI
This is a comment left during a code review.
Path: docs/providers/azure-ai-foundry.md
Line: 1-8

Comment:
**New page not linked from the provider directory index**

`docs/providers/index.md` lists all providers alphabetically and is the primary discovery path for users. Azure AI Foundry is not listed there, so users browsing the provider directory will never find this page. It should be added alphabetically between the Arcee AI and BytePlus entries:

```suggestion
- [Azure AI Foundry (Claude & GPT)](/providers/azure-ai-foundry)
```

(The suggestion line belongs in `docs/providers/index.md`, not in this file — adding it here just shows the intended change.)

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: docs/providers/azure-ai-foundry.md
Line: 31-32

Comment:
**Endpoint URL format inconsistent between prerequisites and examples**

The Prerequisites section shows `https://<resource>-<region>.services.ai.azure.com` (with a `-<region>` segment), but every subsequent code example uses `https://<resource>.services.ai.azure.com` without the region. Users following the steps will copy the example URL format, so the prerequisites description should match it — or both forms should be shown to cover the two naming patterns Azure uses.

```suggestion
2. Your resource endpoint URL (e.g. `https://<resource>.services.ai.azure.com` or `https://<resource>-<region>.services.ai.azure.com`).
```

How can I resolve this? If you propose a fix, please make it concise.

Reviews (1): Last reviewed commit: "docs: add Azure AI Foundry provider guid..." | Re-trigger Greptile

Comment thread docs/providers/azure-ai-foundry.md
Comment thread docs/providers/azure-ai-foundry.md Outdated
Comment on lines +31 to +32
2. Your resource endpoint URL (e.g. `https://<resource>-<region>.services.ai.azure.com`).
3. An API key from the Foundry portal (**Keys and Endpoint** section).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Endpoint URL format inconsistent between prerequisites and examples

The Prerequisites section shows https://<resource>-<region>.services.ai.azure.com (with a -<region> segment), but every subsequent code example uses https://<resource>.services.ai.azure.com without the region. Users following the steps will copy the example URL format, so the prerequisites description should match it — or both forms should be shown to cover the two naming patterns Azure uses.

Suggested change
2. Your resource endpoint URL (e.g. `https://<resource>-<region>.services.ai.azure.com`).
3. An API key from the Foundry portal (**Keys and Endpoint** section).
2. Your resource endpoint URL (e.g. `https://<resource>.services.ai.azure.com` or `https://<resource>-<region>.services.ai.azure.com`).
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/providers/azure-ai-foundry.md
Line: 31-32

Comment:
**Endpoint URL format inconsistent between prerequisites and examples**

The Prerequisites section shows `https://<resource>-<region>.services.ai.azure.com` (with a `-<region>` segment), but every subsequent code example uses `https://<resource>.services.ai.azure.com` without the region. Users following the steps will copy the example URL format, so the prerequisites description should match it — or both forms should be shown to cover the two naming patterns Azure uses.

```suggestion
2. Your resource endpoint URL (e.g. `https://<resource>.services.ai.azure.com` or `https://<resource>-<region>.services.ai.azure.com`).
```

How can I resolve this? If you propose a fix, please make it concise.

- Add Azure AI Foundry to docs/providers/index.md (P1: discoverability)
- Show both URL formats in prerequisites (P2: consistency)
@vincentkoc vincentkoc added the triage: low-signal-docs Candidate: docs-only change looks low signal; maintainer review needed. label Apr 26, 2026
@vincentkoc vincentkoc self-assigned this Apr 29, 2026
@vincentkoc
Copy link
Copy Markdown
Member

Thanks for the provider guide. Closing this because new provider docs need an owner-backed docs gap or plugin/ClawHub path; please resubmit a narrow current-main guide if this is still a supported core provider target.

@vincentkoc vincentkoc closed this Apr 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Improvements or additions to documentation size: XS triage: low-signal-docs Candidate: docs-only change looks low signal; maintainer review needed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants