Using Azure OpenAI API Key

Support Bug Reports
, , ,
1

Describe the Bug

I added Azure OpenAI configuration in Cursor IDE.
Base URL, Deployment Name and API Key.
When I try to chat with Agent using GPT-5.5 I get:
Request ID: ac5d1512-3125-413a-82cb-84085eb645d5
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble finding the resource you requested. If the problem persists, please contact support.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
kds: Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.

Steps to Reproduce

Explained above

Expected Behavior

I expect it to work :smiley:

Operating System

MacOS

Version Information

Version: 3.4.20
VSCode Version: 1.105.1
Commit: 0cf8b06883f54e26bb4f0fb8647c9500ccb43310
Date: 2026-05-15T02:26:10.351Z
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

GPT-5.5

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi @Limunce I apologize for the inconvenience. This is a known issue, and I’ve linked the forum post to the bug report so we can keep you updated on the status of it. In the meantime, the following options may immediately help you:

  1. Use a non-GPT-5 model on your Azure key. Models outside the GPT-5 family — for example a GPT-4.1 or GPT-4o deployment — use Azure’s standard deployment endpoint and should work today with your existing BYOK configuration. Just deploy/select one of those in Azure and pick it in Cursor’s model picker.

  2. If you specifically need GPT-5.5 in the meantime, you can use it through Cursor’s built-in model access (i.e., without the custom Azure key for that model). That path routes correctly. Note this draws on your normal Cursor usage rather than billing to your Azure account.