Integrating OpenClaude with Azure OpenAI Cognitive Services endpoints.
Raw Developer Origin & Technical Request
GitHub Issue
Apr 1, 2026
I followed gitlawb.com/node/repos/z6MkqD... for AzureOpenAi
My attempts:
```
export CLAUDE_CODE_USE_OPENAI=1
export OPENAI_API_KEY=************************
export OPENAI_BASE_URL=*********-eastus2.cognitiveservices.azure.com/openai/deployment...
export OPENAI_MODEL=gpt-5.4-nano
openclaude
```
--> 404
```
export CLAUDE_CODE_USE_OPENAI=1
export OPENAI_API_KEY=************************
export OPENAI_BASE_URL=*************-eastus2.cognitiveservices.azure.com
export OPENAI_MODEL=gpt-5.4-nano
openclaude
```
--> 404
```
export OPENAI_BASE_URL=***********-eastus2.cognitiveservices.azure.com/openai/v1/
....
```
--> 401
Further debugging attempts:
- I recalled that opencode differentiates between azurenopenai and azure cognitiveservices: opencode.ai/docs/providers/ But i guess that would need some application code change?
- One cant control in azure to set to openai or cognitiveservice, its set automatically to best of my knowledge
Cross checking in Python **works**:
```
import os
from openai import AzureOpenAI
endpoint = "xxxxxxxxxxxxxxxx-eastus2.cognitiveservices.azure.com/"
model_name = "gpt-5.4-nano"
deployment = "gpt-5.4-nano"
subscription_key = "xxxxxxxxxxxxxxx"
api_version = "2024-12-01-preview"
client = AzureOpenAI(
api_version=api_version,
azure_endpoint=endpoint,
api_key=subscription_key,
)
response = client.chat.completions.create(
messages=[
...
Developer Debate & Comments
No active discussions extracted for this entry yet.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from Gitlawb/openclaude.
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like 401 and OPENAI_API_KEY by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.
Market Trends