Skip to content

Commit 8fdd29d

Browse files
committed
Tab layout for configure access
1 parent 20de409 commit 8fdd29d

File tree

1 file changed

+16
-6
lines changed

1 file changed

+16
-6
lines changed

articles/search/search-agentic-retrieval-how-to-pipeline.md

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Use one of the following chat completion models with your AI agent:
4747

4848
### Package version requirements
4949

50-
We recommend the following package versions during this preview period. See the [`requirements.txt`](https://github.com/Azure-Samples/azure-search-python-samples/blob/main/agentic-retrieval-pipeline-example/requirements.txt) file for more packages used in the example solution.
50+
Use a package version that provides preview functionality. See the [`requirements.txt`](https://github.com/Azure-Samples/azure-search-python-samples/blob/main/agentic-retrieval-pipeline-example/requirements.txt) file for more packages used in the example solution.
5151

5252
```
5353
azure-ai-projects==1.0.0b11
@@ -59,7 +59,11 @@ azure-search-documents==11.6.0b12
5959

6060
Before you begin, make sure you have permissions to access content and operations. We recommend Microsoft Entra ID authentication and role-based access for authorization. You must be an **Owner** or **User Access Administrator** to assign roles. If roles aren't feasible, you can use [key-based authentication](search-security-api-keys.md) instead.
6161

62-
On Azure AI Search:
62+
Configure access to each resource identified in this section.
63+
64+
### [**Azure AI Search**](#tab/search-perms)
65+
66+
Azure AI Search provides the agentic retrieval pipeline. Configure access for yourself, your app, and your search service for downstream access to models.
6367

6468
1. [Enable role-based access](search-security-enable-roles.md).
6569
1. [Configure a managed identity](search-howto-managed-identities-data-sources.md).
@@ -69,19 +73,25 @@ On Azure AI Search:
6973

7074
+ For integrated operations, ensure that all clients using the retrieval pipeline (agent and tool) have **Search Index Data Reader** role assignments for sending retrieval requests.
7175

72-
On Azure AI Foundry:
76+
### [**Azure AI Foundry**](#tab/foundry-perms)
77+
78+
Azure AI Foundry hosts the AI agent and tool. Permissions are needed to create and use the resource.
7379

7480
+ You must be an **Owner** of your Azure subscription to create the project and resource.
7581

7682
+ For local testing, you must be an **Azure AI User** to access chat completion models deployed to the Foundry resource. This assignment is conferred automatically for **Owners** when you create the resource. Other users need a specific role assignment. For more information, see [Role-based access control in Azure AI Foundry portal](/azure/ai-foundry/concepts/rbac-azure-ai-foundry).
7783

7884
+ For integrated operations, ensure your [search service identity](search-howto-managed-identities-data-sources.md) has an **Azure AI User** role assignment on the Foundry resource.
7985

80-
On Azure OpenAI:
86+
### [**Azure OpenAI**](#tab/openai-perms)
8187

82-
1. For local testing, ensure that you have a **Cognitive Services User** role assignment to access the chat completion model and embedding models (if using).
88+
Azure OpenAI hosts the models used by the agentic retrieval pipeline. Configure access for yourself and for the search service.
8389

84-
1. For integrated operations, ensure your [search service identity](search-howto-managed-identities-data-sources.md) has a **Cognitive Services User** role assignment for model access.
90+
+ For local testing, ensure that you have a **Cognitive Services User** role assignment to access the chat completion model and embedding models (if using).
91+
92+
+ For integrated operations, ensure your [search service identity](search-howto-managed-identities-data-sources.md) has a **Cognitive Services User** role assignment for model access.
93+
94+
---
8595

8696
## Development tasks
8797

0 commit comments

Comments
 (0)