[BUG] vNet Isolation Not Available for Central US

[lsuarez5280]

To Reproduce

1. Create infrastructure necessary to connect a vNet injected Cloud Shell to an Azure Virtual Network in the Central US region.
2. Configure the infrastructure selections at https://shell.azure.com using Advanced Settings + VNET isolation settings.
3. Observe error response from the user settings API.

Observed Behavior

• https://management.azure.com/providers/Microsoft.Portal/userSettings/cloudconsole?api-version=2023-02-01-preview endpoint responds with 400 error due to properties.vnetSettings.location property value of centralus.

  {
    "error": {
      "code": "InvalidLocation",
      "message": "The location 'centralus' is invalid."
    }
  }
  

  
• Arbitrary change of properties.vnetSettings.location to alternate secondary region westcentralus results in successful response.

Expected behavior

Was hoping for a 200 and successful cloud shell configuration/startup. It's unclear from any published documentation if the Central US secondary region supports the cloud shell vNet injection scenario. It was surprising to find that while this secondary region was unsupported, the younger West Central US region is supported.

Is this specific to Cloud Shell?

Yes

Interface information

The same result occurs using:

• PowerShell Invoke-RestMethod
• https://portal.azure.com (Edge for Win11 v113.0.1774.57 x64)

Additional context

It's possible I may just be looking for an availability matrix for vNet injection in secondary regions. It appears this error will also occur when using these other secondary regions as well: East US 2, West US 2, North Central US.

[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.