After Intel IT image with Azure integration, My Azure Storage Account log-in become always Failure

[Timdaway]

Error Details as below , Kindly need your help
Thx

{
"name": null,
"message": ""{\n \"name\": \"Node Fetch Error\",\n \"message\": \"Connect Timeout Error (attempted address: management.azure.com:443, timeout: 10000ms)\",\n \"stack\": \"ConnectTimeoutError: Connect Timeout Error (attempted address: management.azure.com:443, timeout: 10000ms)\\n at onConnectTimeout (C:\\\\Users\\\\timdaway\\\\AppData\\\\Local\\\\Programs\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\out\\\\app\\\\index.js:62:28280)\\n at Immediate._onImmediate (C:\\\\Users\\\\timdaway\\\\AppData\\\\Local\\\\Programs\\\\Microsoft Azure Storage Explorer\\\\resources\\\\app\\\\out\\\\app\\\\index.js:62:27716)\\n at process.processImmediate (node:internal/timers:504:21)\",\n \"cause\": {},\n \"code\": \"UND_ERR_CONNECT_TIMEOUT\"\n}""
}

[Timdaway]

BTW, my old IT machine (since 3~4 years ago) which Intel IT image didn't integrate with Azure, then my Azure Storage Account log-in still working properly
Any insight or OS configuration suggestion for me ?

[craxal]

Thanks for reporting this. The error shows that Storage Explorer is timing out when trying to connect to management.azure.com:443. This is most likely caused by network policy changes introduced by the Intel IT image -- such as a proxy, firewall rule, or SSL inspection -- that are blocking outbound HTTPS connections to Azure endpoints.

A few things to try:

1. In Storage Explorer, go to Edit > Proxy Settings and check whether you need to configure a proxy to reach the internet.
2. Verify you can reach management.azure.com from a browser or command line on the same machine.
3. Check with your IT department whether the image introduced any network restrictions for Azure traffic.

If adjusting proxy settings doesn't help, your IT team will need to allow outbound access to management.azure.com (port 443).