openclaw-azure-config

Name: openclaw-azure-config
Availability: InStock
Author: kyle-deprow

Configure OpenClaw's Azure OpenAI provider with API key management and api-version preload.

Updated Mar 21, 2026

Search Tags:#cold-start #openclaw #azure-openai #api-key-management #provider-config #api-version-preload

Ready to run

npx skills add https://github.com/kyle-deprow/ai_scaffolding --skill openclaw-azure-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-azure-config
Source: https://github.com/kyle-deprow/ai_scaffolding/tree/main/skills/openclaw-azure-config
Command: npx skills add https://github.com/kyle-deprow/ai_scaffolding --skill openclaw-azure-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw Azure OpenAI provider configuration, cold-start setup, API key management, and the api-version fetch preload workaround. Use when setting up OpenClaw with Azure OpenAI from scratch, debugging 401/404 inference errors, managing the push-config workflow, or configuring the NODE_OPTIONS preload.

Core Features & Use Cases

Cold-start install and onboarding for a fresh server or VM.
Repository-managed provider config overlay with model and agent defaults, plus strict schema validation.
API key management and rotation workflow, including env-based key substitution.
API-version preload mechanism to ensure Azure OpenAI requests include the required api-version param.
Push-config automation to merge repo config into local OpenClaw config and validate status.
Debug guidance for common Azure OpenAI errors (401/404) and endpoint changes.

Quick Start

Install and onboard OpenClaw, configure your Azure API key, push the repo config, and launch the OpenClaw services.

Frequently Asked Questions about openclaw-azure-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure Azure OpenAI provider settings for a cold-start setup?▼

Azure OpenAI provider configuration for cold-start setup requires a strict provider config schema, env-based API key resolution, and automated api-version preload injection. This enforces model and agent defaults while validating the config overlay during initial server onboarding.

Why does my Azure OpenAI deployment return 401 or 404 inference errors?▼

Azure OpenAI 401 and 404 inference errors often result from missing api-version parameters or invalid endpoint configurations. Debug guidance addresses endpoint changes and API key management issues, while the api-version preload mechanism ensures required parameters are included in requests.

What is the best way to manage API key rotation for Azure OpenAI?▼

API key management and rotation for Azure OpenAI uses env-based key substitution to securely update credentials. The push-config automation merges repository config into local OpenClaw config, validating status and ensuring the strict provider config schema remains enforced.

Do I need NODE_OPTIONS preload configured for Azure OpenAI api-version requests?▼

The NODE_OPTIONS preload is required to ensure Azure OpenAI requests include the necessary api-version parameter. The automated preload injection mechanism handles this configuration, preventing 401/404 inference errors caused by missing api-version parameters during provider setup.

Can I use repository-managed config overlays to set Azure OpenAI model defaults?▼

Repository-managed provider config overlays enforce strict schema validation for Azure OpenAI model and agent defaults. Push-config automation merges these repository configurations into your local OpenClaw config, validating status and ensuring consistent provider setup across deployments.