Skip to content
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 Tools Extension Incompatibility #2588

Open
harveyramer opened this issue Jan 15, 2025 · 0 comments
Open

Azure Tools Extension Incompatibility #2588

harveyramer opened this issue Jan 15, 2025 · 0 comments

Comments

@harveyramer
Copy link

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

  • 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

  1. Install Azure Tools extension in Cursor
  2. Attempt to sign in using either:
    • Command Palette > "Azure: Sign In"
    • Command Palette > "Azure: Sign In with Device Code"
  3. Authentication process hangs at "waiting for authentication provider to register"

Attempted Solutions

  1. Cleared Azure extension cached credentials:
    rm -rf ~/.azure/msal_token_cache.json ~/.azure/accessTokens.json
  2. Performed fresh Azure CLI login
  3. Cleared Azure extension state:
    rm -rf ~/.config/Code/User/workspaceStorage/**/ms-vscode.azure-account
    rm -rf ~/.config/Code/User/globalStorage/ms-vscode.azure-account
  4. Tried both regular sign-in and device code authentication methods
  5. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant