openclaw-azure-config

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.

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.

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.

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.

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.