Network Injected Azure Cloud Shell Not Supported

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

1. Configure Cloud Shell with Azure Virtual Network injection according to the documentation. IMPORTANT: Deploy the virtual network in a Cloud Shell primary region to avoid failures, e.g. East US, West US, or South Central US as it seems secondary region support isn't guaranteed for the virtual network injection scenario in other regions.
2. Open an Azure Cloud Shell tab and perform device code login.
3. [Optional] Select a tenant from the list displayed by Terminal if appropriate for your account.
4. Elect whether to save connection settings.
5. Observe outputs.

Expected Behavior

A terminal prompt.

Actual Behavior

After logging in, selecting a tenant from my account list, and confirming saving connection settings, the terminal immediately displays:

Requesting a cloud shell instance...
Succeeded.
Requesting a terminal (this might take a while)...

[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

Start with the documented Azure Cloud Shell private VNet setup and reproduce the login flow in the issue using a supported primary region. Compare the expected terminal prompt with the process-exit failure after tenant selection and saved connection settings. Done means a network-injected Cloud Shell reaches a usable terminal prompt.