Skip to content

Commit 8dbca21

Browse files
committed
Addressed blocking issue
1 parent 89a3c0e commit 8dbca21

4 files changed

+4
-4
lines changed

articles/search/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@
231231
- name: Connect through private endpoints
232232
href: search-indexer-howto-access-private.md
233233
- name: Connect to a SQL managed instance private endpoint
234-
href: search-indexer-how-to-access-private-endpoint-sql-mi.md
234+
href: search-indexer-how-to-access-private-sql.md
235235
- name: Data encryption
236236
items:
237237
- name: Customer-managed keys

articles/search/search-index-azure-sql-managed-instance-with-managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Before learning more about this feature, it is recommended that you have an unde
3131

3232
To assign read permissions on SQL Managed Instance, you must be an Azure Global Admin with a SQL Managed Instance. See [Configure and manage Azure AD authentication with SQL Managed Instance](/azure/azure-sql/database/authentication-aad-configure) and follow the steps to provision an Azure AD admin (SQL Managed Instance).
3333

34-
* [Configure a public endpoint and network security group in SQL Managed Instance](search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers.md) to allow connections from Azure Cognitive Search. If your Azure SQL Managed Instance is configured for private connections, [create a shared private link](search-indexer-how-to-access-private-endpoint-sql-mi.md) in Cognitive Search to allow the connection.
34+
* [Configure a public endpoint and network security group in SQL Managed Instance](search-howto-connecting-azure-sql-mi-to-azure-search-using-indexers.md) to allow connections from Azure Cognitive Search. If your Azure SQL Managed Instance is configured for private connections, [create a shared private link](search-indexer-how-to-access-private-sql.md) in Cognitive Search to allow the connection.
3535

3636
## 1 - Assign permissions to read the database
3737

articles/search/search-indexer-howto-access-private.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 02/22/2023
1616

1717
If you have an Azure PaaS resource that has a private connection enabled through [Azure Private Link](../private-link/private-link-overview.md), you'll need to create a *shared private link* to reach those resources from Azure Cognitive Search. This article walks you through the steps for creating, testing, and managing a private link.
1818

19-
If you're setting up a private connection to a SQL Managed Instance, see [this article](search-indexer-how-to-access-private-endpoint-sql-mi.md) instead.
19+
If you're setting up a private connection to a SQL Managed Instance, see [this article](search-indexer-how-to-access-private-sql.md) instead.
2020

2121
## When to use a shared private link
2222

@@ -80,7 +80,7 @@ You can create a shared private link for the following resources.
8080

8181
<sup>3</sup> The `Microsoft.Web/sites` resource type is used for App service and Azure functions. In the context of Azure Cognitive Search, an Azure function is the more likely scenario. An Azure function is commonly used for hosting the logic of a custom skill. Azure Function has Consumption, Premium and Dedicated [App Service hosting plans](../app-service/overview-hosting-plans.md). The [App Service Environment (ASE)](../app-service/environment/overview.md) and [Azure Kubernetes Service (AKS)](../aks/intro-kubernetes.md) aren't supported at this time.
8282

83-
<sup>4</sup> See [Create a shared private link for a SQL Managed Instance](search-indexer-how-to-access-private-endpoint-sql-mi.md) for instructions.
83+
<sup>4</sup> See [Create a shared private link for a SQL Managed Instance](search-indexer-how-to-access-private-sql.md) for instructions.
8484

8585
### Private endpoint verification
8686

0 commit comments

Comments
 (0)