I have three models in Azure: gpt-4.1, o3, o4-mini
GPT-4.1 works fine, but once I change Deployment Name to o3/o4-mini, I get Unauthorized User API Key error.
Anyone else having the same issue? What am I doing wrong?
1 Like
same issue. Azure provider
Getting the same error. cc @deanrie Any chance this could be supported?
chatid: aea55cc9-0ee3-4753-9f19-c65479bfae21
Hey @bobbybo, @threadshare, @ItzAmirreza could you let me know if you have an overridden base URL for the OpenAI API key? It was previously noted that resetting it to default settings should solve the issue, but I’m not sure if this is also not a problem with the Azure API key.
having the same issue, has a solution been found for this? I don’t have anything set in the base URL for the OpenAI API key.
My key is working. When I enable the toggle, it turns green which confirms the key works, otherwise, I wouldn’t be able to enable the toggle if the key is not active and not working
Request ID: b41badc9-4b10-44a5-8d3d-985ebd13a98b
1 Like
Same issue here.
Gpt-4.1 and o3-mini work.
Mine was basically working before the last update. I had gpt4.1 deployed in aifoundry and could select from many open ai models in the chat dropdown and it would generate responses presumably because it uses the same api. But now someone has changed something either with cursor or microsoft because this afternoon it all came to a halt. Getting permissions errors as global admin. I can make a sample query with a py and get a nice result but microsoft is rejecting the calls made directly from the cursor agent. This is a really horrible system since you can’t tell the api is even enabled unless it fails. It would be nice to not have to turn it off when I needed a better result for a specific query. PLEASE cursor-devs make a useful ui for implementing multiple models and keys. I havent tried my aws or openapi direct keys yet but I think we can all agree the system needs to be revised.