Hi,
Since upgrading to 2025.1.25.0 there is an error when connecting to Azure VMs via Bastion connection:
If you click through the error, authentication proceeds and can connect to the virtual machine as usual. Just annoying!
Is this a known issue, or reconfiguration needed for new version?
Thanks!
Screenshot 2025-03-26 134518.png
Hello
Thanks for reporting the issue and I apologize for the inconvenience.
I do believe I understand partly what's going on here. In your Azure Bastion VPN entry / entries, can you change the "Connection Mode" setting to "TCP Tunnel" (I believe you currently have it set to "RD Gateway").
Let me know the outcome
Thanks and kind regards,
Richard Markievicz
Yes, that's resolved it - thanks!
I believe it was working previously as RD Gateway setting, but not after the update, had configured as per:
Configure an Azure Bastion entry in Remote Desktop Manager - Devolutions Documentation
But thank you for the quick/simple fix...
Hello again
Excellent!
I'm not sure why the update to RDM triggered this; but essentially the RD Gateway mode should be considered deprecated at this point. I've already switched the default value in RDM to TCP Tunnel, and need to plan on marking RD Gateway as deprecated or even remove it altogether. I don't believe Microsoft supports this anymore in the `az` CLI, and users have been seeing strange or intermittent behaviour with it which suggests it's going away on the backend (that may be a regional thing - I have no insight beyond reading the `az` CLI source code).
Thanks for pointing out the documentation link, I've already raised a ticket to get that updated.
Please don't hesitate if you have further questions or problems.
Kind regards,
Richard Markievicz
Hello again
Excellent!
I'm not sure why the update to RDM triggered this; but essentially the RD Gateway mode should be considered deprecated at this point. I've already switched the default value in RDM to TCP Tunnel, and need to plan on marking RD Gateway as deprecated or even remove it altogether. I don't believe Microsoft supports this anymore in the `az` CLI, and users have been seeing strange or intermittent behaviour with it which suggests it's going away on the backend (that may be a regional thing - I have no insight beyond reading the `az` CLI source code).
Thanks for pointing out the documentation link, I've already raised a ticket to get that updated.
Please don't hesitate if you have further questions or problems.
Kind regards,
Thank you for the excellent response/support - something that is sadly lacking in many products these days...
Much appreciated!