Azure AiSearch indexer creation for sharepoint link issue

Styve Jerry NDE TCHINDA 0 Reputation points
2025-01-23T16:29:01.9166667+00:00

Hello dear community,

I'm trying to create an Indexer in Azure Cognitive Search service that's linked to a sharepoint library. But, it's not being created, it does not appear in my indexer list in azure Aisearch. on the creation of the index and the indexer i receive the "200 OK" notificaton on postman, on the "statuts" call i also get "200 OK". But when i try to visualize my indexer, it is not dislpayed despite having the "200 OK" on "statuts" call. But i can visualize my index(not indexer) in azure. i have the "404 not found" when i use the "run" function. could you please help me with that issue please ?

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
1,170 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Laxman Reddy Revuri 2,315 Reputation points Microsoft Vendor
    2025-01-24T11:39:56.4166667+00:00

    Hi @Styve Jerry NDE TCHINDA
    Thanks for the question and using MS Q&A platform.
    Looks like you're having trouble with the indexer not showing up in Azure Cognitive Search, even though you're getting "200 OK" responses when creating and checking its status.

    1.Make sure there are no Conditional Access policies blocking the indexer from accessing the SharePoint document library. If you see a message saying the device needs to be managed, you might need to tweak your Conditional Access policies in the Azure portal.

    2.Check that the account used to create the indexer has the right permissions to access the SharePoint site and library. It might help to create a new organizational user account with the exact permissions needed for the indexer.

    3.Ensure the indexer is set up correctly to point to the right data source and that the data source is accessible.

    The "404 not found" error when using the "run" function might mean the indexer wasn't created successfully, even if you got "200 OK" responses. Double-check the indexer creation process and make sure all required fields and configurations are set correctly. If these steps don't fix the issue, it might be useful to consult Azure's documentation or support for more help.

    References:
    Index data from SharePoint document libraries.

    Indexer troubleshooting guidance for Azure AI Search.
    Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.