Azure OpenAI Chat Works, but Cursor “Apply” Fails (404) Due to Hardcoded /v1/responses Endpoint Mismatch

[Pedro_Maia]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor IDE (AI features → Apply / patching, and any flow that uses the Responses API style)

Steps to Reproduce

1. In Azure OpenAI / Azure AI Foundry, deploy a chat-capable model (example: gpt-4o, gpt-5.x-chat) and copy:

• Resource endpoint (e.g. https://.openai.azure.com)
• API key
• Deployment name (if applicable)

2. In Cursor → Settings → Models / API Keys, configure a provider so Cursor can use your Azure deployment (BYOK).

• Use the Azure endpoint as the Base URL and your Azure key.

3. Verify normal usage works:

• Open a file / repo
• Use chat/composer/generation features (anything not Apply) → works

4. Now trigger Apply (patching) from an AI suggestion (the “Apply” button / patch flow).
5. Observe the failure:

• Request attempts to hit an OpenAI-style path like /v1/responses
• Azure returns 404 / Resource not found (or Cursor may hang/crash)

This aligns with other Cursor reports where Cursor sends Responses API requests to the wrong endpoint/path, producing 404s.

Expected Behavior

When using Azure OpenAI as the backend, Cursor’s Apply (patching) should call Azure’s Responses API using Azure’s required routing, e.g.: POST https://{endpoint}/openai/v1/responses?api-version=preview

…instead of calling POST {endpoint}/v1/responses (which causes 404s on Azure).

Result: Apply should successfully generate and apply the patch, just like the other Cursor actions that already work with the same model configuration.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

GPT 5.2 Chat

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report.

This is a known issue - Azure OpenAI endpoints use different routing for the Responses API compared to standard OpenAI, and Cursor’s Apply/Agent features currently send requests in a format that causes 404s on Azure.

The team is aware and working on improving Azure BYOK compatibility. As a workaround for now, you’ll need to use Cursor’s built-in models for Apply/Agent Mode operations.

Related thread with same issue: Cursor Agent Mode cannot modify files when using Azure-deployed GPT-5 mini (communication works but no file editing)