Thanks for providing those details! I noticed an important mismatch:
In your Cursor settings you have: https://{myresource}.services.ai.azure.com/anthropic
But in your working Python example you use: https://{myresource}.openai.azure.com/anthropic
Please update your Cursor settings to use the same endpoint URL format as in your working Python code (with openai.azure.com instead of services.ai.azure.com) and test again.
Also, please share the console errors as I asked above (Help → Toggle Developer Tools → Console tab, then test the model).
Thanks for the logs. I can see the issue now - Cursor is showing ERROR_OPENAI and [invalid_argument] errors, which means Cursor is treating your Azure Anthropic deployment as an Azure OpenAI endpoint.
The problem is that Anthropic models in Azure AI Foundry use a different API format than Azure OpenAI. Your Python code works because the AnthropicFoundry client uses the correct Anthropic API format, while Cursor’s Azure integration currently only supports the Azure OpenAI API format.
Fixing this will require engineering work to add full support for Anthropic in Azure AI Foundry. I’ll pass this to the team as a feature request/bug.
Yes, there’s a problem with Sonnet 4.5. I’m having the same problem. You’re asking for a log, but this isn’t a specific problem; it’s a general one. I haven’t used it for a week. I was spending $200 a day.
Hoping to get full support for Anthropic models through Azure AI Foundry. For anybody looking for a workaround, you can use the Claude Code extension. Not the same but at least I can keep using Claude models after I hit the Cursor Pro usage limits..