Skip to content

Commit 91ce6f9

Browse files
addressing feedback,correcting typos
1 parent 882b985 commit 91ce6f9

File tree

2 files changed

+8
-12
lines changed

2 files changed

+8
-12
lines changed

articles/search/search-blob-indexer-role-based-access.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Use a Blob indexer to ingest Rbac scopes metadata
2+
title: Use a Blob indexer to ingest RBAC scopes metadata
33
titleSuffix: Azure AI Search
44
description: Learn how to configure Azure AI Search indexers for ingesting Azure Role-Based Access (RBAC) metadata on Azure Blobs.
55
ms.service: azure-ai-search
@@ -9,11 +9,11 @@ author: vaishalishah
99
ms.author: vaishalishah
1010
---
1111

12-
# Use a Blob indexer to ingest Rbac scopes metadata
12+
# Use a Blob indexer to ingest RBAC scopes metadata
1313

1414
[!INCLUDE [Feature preview](./includes/previews/preview-generic.md)]
1515

16-
Starting in 2025-05-01-preview, you can now include Rbac scope alongside document ingestion in Azure AI Search and use those permissions to control access to search results.
16+
Starting in 2025-05-01-preview, you can now include RBAC scope alongside document ingestion in Azure AI Search and use those permissions to control access to search results.
1717

1818
You can use the push APIs to upload and index content and permission metadata manually see [Indexing Permissions using the push REST API](search-index-access-control-lists-and-rbac-push-api.md), or you can use an indexer to automate data ingestion. This article focuses on the indexer approach.
1919

@@ -27,9 +27,9 @@ The indexer approach is built on this foundation:
2727

2828
## Prerequisites
2929

30-
+ Microsoft Entra ID authentication and authorization. Services and apps must be in the same tenant. Role assignments are used for each authenticated connection.
30+
+ [Microsoft Entra ID authentication and authorization](https://learn.microsoft.com/en-us/entra/identity/authentication/overview-authentication). Services and apps must be in the same tenant. Role assignments are used for each authenticated connection.
3131

32-
+ Azure AI Search, any region, but you must have a billable tier (basic and higher) for managed identity support. The search service must be [configured for role-based access](search-security-enable-roles.md) and it must [have a managed identity (either system or user)](search-howto-managed-identities-data-sources.md).
32+
+ Azure AI Search, any region, but you must have a billable tier (basic and higher) see [Service limits](search-limits-quotas-capacity.md) for managed identity support. The search service must be [configured for role-based access](search-security-enable-roles.md) and it must [have a managed identity (either system or user)](search-howto-managed-identities-data-sources.md).
3333

3434
## Limitations
3535

@@ -39,9 +39,7 @@ The indexer approach is built on this foundation:
3939

4040
### Authorization
4141

42-
For indexer execution, your search service identity must have **Storage Blob Data Reader** permission.
43-
44-
If you're testing locally, you should also have a **Storage Blob Data Reader** role assignment. For more information, see [Connect to Azure Storage using a managed identity](search-howto-managed-identities-storage.md).
42+
For indexer execution, your search service identity must have **Storage Blob Data Reader** permission see [Connect to Azure Storage using a managed identity](search-howto-managed-identities-storage.md).
4543

4644
## Configure Azure AI Search for indexing permission filters
4745

@@ -52,9 +50,7 @@ Recall that the search service must have:
5250

5351
### Authorization
5452

55-
For indexer execution, the client issuing the API call must have **Search Service Contributor** permission to create objects, **Search Index Data Contributor** permission to perform data import, and **Search Index Data Reader** to query an index.
56-
57-
If you're testing locally, you should have the same role assignments. For more information, see [Connect to Azure AI Search using roles](search-security-rbac.md).
53+
For indexer execution, the client issuing the API call must have **Search Service Contributor** permission to create objects, **Search Index Data Contributor** permission to perform data import, and **Search Index Data Reader** to query an index see [Connect to Azure AI Search using roles](search-security-rbac.md).
5854

5955
## Indexing permission metadata
6056

articles/search/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -529,7 +529,7 @@ items:
529529
href: search-document-level-access-overview.md
530530
- name: Use security filters
531531
href: search-security-trimming-for-azure-search.md
532-
- name: Use ACLs
532+
- name: Use ACLs or RBAC scopes
533533
items:
534534
- name: Push document-level permissions to an index
535535
href: search-index-access-control-lists-and-rbac-push-api.md

0 commit comments

Comments
 (0)