Skip to content

Commit f2f3793

Browse files
authored
Update search-document-level-access-overview.md
Correcting typo
1 parent 6cfb995 commit f2f3793

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/search/search-document-level-access-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ You can use the [REST API](/rest/api/searchservice/operation-groups) or supporte
3131
If you're using ADLS Gen2 as your data source, [Azure AI Search's built-in indexer](search-indexer-access-control-lists-and-role-based-access.md) simplify data ingestion. This indexer pulls ACLs and RBAC roles at container level during the data ingestion process, enabling a low/no-code workflow for managing document-level permissions.
3232

3333
#### Enforcing document-level permissions at query time
34-
With native [token-based querying](https://aka.ms/azs-query-preserving-permissions), Azure AI Search validates a user's [Microsoft Entra token](/Entra/identity/devices/concept-tokens-microsoft-Entra-id) to enforce ACLs and RBAC roles automatically. This functionality helps trim result sets to include only documents the user is authorized to access. You can achieve this by attaching the user's Microsot Entra token to your query request.
34+
With native [token-based querying](https://aka.ms/azs-query-preserving-permissions), Azure AI Search validates a user's [Microsoft Entra token](/Entra/identity/devices/concept-tokens-microsoft-Entra-id) to enforce ACLs and RBAC roles automatically. This functionality helps trim result sets to include only documents the user is authorized to access. You can achieve automatic trimming by attaching the user's Microsoft Entra token to your query request.
3535

3636

3737
### 2. Security trimming via filters

0 commit comments

Comments
 (0)