Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Enable Azure OpenAI integration with OpenClaw via a lightweight local proxy. Use when configuring Azure OpenAI as a model provider, when encountering 404 errors with Azure OpenAI in OpenClaw, or when needing to use Azure credits (e.g. Visual Studio subscription) with OpenClaw subagents. Solves the api-version query parameter issue that prevents direct Azure OpenAI integration.
Enable Azure OpenAI integration with OpenClaw via a lightweight local proxy. Use when configuring Azure OpenAI as a model provider, when encountering 404 errors with Azure OpenAI in OpenClaw, or when needing to use Azure credits (e.g. Visual Studio subscription) with OpenClaw subagents. Solves the api-version query parameter issue that prevents direct Azure OpenAI integration.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
A lightweight Node.js proxy that bridges Azure OpenAI with OpenClaw.
OpenClaw constructs API URLs like this: const endpoint = `${baseUrl}/chat/completions`; Azure OpenAI requires: https://{resource}.openai.azure.com/openai/deployments/{model}/chat/completions?api-version=2025-01-01-preview When api-version is in the baseUrl, OpenClaw's path append breaks it.
# Set your Azure details export AZURE_OPENAI_ENDPOINT="your-resource.openai.azure.com" export AZURE_OPENAI_DEPLOYMENT="gpt-4o" export AZURE_OPENAI_API_VERSION="2025-01-01-preview" # Run the proxy node scripts/server.js
Add to ~/.openclaw/openclaw.json: { "models": { "providers": { "azure-gpt4o": { "baseUrl": "http://127.0.0.1:18790", "apiKey": "YOUR_AZURE_API_KEY", "api": "openai-completions", "authHeader": false, "headers": { "api-key": "YOUR_AZURE_API_KEY" }, "models": [ { "id": "gpt-4o", "name": "GPT-4o (Azure)" } ] } } }, "agents": { "defaults": { "models": { "azure-gpt4o/gpt-4o": {} } } } } Important: Set authHeader: false β Azure uses api-key header, not Bearer tokens.
Save Azure credits by routing automated tasks through Azure: { "agents": { "defaults": { "subagents": { "model": "azure-gpt4o/gpt-4o" } } } }
Copy the template and configure: mkdir -p ~/.config/systemd/user cp scripts/azure-proxy.service ~/.config/systemd/user/ # Edit the service file with your Azure details nano ~/.config/systemd/user/azure-proxy.service # Enable and start systemctl --user daemon-reload systemctl --user enable azure-proxy systemctl --user start azure-proxy
VariableDefaultDescriptionAZURE_PROXY_PORT18790Local proxy portAZURE_PROXY_BIND127.0.0.1Bind addressAZURE_OPENAI_ENDPOINTβAzure resource hostnameAZURE_OPENAI_DEPLOYMENTgpt-4oDeployment nameAZURE_OPENAI_API_VERSION2025-01-01-previewAPI version
curl http://localhost:18790/health # {"status":"ok","deployment":"gpt-4o"}
404 Resource not found: Check endpoint hostname and deployment name match Azure Portal. 401 Unauthorized: API key is wrong or expired. Content Filter Errors: Azure has aggressive content filtering β some prompts that work on OpenAI may get blocked.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.