Azure AI API models still unreliable in Cursor — please prioritize a native fix

Ideas Feedback
1

Hi Cursor team,

I’m posting this because I’ve been following the forum threads about Azure model support for a long time, and I keep seeing “noted / on our radar” — but it’s been months now and the situation is still not reliable.

Right now I can’t consistently use Azure models inside Cursor in a stable way. The only way I’ve been able to make it work is by running proxy servers / custom routing workarounds. The problem is: every time Cursor updates, something changes and a new error pops up, and then I have to spend time fixing the proxy setup again. This is exhausting and it’s starting to hurt the “daily driver” experience.

I’m saying this a bit bluntly because I genuinely like Cursor and I want to keep using it:

  • I’ve recommended Cursor to a lot of people.

  • Many friends/teammates around me started using it because of my recommendation.

  • Cursor is great overall — I’m happy with it — but this Azure issue staying unresolved for months is pushing me to look for alternatives, even though I really don’t want to.

I don’t believe this is a “too hard to solve” problem for your team. I’m just asking you to prioritize a proper, native, stable Azure integration so we don’t need fragile proxy workarounds that break with every update.

If you need anything from my side, I can provide:

  • example error logs / screenshots

  • Cursor version + OS details

  • the exact proxy approach I’m using and where it breaks after updates

Please, can we get a clear update or timeline on when Azure model support will be stable in Cursor? Even a short “here’s what’s blocking it / what we’re changing” would help.

Thanks.

2 Likes
3

Hey, thanks for the feedback.

I get your frustration. This is a known issue. Azure BYOK is genuinely unstable right now, especially for code editing and Agent Mode.

What’s happening: Cursor sends requests in a format that isn’t fully compatible with the Azure OpenAI API. The tools schema is wrong for file operations. Chat works, but applying code changes breaks. It’s even worse with newer models (GPT-5, GPT-5.2) because they use the Responses API, which Cursor doesn’t support on Azure yet.

Temporary workaround:
The community proxy by @gabrii works for GPT-5 and 5-mini: GitHub - gabrii/Cursor-Azure-GPT-5: A service that allows Cursor to use Azure GPT-5 deployments.. Yeah, it’s the same fragile workaround you mentioned, but right now it’s the only stable option.

How you can help the team:
If you share specifics, I’ll pass them along:

  • Which Azure models you’re trying to use
  • The exact errors you see (screenshots or text)
  • Your Cursor version (Help > About Cursor)
  • Your proxy setup, and where it breaks after updates

The team is aware of the issue, and your report helps raise the priority.

4

I’m waiting for a resolution to this issue as well. Please escalate this to a higher priority.