Merge pull request #1772 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-ai-docs (branch main)

Author: Taojunshen

articles/machine-learning/how-to-custom-dns.md

@@ -290,8 +290,8 @@ The following table shows example IPs from Azure US Government regions:
 
 | FQDN | IP Address |
 | ----- | ----- |
-| `52882c08-ead2-44aa-af65-08a75cf094bd.workspace.chinaeast2.api.ml.azure.us` | `10.1.0.5` |
-| `52882c08-ead2-44aa-af65-08a75cf094bd.workspace.chinaeast2.cert.api.ml.azure.us` | `10.1.0.5` |
+| `52882c08-ead2-44aa-af65-08a75cf094bd.workspace.usgovvirginia.api.ml.azure.us` | `10.1.0.5` |
+| `52882c08-ead2-44aa-af65-08a75cf094bd.workspace.usgovvirginia.cert.api.ml.azure.us` | `10.1.0.5` |
 | `ml-mype-plt-usgovvirginia-52882c08-ead2-44aa-af65-08a75cf094bd.usgovvirginia.notebooks.usgovcloudapi.net` | `10.1.0.6` |
 | `*.usgovvirginia.inference.ml.azure.us` | `10.1.0.7` |
 

articles/search/search-indexer-troubleshooting.md

@@ -38,7 +38,7 @@ There are two options for allowing indexers to access these resources in such an
 * Configure an inbound rule for the IP address of your search service and the IP address range of `AzureCognitiveSearch` [service tag](/azure/virtual-network/service-tags-overview#available-service-tags). Details for configuring IP address range restrictions for each data source type can be found from the following links:
 
   * [Azure Storage](/azure/storage/common/storage-network-security#grant-access-from-an-internet-ip-range)
-  * [Azure Cosmos DB](/azure/storage/common/storage-network-security#grant-access-from-an-internet-ip-range)
+  * [Azure Cosmos DB](/azure/cosmos-db/how-to-configure-firewall)
   * [Azure SQL](/azure/azure-sql/database/firewall-configure#create-and-manage-ip-firewall-rules)
 
 * As a last resort or as a temporary measure, disable the firewall by allowing access from **All Networks**.