Skip to content

Commit 2aa3c1b

Browse files
authored
Merge pull request #76622 from jjgriff93/patch-2
Add note for analytical store private dns zone
2 parents 7d04068 + 2c072a1 commit 2aa3c1b

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/cosmos-db/analytical-store-private-endpoints.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ ms.author: anithaa
1414

1515
In this article, you will learn how to set up managed private endpoints for Azure Cosmos DB analytical store. If you are using the transactional store, see [Private endpoints for the transactional store](how-to-configure-private-endpoints.md) article. Using [managed private endpoints](../synapse-analytics/security/synapse-workspace-managed-private-endpoints.md), you can restrict network access of your Azure Cosmos DB analytical store, to a Managed Virtual Network associated with your Azure Synapse workspace. Managed private endpoints establish a private link to your analytical store.
1616

17+
> [!NOTE]
18+
> If you are using Private DNS Zones for Cosmos DB and wish to create a Synapse managed private endpoint to the analytical store sub-resource, you must first create a DNS zone for the analytical store (`privatelink.analytics.cosmos.azure.com`) linked to your Cosmos DB's virtual network.
19+
1720
## Enable a private endpoint for the analytical store
1821

1922
### Set up Azure Synapse Analytics workspace with a managed virtual network

0 commit comments

Comments
 (0)