Skip to content

Commit 3e769d5

Browse files
authored
Update analytical-store-private-endpoints.md
1 parent 1a9e226 commit 3e769d5

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

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

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,6 @@ In this article, you will learn how to set up managed private endpoints for Azur
1717
> [!NOTE]
1818
> If you are using Private DNS Zones for Azure 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 Azure Cosmos DB's virtual network.
1919
20-
> [!NOTE]
21-
> Synapse Link for API for Gremlin is now in preview. You can enable Synapse Link in your new or existing graphs using Azure CLI. For more information on how to configure it, click [here](configure-synapse-link.md).
22-
23-
> [!NOTE]
24-
> Synapse Link for API for Gremlin is now in preview. You can enable Synapse Link in your new or existing graphs using Azure CLI. For more information on how to configure it, click [here](configure-synapse-link.md).
25-
26-
2720
## Enable a private endpoint for the analytical store
2821

2922
### Set up Azure Synapse Analytics workspace with a managed virtual network and data-exfiltration

0 commit comments

Comments
 (0)