Share via

Error detail: 'Failed to provision Cloud Shell'

Hristiyan Genchev 5 Reputation points
2025-04-01T12:40:46.4033333+00:00

I'm trying to create a CloudShell inside a VNet (using the portal) but when it starts I get the following issue 

Sorry, your Cloud Shell failed to provision: {"code":"ConsoleDeploymentFailed","message":"Console Deployment failed. Error detail: 'Failed to provision Cloud Shell. Please refer to: https://aka.ms/cloudshell-vnet-troubleshootingguide or contact Azure support. For tracking purposes, Correlation Id: 18088a7d-a4c0-4888-a4d7-e4a49e33390c and Activity Id: 193533a7-b93b-4dee-a307-2b3fb05e5075'."} Please refresh the page. If the issue persists, please follow the troubleshooting guide Cloud Shell Troubleshooting or file a ticket New support request.  Request correlation id: FRANCECENTRAL:20250401T122155Z:18088a7d-a4c0-4888-a4d7-e4a49e33390c

How to resolve this issue or at least get better details around it because this error message doesn't mean a lot.

Azure Virtual Network
Azure Virtual Network

An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amira Bedhiafi 42,941 Reputation points MVP Volunteer Moderator
    2025-04-01T21:22:08.8+00:00

    You're encountering a common issue when provisioning Azure Cloud Shell inside a VNet. This typically happens due to misconfiguration in the delegated subnet, missing network resources, or NSG/firewall issues.

    Cloud Shell requires a delegated subnet specifically for Microsoft.Web/serverFarms.

    • Go to your VNet > Subnets > Select the subnet you're using for Cloud Shell.
    • Verify it is delegated to: 
        Microsoft.Web/serverFarms

    Make sure the subnet has access to these:

    • Storage Account: Cloud Shell needs a file share mounted.
    • Public IP / DNS Resolution: Even if you're inside a VNet, the shell needs to resolve public domains (like microsoft.com) for updates and connections.
    • If using private DNS zones, ensure correct DNS forwarding is set up (to Azure 168.63.129.16 resolver).

    Check your NSG for outbound rules. It must allow outbound access to:

    Destination Ports Purpose
    *.azure.com, *.microsoft.com 443 API calls
    *.azure.com, *.microsoft.com 443 API calls
    Storage account endpoint 443 File share mount
    168.63.129.16 53, 80, 443 Azure infrastructure communication

    If you block outbound traffic to public IPs, Cloud Shell cannot start.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.