Skip to content

Commit 75f7a0a

Browse files
authored
Update search-indexer-troubleshooting.md
Updating title since this is related to Azure Active Directory conditional access policies (not SharePoint access policies). This applies for SharePoint indexer
1 parent f5fbbb0 commit 75f7a0a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/search/search-indexer-troubleshooting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: gimondra
99
ms.service: cognitive-search
1010
ms.custom: ignite-2022
1111
ms.topic: conceptual
12-
ms.date: 12/01/2022
12+
ms.date: 04/04/2023
1313
---
1414

1515
# Indexer troubleshooting guidance for Azure Cognitive Search
@@ -82,7 +82,7 @@ If your SQL database is on a [serverless compute tier](/azure/azure-sql/database
8282

8383
If the database is paused, the first login from your search service will auto-resume the database, but it will also return an error stating that the database is unavailable with error code 40613. After the database is running, retry the login to establish connectivity.
8484

85-
## SharePoint Conditional Access policies
85+
## Azure Active Directory Conditional Access policies
8686

8787
When creating a SharePoint indexer you will go through a step that requires you to sign in to your Azure AD app after providing a device code. If you receive a message that says `"Your sign-in was successful but your admin requires the device requesting access to be managed"` the indexer is likely being blocked from accessing the SharePoint document library due to a [Conditional Access](../active-directory/conditional-access/overview.md) policy.
8888

0 commit comments

Comments
 (0)