Workspace sgs-workspace is not accessible Failed to retrieve this workspace. subscriptions/88ddafdc-c7ea-4fdd-9a7b-45ecb2fe1271/resourcegroups/MPA-Synapse-prod-ausoutheast-001/providers/Microsoft.Synapse/workspaces/sgs-workspace

Jason Hofmann 0 Reputation points

Failed to load one or more resources due to no response.

  • Pipeline
  • Data flow
  • Trigger
  • Credential
  • Linked service
  • Lake databases
  • Synapse KQL scripts
  • SQL script
  • Apache Spark configuration

Please refresh or troubleshoot the connectivity issue.

Learn more

Code

NetworkError

Message

Request failed due to network issues.

  • Session ID ab7df8572a934d14a0ceb046f72170c1
  • Resource ID Not available
  • Extension HubsExtension
  • Content ResourceMenuBlade
  • Error code --
0 comments No comments
Sign in to comment

2 answers

  1. Pratyush Vashistha 5,135 Reputation points • Microsoft External Staff • Moderator

    Hey Jason,

    It looks like you're facing an issue with accessing your Azure Synapse Analytics workspace, and you're getting a NetworkError due to failed resource retrieval. Here are a few things you can check to troubleshoot this connectivity issue:

    Public Network Access Settings: Make sure that your workspace's public network access settings are configured correctly. If public access is required, ensure that it is enabled. If access is limited, check that your client IP address is listed in the Azure Synapse workspace firewall settings. You can learn more about configuring firewall rules here.

    Network Dependencies: Confirm that there are no network dependencies or blocks that could be preventing access to your workspace. This includes checking whether necessary endpoints, such as Managed Virtual Networks or Private Endpoints, are correctly set up.

    Subscription Status: Ensure that your subscription is active and registered for Microsoft.Synapse. You can verify the status in the Azure portal.

    Error Codes: Given that you received a message related to "Request failed due to network issues," ensure your client IP is not being blocked. The error code 403 usually indicates that public access is denied.

    If the above steps don't resolve the issue, here are some follow-up questions to help further diagnose the problem:

    • Are there any recent changes made to firewall rules or network configurations for your Synapse workspace?
    • Have you checked the Azure portal for any active network security groups or policies that might affect access?
    • Can you confirm whether your subscription is correctly set up and registered for Azure Synapse services?
    • Do you have a client IP that might be varying or changing, affecting firewall rule matches?

    Hopefully, this helps you get closer to resolving the issue! If you have any more details or questions, feel free to share.

    References:

    Note: This content was drafted with the help of an AI system.

    If this answers your query, do click UpVoteandYes` for was this answer helpful. And, if you have any further query do let us know.

    Thanks

    Pratyush

    1. Manoj Kumar Boyini 16,895 Reputation points • Microsoft External Staff • Moderator

      Hi Jason Hofmann,

      I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

    2. Anonymous

      Hi Jason Hofmann,

      Following up to see if the given answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    Sign in to comment

  2. AI answer

    It seems you are experiencing a connectivity issue with your Azure Synapse workspace, which is resulting in the error message indicating that the workspace is not accessible. This could be due to several reasons, including network issues or permissions problems.

    Here are some steps you can take to troubleshoot the issue:

    1. Check Permissions: Ensure that you have the required permissions to access the workspace. You can do this by navigating to your Synapse workspace in the Azure portal, going to Access control (IAM), and checking your access level.
    2. Network Configuration: Verify that your network allows outgoing connections to the necessary ports for Azure Synapse. Ensure that TCP ports 80, 443, and 1443 are open, and that your local firewall settings are not blocking access.
    3. Browser Issues: Sometimes, browser-related issues can cause connectivity problems. Try clearing your browser's cookies and cached data, using private mode, or switching to a different browser.
    4. Resource Availability: Ensure that the resources you are trying to access (such as pipelines, data flows, etc.) are available and have not been deleted or moved.
    5. Session and Network Status: If you see a network error, check your internet connection and try refreshing the page. If the issue persists, it might be worth trying from a different network or device to rule out local network issues.

    If these steps do not resolve the issue, you may need to open a support ticket with Azure for further assistance.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer