Founder of SAGEWORKS AI — building the Web4 layer where AI, blockchain & time flow as one. Creator of Mind’s Eye and BinFlow. Engineering the future of temporal, network-native intelligence.
Appreciate everyone who’s been asking about Azure support in OpenClaw — this post is basically my “fine, I’ll just route around it” moment 😅
Quick recap: OpenClaw doesn’t speak Azure OpenAI (or Azure AI Foundry) natively yet, so the move is:
OpenClaw → LiteLLM Proxy → Azure OpenAI
OpenClaw thinks it’s talking to OpenAI, LiteLLM translates the requests, and you get to burn Azure credits instead of paying direct.
The two things that matter most (because they cause 90% of the pain):
drop_params: true in LiteLLM (Azure rejects some params OpenClaw sends, like store)
setting "api": "openai-completions" in OpenClaw’s provider config (otherwise you get the dumb “api: undefined” error)
If you’re using startup sponsorship credits / MSDN / enterprise Azure policies, this makes OpenClaw actually usable in those environments right now.
Curious though — who here is trying to run agents through Azure for compliance/region reasons vs just because free credits are free credits? 😂
Drop your setup + what you got stuck on, and I’ll help troubleshoot in the comments.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Appreciate everyone who’s been asking about Azure support in OpenClaw — this post is basically my “fine, I’ll just route around it” moment 😅
Quick recap: OpenClaw doesn’t speak Azure OpenAI (or Azure AI Foundry) natively yet, so the move is:
OpenClaw → LiteLLM Proxy → Azure OpenAI
OpenClaw thinks it’s talking to OpenAI, LiteLLM translates the requests, and you get to burn Azure credits instead of paying direct.
The two things that matter most (because they cause 90% of the pain):
drop_params: true in LiteLLM (Azure rejects some params OpenClaw sends, like store)
setting "api": "openai-completions" in OpenClaw’s provider config (otherwise you get the dumb “api: undefined” error)
If you’re using startup sponsorship credits / MSDN / enterprise Azure policies, this makes OpenClaw actually usable in those environments right now.
Curious though — who here is trying to run agents through Azure for compliance/region reasons vs just because free credits are free credits? 😂
Drop your setup + what you got stuck on, and I’ll help troubleshoot in the comments.