-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Account timeout, cannot use Azure plugins #1648
Comments
Writing to endorse the issue. I'm having the same problem here. |
Same issue here. No solution yet. |
Same issue here, also a problem with the databricks extension. Only a problem with WSL though. |
Same problem here |
Seems like this issue is related to the fact that Azure authentication is relying now on this Microsoft Authentication extension, which is build-in VSCode lately. This extension is missing on cursor. So, if anyone knows how to pack that buildin extension into a .vsix file probably it will solve this problem. |
I looked heavily into this a while ago but had to switch back to vscode for the project I needed Azure integrations with. And to your point @vladsterian-diconium, I even tried switching the MS auth setting that PR is aiming to do:
But not luck. Some more details: Azure Resource Groups
Window
Extensions host
|
Still having this issue as well |
This seems to be the solution: microsoft/vscode-azure-account#897 (comment)
|
I confirm that the solution works, however only using MSAL |
OS: Windows 11, also WSL Ubuntu
We are currently evaluating Cursor as a replacement for VS Code / Co-Pilot, and noticed this problem, which is now blocking us: The Azure extensions do not function, with a "timed out waiting for authentication provider to register" message.
You can try and do the Azure login commands but it does not seem to do anything inside of Cursor
This issue related to remote tunnels mentioned this problem, but I think this is a separate issue: #1191
Also see microsoft/vscode-azure-account#897, though it does seem like it's a Cursor issue.
The text was updated successfully, but these errors were encountered: