AI Search SharePoint Integration Issues - Indexed content won't show up

[davitvoski]

Hey team,

I am having troubles integrating AI Search with SharePoint. I have successfully created all configuration by following the documentation for azure and servicenow:
1. https://docs.servicenow.com/bundle/vancouver-integrate-applications/page/administer/integrationhub-s...
2. https://docs.servicenow.com/bundle/vancouver-employee-service-management/page/product/sharepoint-onl...

On my first attempt to launching the SharePoint Connector, it was successful however no sites/sub sites where showing as being indexed.

So I deleted it and retried and This got me to the point where I launched the SharePoint Connector again and got it to the complete state with some sites being indexed and some not indexed.

I have than configured the EVAMs for us to be able to view the share point searches and have configured the Search Profile and Search Application appropriately to include SharePoint as one of its indexed sources. We are using the default CSP Search Application and Search Profile for our portal.

However, after doing all the configuration mentioned in the docs with successfully having launched and completed the SharePoint Connector, we are still not able to see any articles on the share point tab on the portal.

Thank you for any help you can provide,

[Spencer Speas]

Do I have this right?

•  sn_sp_con_sharepoint_user_mapping table was not populating, therefore not populating ais_external_search_user_mapping_data_source_m2m
  • This was due to permissions on sites and subsites you wanted indexed, having the Sharepoint sites configured to allow "Everyone except external users"
    
• Changing permissions on each of the sites you wanted indexed to something other than "Everyone except external users", then reindexing brought you the result you wanted. 

On the second thing you mentioned, "sn_sp_con_sharepoint_external_search" is never populated with any records. My search index is using this table - do I need to change my search index after fixing the above, or should I expect AI search to work despite it shows "0 records" in the table?

Thank you again for the help here - many of the microsoft <> SNow integrations seem to be bleeding edge. 

[Brian Bakker]

@davitvoski 

Sorry for not responding.I'm pleased it was resolved by ServiceNow Support in the case that you rightly created. Can you let us know the solution, or the case ID where it was resolved, as I would like to create a knowledge article on this, as others are experiencing similar issues with this implementation.

Many thanks,

Brian

[davitvoski]

Hey @Brian Bakker, 

The main issue was resolved, and I will share the ID with you once it is fully resolved.

[svani]

Hi @Brian Bakker 

Please help here if any KA created for this issue i am facing same issue .

Thanks in advance

[Brian Bakker]

We updated our documentation Setting up the SharePoint Online Search Connector, which is being deprecated in Yokohama, as we will introduce a better framework to connect to external sources. For the time being, please follow this documentation for setting up the connector, and Index sites for search