azure-cli-extensions: az network bastion rdp does not work for IP-based connection

Describe the bug

Since last few days , we are experiencing issues with RDP connection to Azure VMs using az network bastion rdp IP-Based command. Few of our observations below -

  • the operation fails in few regions, so far we have tested Canadeast , Canada Central and West Europe.
  • the command/operation works fine using --target-resource-id parameter irrespective of the region
  • IP based connection using “Connect” option from the Bastion blade in the portal works fine.

Command Name az network bastion rdp Extension Name: bastion. Version: 0.2.3.

Errors:

While the command does not display any error but I occasionally I get "An Internal Error Occured" dialogue box once the requested RDP connection fails or sometimes the "Remote Desktop Connection" keeps connecting without any error, post cancellation we get 
**[WinError 10054] An existing connection was forcibly closed by the remote host** only when we run the command with `--debug` flag.


To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Bastion resource should be deployed in Canada East region

  • az network bastion rdp --name {} --resource-group {} --target-ip-address {} or
  • az network bastion rdp --name {} --resource-group {} --target-ip-address {} --debug

Expected Behavior

Upon successful completion of the command and remote desktop connection, we should get login prompt to enter our username and password for the VM to login.

Environment Summary

Windows-10-10.0.19045-SP0
Python 3.10.10
Installer: MSI

azure-cli 2.46.0

Extensions:
account 0.2.1
bastion 0.2.3
interactive 0.4.5

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context

if this helps msal.telemetry: Generate or reuse correlation_id: b6398262-da94-419a-8a72-196b25642623

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 17 (3 by maintainers)

Most upvoted comments

Hi @mbeaudin @AussieDavo this feature will not be available soon. I’ve been told that it’s still on development and there is no concrete deployment date, so don’t expect to use the ‘–target-ip-address’ argument at the moment. The connection via ‘–target-resource-id’ works though.

This feature is also available as documentation, so many people may be using it. I use it myself.

I hope it will be officially released soon🙏.