You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Azure Tools extension in Cursor is unable to complete authentication, getting stuck at "waiting for authentication provider to register" indefinitely. This occurs despite being properly authenticated with Azure CLI and the extension working correctly in VS Code.
Environment
OS: Windows 10 (22631) running WSL Ubuntu
Azure CLI: 2.68.0
Authentication: Successfully logged in via Azure CLI
Azure Account: Properly configured and working in VS Code
Steps to Reproduce
Install Azure Tools extension in Cursor
Attempt to sign in using either:
Command Palette > "Azure: Sign In"
Command Palette > "Azure: Sign In with Device Code"
Authentication process hangs at "waiting for authentication provider to register"
Tried both regular sign-in and device code authentication methods
Completely closed and reopened Cursor
Expected Behavior
Azure Tools extension should complete authentication process
Should be able to access Azure resources through the extension, as it does in VS Code
Actual Behavior
Authentication process never completes
Extension remains stuck at "waiting for authentication provider to register"
Impact
This blocks essential Azure-related development work and forces users to switch to VS Code for Azure operations, defeating the purpose of having the extension in Cursor.
Additional Context
Azure CLI authentication works correctly
The same extension and authentication process work properly in VS Code
This appears to be a Cursor-specific issue with the extension's authentication provider
The text was updated successfully, but these errors were encountered:
Azure Tools Extension Authentication Issue
Description
The Azure Tools extension in Cursor is unable to complete authentication, getting stuck at "waiting for authentication provider to register" indefinitely. This occurs despite being properly authenticated with Azure CLI and the extension working correctly in VS Code.
Environment
Steps to Reproduce
Attempted Solutions
Expected Behavior
Actual Behavior
Impact
This blocks essential Azure-related development work and forces users to switch to VS Code for Azure operations, defeating the purpose of having the extension in Cursor.
Additional Context
The text was updated successfully, but these errors were encountered: