Hey, this isn’t a misconfiguration. Using your own API keys (BYOK), including Azure OpenAI, now requires a Pro subscription. On the Free plan, your own keys won’t work even if they’re set up correctly.
Hmm, from what we can see on our side, your account shows as Free.
If you’re actually on Enterprise, then BYOK with Azure OpenAI should work. A couple things to check:
Make sure you’re logged in with your Enterprise account, the email that’s tied to the Enterprise team.
Check with your Enterprise admin whether BYOK is disabled at the team level. In Enterprise there’s a setting called Restrict personal API keys, and it can block BYOK.
Let me know what you see in settings and we’ll figure it out.
Since today it April 1, I received my new monthly Cursor pocket money and wanted to retest BYOK with Azure OpenAI: no complain about the key, but also, no output. Any idea? I feel Cursor should give some kind of message (invalid key, BYOK disabled, invalid, model deployment name, etc.) so maybe worth raising an issue internally on your side. I’m leaving my enterprise email in the screenshot if you want to see the log + model deployment name to show it matches the selected model in Cursor chat: