Thomas Moerman

I'm having a similar issue connecting to a remote tunnel, same error message (using Cursor, works fine in VS Code). I suspect that it is related to how Cursor handles...

For people exerpiencing this issue using Cursor, it might be good to specifically comment on their repo. For example on this issue: https://github.com/getcursor/cursor/issues/1191. @seo1623 @port2077 @marcosclub

Yes, I second this. Also, it seems that currently Cursor turns off / doesn't have the builtin Microsoft extension leading to some confusion related to this, see also: [https://github.com/microsoft/vscode-azure-account/issues/897#issuecomment-1981727943](https://github.com/microsoft/vscode-azure-account/issues/897#issuecomment-1981727943 )

An update on this would be really helpful. The ability to connect to tunnels and use the Microsoft account plays a significant role in the workflow for many of us.

@adriantheuma @gameveloster have you found any answers to these issues?

Thanks for the update! It seems that I'm still unable to use my Microsoft account to connect to a remote tunnel. Also, the Microsoft extension is not enabled/installed as far...

This seems to be the solution: https://github.com/microsoft/vscode-azure-account/issues/897#issuecomment-2424082420 > Found the fix elsewhere. https://forum.cursor.com/t/azure-extension-doesent-work/3949/15 > > **Fix Azure extensions on Cursor** Cursor does not come with Microsoft authentication, a builtin extension...