Skip to content

Commit 64fea18

Browse files
Adjusted naming to Azure Cosmos DB account
1 parent 4dbe6f1 commit 64fea18

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/how-to-configure-vnet-service-endpoint.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -356,8 +356,8 @@ NSG rules are used to limit connectivity to and from a subnet with virtual netwo
356356
### Are service endpoints available for all VNets?
357357
No, Only Azure Resource Manager virtual networks can have service endpoint enabled. Classic virtual networks don't support service endpoints.
358358

359-
### When should I "Accept connections from within public Azure datacenters" for a Cosmos account?
360-
This setting should only be enabled when you want your Azure Cosmos DB account to be accessible to any Azure service in any Azure region. Other Azure first party services such as Azure Data Factory and Azure Cognitive Search provide documentation for how to secure access to data sources including Cosmos accounts, for example:
359+
### When should I "Accept connections from within public Azure datacenters" for an Azure Cosmos DB account?
360+
This setting should only be enabled when you want your Azure Cosmos DB account to be accessible to any Azure service in any Azure region. Other Azure first party services such as Azure Data Factory and Azure Cognitive Search provide documentation for how to secure access to data sources including Azure Cosmos DB accounts, for example:
361361

362362
* [Azure Data Factory Managed Virtual Network](../data-factory/managed-virtual-network-private-endpoint.md)
363363
* [Azure Cognitive Search Indexer access to protected resources](../search/search-indexer-securing-resources.md)

0 commit comments

Comments
 (0)