Azure Cloud Shell Could not connect to Azure behind Corp Proxy #6422

Open
opened 2026-01-31 00:38:17 +00:00 by claunia · 0 comments
Owner

Originally created by @Ugenx on GitHub (Feb 13, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): v0.9.433.0

Any other software?

Steps to reproduce

Add a new "Azure Cloud Shell" tab to your terminal instance.

Expected behavior

A prompt should appear asking to authenticate with Azure.

Actual behavior

The message "Could not connect to Azure. You may not have internet or the server might be down." appears immediately in the new tab. Fiddler only shows a single outgoing SSL initiation request to login.microsoftonline.com with a 200 response and no followup communication.

I recently had to update the cacert bundle for the azure cli located in C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\Lib\site-packages\certifi\cacert.pem to include our corp proxy certificate which restored its functionality. Is there something similar here or should the terminal be using the windows store?

Originally created by @Ugenx on GitHub (Feb 13, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): v0.9.433.0 Any other software? ``` # Steps to reproduce Add a new "Azure Cloud Shell" tab to your terminal instance. # Expected behavior A prompt should appear asking to authenticate with Azure. # Actual behavior The message "Could not connect to Azure. You may not have internet or the server might be down." appears immediately in the new tab. Fiddler only shows a single outgoing SSL initiation request to login.microsoftonline.com with a 200 response and no followup communication. I recently had to update the cacert bundle for the azure cli located in C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\Lib\site-packages\certifi\cacert.pem to include our corp proxy certificate which restored its functionality. Is there something similar here or should the terminal be using the windows store?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6422