Skip to content

Commit 4f1e0fc

Browse files
committed
AzS: Authenticate with keys refresh
1 parent 030491a commit 4f1e0fc

File tree

2 files changed

+0
-12
lines changed

2 files changed

+0
-12
lines changed

articles/search/search-security-enable-roles.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -223,12 +223,6 @@ To re-enable key authentication, set "disableLocalAuth" to false. The search ser
223223
224224
---
225225
226-
## Effects of multiple service principals
227-
228-
+ Each unique combination of service resource (index, indexer, skillsets and so forth) and service principal triggers an authorization check. These authorization checks can add up to 200 milliseconds of latency per request.
229-
230-
+ In rare cases where requests originate from a high number of different service principals, all targeting different service resources (indexes, indexers, and so forth), it's possible for the authorization checks to result in throttling. Throttling would only happen if hundreds of unique combinations of search service resource and service principal were used within a second.
231-
232226
## Next steps
233227
234228
> [!div class="nextstepaction"]

articles/search/search-security-rbac.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -606,12 +606,6 @@ To enable a Conditional Access policy for Azure AI Search, follow these steps:
606606
> [!IMPORTANT]
607607
> 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.
608608

609-
## Limitations
610-
611-
+ Role-based access control can increase the latency of some requests. Each unique combination of service resource (index, indexer, etc.) and service principal triggers an authorization check. These authorization checks can add up to 200 milliseconds of latency per request.
612-
613-
+ In rare cases where requests originate from a high number of different service principals, all targeting different service resources (indexes, indexers, etc.), it's possible for the authorization checks to result in throttling. Throttling would only happen if hundreds of unique combinations of search service resource and service principal were used within a second.
614-
615609
## Troubleshooting role-based access control issues
616610

617611
When developing applications that use role-based access control for authentication, some common issues might occur:

0 commit comments

Comments
 (0)