A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.
Hello Rachita Sharma,
You’re trying to use Azure Cloud Shell with VNet integration. Your resources and VNet are in UAE North, but Cloud Shell was initially set up in Central India. Cloud Shell provisioning fails with a ConsoleDeploymentFailed error when attempting to attach to the UAE North VNet, indicating a regional mismatch and/or missing VNet prerequisites.
Cloud Shell runs its compute and uses a storage account in the region chosen at first setup. It cannot attach to a VNet in a different region.The target subnet must permit Cloud Shell traffic (service endpoints or private access), have correct NSG rules, and not block required outbound paths. If these are missing or misconfigured, provisioning fails even in the same region.
To fix this you can remove the current backing storage Delete the Cloud Shell storage account and file share in Central India (or choose “Change storage” in Cloud Shell). this result forces Cloud Shell to re-prompt you for storage on next launch.
Create storage a storage account and file share in UAE North or let Cloud Shell create them when prompted. Choose UAE North in the prompt.
Align VNet and subnet in UAE North, Use a subnet (e.g., snet-cloudshell) in vnet-cloudshell-aura-dev-uan for Cloud Shell integration.
Config checklist:
- Subnet delegation/service endpoints: Enable service endpoint for Microsoft.Storage if using public storage. or If using Private Endpoints, ensure DNS and routing resolve the storage account.
- NSG rules: Allow outbound to Azure Storage and Azure control plane endpoints. Deny-all outbound without exceptions.
- Route tables: Ensure no UDRs blocking internet/Azure service paths required by Cloud Shell.
In Cloud Shell “Networking” settings, select the UAE North VNet/subnet. Provisioning should complete; no ConsoleDeploymentFailed error.
Hope this helps. Thanks