You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Couldn't create a vnet integrated cloudshell in the germanywestcentral secondary region. I had to use the az rest method as there's an issue with the portal and the storage selection dropdown is disabled, so there's a chance that the request body is not perfect.
az rest --method put --url https://management.azure.com/providers/Microsoft.Portal/userSettings/cloudconsole?api-version=2023-02-01-preview --body @cloudshell.json
Observed Behavior
The request returns with an error:
Bad Request({
"error": {
"code": "InvalidLocation",
"message": "The location 'gernamywestcentral' is invalid."
}
})
Expected behavior
The cloudshell is created.
Is this specific to Cloud Shell?
Yes.
Interface information
not relevant.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
This restriction is not mentioned in the feature documentation and the portal also allows you to select secondary regions. (Though currently the portal fails to create vnet integrated cloudshell for any region.).
The problem seems to be a simple request validation issue, but could be more.
Despite this, the issue can be relabeled to feature request or closed as duplicate, but the lack of this feature limits the usability of cloudshell.
Couldn't create a vnet integrated cloudshell in the germanywestcentral secondary region. I had to use the
az rest
method as there's an issue with the portal and the storage selection dropdown is disabled, so there's a chance that the request body is not perfect.To Reproduce
cloudshell.json
request example:Observed Behavior
The request returns with an error:
Expected behavior
The cloudshell is created.
Is this specific to Cloud Shell?
Yes.
Interface information
not relevant.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: