Share via

Synapse Worspace Connectivity Error.

Rangarajan Subramani 90 Reputation points Microsoft Employee
2026-04-01T08:58:35.66+00:00

I am getting this connectivity error in my Synapse Workspace "Code NetworkError Message Request failed due to network issues." I checked VNET configuration and VPN Connection. Everything seems to be in order. When I asked Copilot, I got the below response. "Engage your Windows / Security team with this statement:

“SCHANNEL TLS cipher suites do not include ECDHE + AES‑GCM required by Azure Synapse”"

Azure Synapse Analytics
Azure Synapse Analytics

An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.

0 comments

Answer recommended by moderator

Rangarajan Subramani 90 Reputation points Microsoft Employee
2026-04-07T12:24:40.8833333+00:00

This issue is resolved. My laptop had Global Secure Access Private Channel enabled. Once I disabled that, I was able to connect to my Synapse workspace instance. @Manoj Kumar Boyini

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Manoj Kumar Boyini 14,665 Reputation points Microsoft External Staff Moderator
    2026-04-01T10:33:41.9433333+00:00

    Hi @Rangarajan Subramani

    To further isolate the “NetworkError – Request failed due to network issues” observed in Synapse Studio (Access Control / Role assignments), we recommend the following steps. These checks help determine whether the issue is related to client‑side network, firewall, proxy, or security policies.

    1. Run Azure Synapse Connectivity Checker
      Please run the Microsoft‑provided connectivity validation script from the affected machine and share the output.

    GitHub repository: https://github.com/microsoft/Azure-Synapse-Connectivity-Checker?tab=readme-ov-file#execution-

    Instructions:

    • Run the script using PowerShell ISE or elevated PowerShell
    • Execute it from the same machine and network where the issue is observed
    • This script validates connectivity to all required Synapse endpoints (Studio, Dev endpoint, SQL, and Azure Resource Manager)

    This will help confirm whether any required endpoint, port, or TLS connection is being blocked.

    1. Test from an Alternate Network (Without VPN)

    To determine whether the issue is specific to the corporate network or proxy, please try accessing Synapse Studio from:

    • A mobile hotspot or home network
    • Without connecting to the corporate VPN

    If the issue does not occur on an alternate network, it strongly indicates a corporate network, firewall, proxy, or TLS inspection dependency.

    1. Collect a Browser HAR Trace (If Issue Persists)

    If the issue still occurs after the above steps, please collect a HAR (HTTP Archive) trace while reproducing the issue in Synapse Studio and share it with us.

    Reference documentation: https://learn.microsoft.com/en-us/azure/azure-portal/capture-browser-trace

    This trace helps identify:

    Which request is failing
    Whether the failure is due to SSL/TLS handshake, proxy reset, or blocked endpoint

    Please let us know once the above checks are completed, and share the results so we can proceed with the next steps.

    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.