Skip to content

Commit c492586

Browse files
Merge pull request #271914 from mattgotteiner/matt/rbac-auth-update
Update RBAC auth documentation
2 parents 9e24e95 + e4d92e3 commit c492586

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

articles/search/search-security-rbac.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -356,7 +356,7 @@ If you're already a Contributor or Owner of your search service, you can present
356356

357357
## Grant access to a single index
358358

359-
In some scenarios, you may want to limit application's access to a single resource, such as an index.
359+
In some scenarios, you might want to limit an application's access to a single resource, such as an index.
360360

361361
The portal doesn't currently support role assignments at this level of granularity, but it can be done with [PowerShell](../role-based-access-control/role-assignments-powershell.md) or the [Azure CLI](../role-based-access-control/role-assignments-cli.md).
362362

@@ -500,7 +500,10 @@ The PowerShell example shows the JSON syntax for creating a custom role that's a
500500

501501
## Disable API key authentication
502502

503-
API keys can't be deleted, but they can be disabled on your service if you're using the Search Service Contributor, Search Index Data Contributor, and Search Index Data Reader roles and Microsoft Entra authentication. Disabling API keys causes the search service to refuse all data-related requests that pass an API key in the header.
503+
Key access, or local authentication, can be disabled on your service if you're using the Search Service Contributor, Search Index Data Contributor, and Search Index Data Reader roles and Microsoft Entra authentication. Disabling API keys causes the search service to refuse all data-related requests that pass an API key in the header.
504+
505+
> [!NOTE]
506+
> Admin API keys can only be disabled, not deleted. Query API keys can be deleted.
504507

505508
Owner or Contributor permissions are required to disable features.
506509

@@ -565,3 +568,10 @@ To enable a Conditional Access policy for Azure AI Search, follow the below step
565568

566569
> [!IMPORTANT]
567570
> If your search service has a managed identity assigned to it, the specific search service will show up as a cloud app that can be included or excluded as part of the Conditional Access policy. Conditional Access policies can't be enforced on a specific search service. Instead make sure you select the general **Azure AI Search** cloud app.
571+
572+
## Troubleshooting role-based access control issues
573+
574+
When developing applications that use role-based access control for authentication, some common issues might occur:
575+
576+
* If the authorization token came from a [managed identity](/entra/identity/managed-identities-azure-resources/overview) and the appropriate permissions were recently assigned, it [might take several hours](/entra/identity/managed-identities-azure-resources/managed-identity-best-practice-recommendations#limitation-of-using-managed-identities-for-authorization) for these permissions assignments to take effect.
577+
* The default configuration for a search service is [key-based authentication only](#configure-role-based-access-for-data-plane). If you didn't change the default key setting to **Both** or **Role-based access control**, then all requests using role-based authentication are automatically denied regardless of the underlying permissions.

0 commit comments

Comments
 (0)