Skip to content

Commit bbb3a2d

Browse files
Merge pull request #263678 from aahill/az-sku
specifying Azure AI Search sku
2 parents fc56577 + ecf66c6 commit bbb3a2d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/ai-services/openai/how-to/use-your-data-securely.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: azure-ai-openai
88
ms.topic: how-to
99
author: aahill
1010
ms.author: aahi
11-
ms.date: 11/29/2023
11+
ms.date: 01/19/2024
1212
recommendations: false
1313
---
1414

@@ -117,6 +117,8 @@ To allow access to your Azure OpenAI service from your client machines, like usi
117117

118118
## Configure Azure AI Search
119119

120+
You can use basic pricing tier and higher for the configuration below. You don’t have to use S2 pricing tier because the configuration doesn't require [private endpoint support for indexers with a skill set](/azure/search/search-limits-quotas-capacity#shared-private-link-resource-limits). See [step 8](#data-ingestion-architecture) of the data ingestion architecture diagram. The networking for custom skill is *bypass trusted service*, not *private endpoint*.
121+
120122
### Enable managed identity
121123

122124
To allow your other resources to recognize the Azure AI Search using Microsoft Entra ID authentication, you need to assign a managed identity for your Azure AI Search. The easiest way is to toggle on the system assigned managed identity in the Azure portal.

0 commit comments

Comments
 (0)