# Struggling with Azure OpenAI setting

**URL:** <https://forum.cursor.com/t/struggling-with-azure-openai-setting/810>\
**Category:** Help\
**Created:** [September 30, 2023, 3:41pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810 "2023-09-30T15:41:52Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![JimmC](https://avatars.discourse-cdn.com/v4/letter/j/5e9695/32.png) [@JimmC](https://forum.cursor.com/u/JimmC)\
**Post date:** [April 19, 2025, 5:39pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810/21 "2025-04-19T17:39:00Z")

</div>

Has this been fixed? It currently only works with 4o

---

<div class="post-metadata">

**Author:** ![ksquarekumar](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ksquarekumar/32/9202_2.png) [@ksquarekumar](https://forum.cursor.com/u/ksquarekumar)\
**Post date:** [June 7, 2025, 6:36pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810/22 "2025-06-07T18:36:36Z")

</div>

Do reasoning and max mode even work for BYOK at all ?  
@danperks is there anything in the roadmap for this?

- not having parity between self hosted and BYOK while having something like max mode with it’s per api-call pricing seems like an inconsistency in the product positioning by cursor, if reasoning and max mode are not going to be offered for BYOK why even have BYOK at this point ?

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [June 11, 2025, 9:41pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810/23 "2025-06-11T21:41:39Z")

</div>

The difficulty with API key support in general is various models and providers all have different formats for how they need requests to be structured.

I’ve bumped this feedback up again internally to see if it’s something we can resolve in the future, but due to the 1000s of things we want to work on and the engineering capacity we have, BOYK is currently offered as a “best effort” feature until we can dedicate some time to give it some love or a revamp.

---

<div class="post-metadata">

**Author:** ![gabrii](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/gabrii/32/79648_2.png) [@gabrii](https://forum.cursor.com/u/gabrii)\
**Post date:** [September 14, 2025, 4:22pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810/24 "2025-09-14T16:22:17Z")

</div>

@ksquarekumar I’ve created this project for the community, which allows you to use Azure GPT-5 in Cursor [GitHub - gabrii/Cursor-Azure-GPT-5: A service that allows Cursor to use Azure GPT-5 deployments.](https://github.com/gabrii/Cursor-Azure-GPT-5)

It’s not perfect, but useful until model support is improved by the team. And after building this, I can attest to the complexity of supporting different BYOK configurations

---

<div class="post-metadata">

**Author:** ![Mehrdad](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mehrdad](https://forum.cursor.com/u/Mehrdad)\
**Post date:** [September 23, 2025, 4:11pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810/25 "2025-09-23T16:11:56Z")

</div>

Question, the app currently asks for endpoint url, deployment name, and api key. However, Azure needs api version as well.

Currently gpt-4o works but gpt-5 doesn’t work. I think this is most likely due to api-version changing. When I looked at cursor code there is no place that this api-version could be changed.

Could you update this on your end? this should be a quick fix.

---

<div class="post-metadata">

**Author:** ![gabrii](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/gabrii/32/79648_2.png) [@gabrii](https://forum.cursor.com/u/gabrii)\
**Post date:** [September 24, 2025, 1:27pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810/26 "2025-09-24T13:27:12Z")

</div>

Hi @Mehrdad , it’s not just because of the api version. It’s because cursor currently doesn’t support BYOK for models using the responses api (like GPT-5). That is why gpt-4o works (as it supports the completions api).

For example, my project works by allowing cursor to consume GPT-5 as if it was a custom model served through the completions api, while behind the scenes it’s using azure through the responses api.

---

<div class="post-metadata">

**Author:** ![agamboa](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@agamboa](https://forum.cursor.com/u/agamboa)\
**Post date:** [February 17, 2026, 8:48pm UTC](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810/27 "2026-02-17T20:48:45Z")

</div>

Any update on this? We have 300k in azure credits but still need to pay three digit monthly for Cursor usage because we are unable to leverage our own keys, feels like such a waste. We deployed using azure ai foundry but there is no way to make it work.

[Previous page](https://forum.cursor.com/t/struggling-with-azure-openai-setting/810.md?page=1)
