Cloud Shell failed to request a terminal

Hello Robert,

Thank you for sharing the details and screenshot.

The error “Sorry, your Cloud Shell failed to request a terminal” typically occurs when Azure Cloud Shell is unable to establish the required WebSocket connection to the Cloud Shell service. This is commonly related to network restrictions, browser session issues, or tenant‑specific configuration rather than a problem with your Azure resources themselves.

Please try the following steps in order:

1. Restart Cloud Shell Click Restart directly in the Cloud Shell pane. This forces a new backend session and often resolves transient connection issues. [learn.microsoft.com]
2. Try a clean browser session Open Cloud Shell using an InPrivate/Incognito window or a different supported browser (Microsoft Edge or Chrome). Browser extensions or cached sessions can interfere with the Cloud Shell handshake. [bing.com]
3. Verify network and firewall access Ensure your network or proxy allows HTTPS and WebSocket traffic to the following endpoints:
   • *.console.azure.com
   • *.servicebus.windows.net Blocking these endpoints prevents the terminal from being created.
4. Reset Cloud Shell user settings In the Cloud Shell menu, select Settings → Reset user settings and reconnect. This clears any corrupted Cloud Shell configuration associated with your profile.
5. Check Cloud Shell storage configuration Cloud Shell requires an associated Azure Storage account. If the storage account was deleted or modified recently, reopen Cloud Shell and allow it to recreate or reattach a valid storage account.

Note : This is an AI content

Links

https://learn.microsoft.com/en-us/azure/cloud-shell/faq-troubleshooting

https://learn.microsoft.com/en-us/azure/cloud-shell/overview

Thanks,
Manish

The error message you are encountering, "Sorry, your Cloud Shell failed to request a terminal," typically indicates that Cloud Shell is unable to establish a websocket connection to its infrastructure. This can happen for several reasons, including network restrictions or DNS resolution issues.

To troubleshoot this issue, you can try the following steps:

1. Network Configuration: Ensure that your network allows sending HTTPS and websocket requests to the following domains:
   • *.console.azure.com
   • *.servicebus.windows.net
   • If you are using Azure Government Cloud, also check *.servicebus.usgovcloudapi.net.
2. Private DNS Issues: If you are accessing Cloud Shell from a network that uses a private DNS resolver, it may cause DNS resolution problems. You can add a DNS record for the Azure Relay instance that Cloud Shell uses. To do this:
   • Open your browser's Developer Tools (F12) and navigate to the Network tab.
   • Look for requests to terminals? to find the Azure Relay instance name.
   • Use the nslookup command from a host outside your private network to find the IP address of the hostname you identified.
3. Restart Cloud Shell: Sometimes, simply clicking the restart button in Cloud Shell can resolve temporary issues.

If the issue persists after trying these steps, consider filing a support request with Azure support, including your tenant ID and any relevant details about the error.

References:

• Azure Cloud Shell frequently asked questions (FAQ)
• Azure Cloud Shell frequently asked questions (FAQ)