[BUG] vNet Isolation Not Available for Central US about cloudshell

[theJasonHelmick]

Hi @lsuarez5280 - Thank you for reporting this - we are investigating and will report back.

[dsajanice]

We have addressed this issue. Central US is now available in the regions dropdown list.

[lsuarez5280]

@dsajanice I am still receiving the same response from the API and the presence of the region in the dropdown was not an issue. Has this fix been deployed or is that still pending a future release?

Is there an updated API version identifier I can use with this functionality or should this still work with the Microsoft.Portal provider API version 2023-02-01-preview?

[dsajanice]

@lsuarez5280 please check again. When I last closed the issue, the rollout of the change to all regions was not complete yet.

[lsuarez5280]

@dsajanice Results have been mixed.

I'm pleased to report the issue is resolved for the Central US region, and my compliments to the team for that.

The regions identified in the additional context of this issue are still failing. These were provided when I wasn't sure if this was a defect or availability limitation. If you would prefer to keep this issue open to track those failures, I can update the original report. Otherwise, I can provide a new issue report. 400 Bad Request responses are still being returned for US regions including:

• East US 2
• West US 2
• North Central US

[hima-gadupudi]

CentralUS region is supported for VNET.