Skip to content

Commit 7a1a70d

Browse files
Merge pull request #226887 from Danzhang-msft/patch-8
Update how-to-connect-to-workspace-from-restricted-network.md
2 parents e1774d5 + ddc2348 commit 7a1a70d

File tree

2 files changed

+22
-2
lines changed

2 files changed

+22
-2
lines changed

articles/synapse-analytics/security/how-to-connect-to-workspace-from-restricted-network.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: danzhang
66
ms.service: synapse-analytics
77
ms.topic: how-to
88
ms.subservice: security
9-
ms.date: 02/15/2022
9+
ms.date: 02/09/2023
1010
ms.reviewer: sngun
1111
---
1212

@@ -111,6 +111,24 @@ After you create this endpoint, the approval state shows a status of **Pending**
111111

112112
Now, all set. You can access your Azure Synapse Analytics Studio workspace resource.
113113

114+
## Step 6: Allow URL through firewall
115+
116+
Following URLs must be accessible from client browser after enabling Azure Synapse private link hub.
117+
118+
Required for auth:
119+
- `login.microsoftonline.com`
120+
- `aadcdn.msauth.net`
121+
- `msauth.net`
122+
- `msftauth.net`
123+
- `graph.microsoft.com`
124+
- `login.live.com`, though this may be different based on account type.
125+
126+
Required for workspace/pool management:
127+
- `management.azure.com`
128+
- `{workspaceName}.[dev|sql].azuresynapse.net`
129+
- `{workspaceName}-ondemand.sql.azuresynapse.net`
130+
131+
114132
## Appendix: DNS registration for private endpoint
115133

116134
If the "Integrate with private DNS zone" is not enabled during the private endpoint creation as screenshot below, you must create the "**Private DNS zone**" for each of your private endpoints.

articles/synapse-analytics/security/synapse-private-link-hubs.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,9 @@ There are two steps to connect to Synapse Studio using private links. First, you
2222
## Azure Private Links Hubs and Azure Synapse Studio
2323
You can use a single Azure Synapse private link hub resource to privately connect to all your Azure Synapse Analytics workspaces using Azure Synapse Studio. The workspaces do not have to be in the same region as the Azure Synapse Private link hub. The Azure Synapse Private link hub resource can also be used for connections to Synapse workspaces in different subscriptions or Azure AD tenants.
2424

25-
You can create your private link hub by searching for *Synapse private link hubs* in the Azure portal and selecting **Azure Synapse Analytics (private link hubs)** from Services. Follow the steps in the guide for how to [connect to workspace resources from a restricted network](./how-to-connect-to-workspace-from-restricted-network.md) for details.
25+
You can create your private link hub by searching for *Synapse private link hubs* in the Azure portal and selecting **Azure Synapse Analytics (private link hubs)** from Services. Follow the steps in the guide for how to [connect to workspace resources from a restricted network](./how-to-connect-to-workspace-from-restricted-network.md) for details. Certain URLs must be accessible from the client browser after enabling Azure Synapse private link hub. For more information, see [Connect to workspace resources from a restricted network](how-to-connect-to-workspace-from-restricted-network.md).
26+
27+
2628

2729
>[!NOTE]
2830
>Private link hubs are intended for securely loading the static content Synapse Studio over private links. You must create **separate, private endpoints** to the resources you wish to connect to within the workspace, such as provisioned/dedicated SQL pools, or Spark pools.

0 commit comments

Comments
 (0)