Windows Terminal fails to instantiate Azure Shell when it is configured with an isolated VNET

[robey-ms]

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.1379]
Windows Terminal version (if applicable):  Version: 1.0.1401.0

Any other software? No

Steps to reproduce

Configure Cloud Shell with isolated VNET settings per https://docs.microsoft.com/en-us/azure/cloud-shell/private-vnet
Validate correct Cloud Shell behavior with https://shell.azure.com
In Windows Terminal attempt to create a new session for Azure Cloud Shell

Expected behavior

Cloud shell opens.

Actual behavior

Cloud shell fails to instantiate with the messages:
You have not set up your cloud shell account yet. Please go to https://shell.azure.com to set it up.
[process exited with code 1]

[zadjii-msft]

Thanks for the report!

[DHowett]

Thanks indeed. This is another one of the unfortunate side effects of having reverse-engineered their protocol. 😄

[DHowett]

Also:

Windows Terminal version (if applicable): Version: 1.0.1401.0

wow. It's been a while! We're at 1.6 now 😄

[Don-Vito]

Thanks indeed. This is another one of the unfortunate side effects of having reverse-engineered their protocol. 😄

Not sure if the feature existed when the protocol was reversed. IMHO it wasn't there from beginning.

[robey-ms]

Feature went live in Sept I think. And yes I need to get them to approve a newer version for our images. Once this is fixed I'll jump on it. :)

[ThomasPiskol]

Any news regarding this issue? Currently it's added to the 2.0 milestone and that's the end of this year 🥺
Is there any change that it will get fixed in an earlier version?