Azure Synapse studio 403 issue when public network disabled

Gopisetty, Srikanth (External) 20 Reputation points
2024-06-05T14:15:11.8866667+00:00

We have created azure synapse studio with public access disabled and we have created private end points for synapse workspace with private link hub to access web synapse. but still we are getting 403 forbidden error while opening synapse web UI.

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.
4,597 questions
Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
483 questions
Accepted answer
  1. Sina Salam 6,341 Reputation points
    2024-06-05T22:30:30.32+00:00

    Hello Gopisetty, Srikanth (External),

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    Problem

    I understand that you are having 403 forbidden error while opening synapse web UI. After you have created azure synapse studio with public access disabled and we have created private end points for synapse workspace with private link hub to access web synapse.

    Solution

    When encountering a 403 Forbidden error while trying to access the Synapse web UI, it typically indicates an issue with permissions or network configurations. To some extent it might have many reasons beyond normal.

    To get the root of the incident, check the diagnostic logs in Azure Synapse and any related logs in your Azure environment for more detailed error messages and use Azure Monitor to gather more insights about the connection attempts and potential issues for specific solution.

    However, I will provide you with possibility diagnosis that can solve the issue in a normal scenario:

    1. Ensure that the private endpoints for your Synapse workspace are correctly set up.
    2. Check that the DNS configuration is correctly resolving the private endpoint.
    3. Verify that the Network Security Groups (NSGs) associated with your private endpoints allow inbound traffic from your IP address or subnet.
    4. Ensure that the firewall settings on your Synapse workspace are correctly configured to allow access from your private endpoints.
    5. Ensure that the user account you are using has the necessary permissions to access the Synapse workspace.
    6. Check role assignments in Azure Synapse and ensure the user has at least the Synapse Administrator or Synapse Contributor role.
    7. Ensure that your DNS is correctly configured to resolve the private link FQDN to the private IP address of the private endpoint.
    8. If you are accessing the Synapse workspace from a VNet, ensure that the VNet integration is correctly configured.
    9. Check the VNet peering settings if your Synapse workspace and the accessing resources are in different VNets.
    10. Verify that the private link service has been approved and is in a Connected state.

    If you could check through these lists, the problem should be solved and if not get back with more log report for best solution.

    Accept Answer

    I hope this is helpful! Do not hesitate to let me know if you have any other questions.

    ** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful ** so that others in the community facing similar issues can easily find the solution.

    Best Regards,

    Sina Salam

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. PRADEEPCHEEKATLA-MSFT 83,886 Reputation points Microsoft Employee
    2024-06-06T05:25:02.3333333+00:00

    @Gopisetty, Srikanth (External) - Thank for the question and using MS Q&A platform.

    This article - Disabling Public Network Access in Synapse helps to resolve the issue.

    And also Watch this video to learn how to disable public network access.

    Hope this helps. Do let us know if you any further queries.

    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.

    0 comments