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,

[davitvoski]

Hey team, will update the solution in a bit, worked with ServiceNow to solve this issue by opening a ticket

[Spencer Speas]

Hi @davitvoski  I am having the same issue implementing the Sharepoint online search connector, and am very relieved to see your post here and that you have a resolution. Please do share the fix you found with ServiceNow! I have had much trouble building this integration, and your post is a light in the dark

[davitvoski]

Hey Spencer,
first question is your SharePoint connection working?
Second question could you check the sites you are trying to index, what is the permission on them and how users are given access to them? Is it via "Everyone except external users" site permissions. This was the main issue on our end, as this is not supported with the current integration and I assume most sites are kind of done with that permission (was the case in our scenario).

[Spencer Speas]

@davitvoski My connection appears to be working, the UI page for connection validation passes all checks besides the REST Connection Alias (current: "MicrosoftSharePointOnline", expected: "MicrosoftSharepointOnline"). My oAuth connections all work properly to generate tokens.

In my case, the Sharepoint External Search table (sn_sp_con_sharepoint_external_search) for AI search is not populating, but the metadata table (sn_sp_con_sharepoint_file_meta_data) is populating properly. Was this the case for you, before fixing the integration?

As for the site permissions, would that require configuration in Sharepoint itself or only the Azure application with permissions to access Sharepoint? I've attached a screenshot of my Azure application's Authentication tab, which is what I think you're talking about.

Thanks again for the help here - hoping to have this up soon! 

[davitvoski]

Our connection was also working as expected but the issue was with those perimissions as it wasn't getting the "groups" for the ais_external_search_user_mapping_data_source_m2m
You would need to configure for the sites themselves and not the azure application.

As for sn_sp_con_sharepoint_external_search table, from my understanding it will not populate it. It does not store the files that are gotten inside the table. The table is just used for mapping purposes to map the fields gotten to a ServiceNow field for example a SharePoint Description to a ServiceNow Description. It won't show any actual records.