How to unify a ServiceNow knowledge base with SharePoint and your CMS

To unify a ServiceNow knowledge base with SharePoint, a CMS and file shares, index every source into one enterprise search platform that captures each item's permissions, then put one search page and AI assistant on top. Articles stay in ServiceNow. The hard part is permissions, so choose a consultant who tests ServiceNow user criteria first.

The short answer

Connect the ServiceNow knowledge base, SharePoint, your CMS and your file shares to one enterprise search index, with each item's permissions captured when it is indexed. Then put a single search page, and later an AI assistant, on top of that index. Nothing moves out of ServiceNow. Authors keep publishing articles there, and the search layer finds them next to everything else.

The connector is rarely the hard part. The work is in the permissions, the content cleanup and the relevance tuning in two languages. That is also what separates a good consultant from a good demo.

Why ServiceNow knowledge ends up in its own silo

ServiceNow is often where IT and HR publish how-to articles, policies and fixes. The intranet sits in SharePoint or a CMS, and procedures live in file shares. Each system has its own search box, so employees must guess where an answer lives before they can find it. Many give up and open a ticket for something that was already documented.

An AI assistant does not fix this on its own. If it sees only part of the content, it answers from only part of the content.

Three ways to unify the sources

1. One central index. Connectors crawl each source into a single index, with metadata and permissions. One relevance model ranks everything together. This is the usual choice for an intranet.
2. Federated search. The search page queries each system live and merges the results. It avoids copying content, but it depends on the speed and search quality of every system. It fits sources you cannot index.
3. Content migration. You move the articles into one system. This makes sense only when you are already retiring a platform, and it is a content project more than a search project.

Our article on federated search architecture compares the first two options in more depth.

Permissions come first

ServiceNow controls who can read knowledge with user criteria, at the knowledge base level and at the article level, with "Can Read" and "Cannot Read" rules. Some instances also use script-based criteria. Your unified search must reproduce those rules exactly, or it will show restricted articles to the wrong people.

The vendors document real limits here:

• Microsoft 365 Copilot. The ServiceNow Knowledge connector evaluates knowledge base and article user criteria. Its default Simple flow cannot evaluate script-based criteria, and Microsoft says to use the Advanced flow for those. Microsoft also warns that HR-scoped knowledge bases need an extra role on the service account, or restricted HR articles can be indexed as visible to everyone.
• Glean. The ServiceNow connector reads advanced user criteria through a Scripted REST API and enforces permissions at query time.
• Coveo. Coveo imports item permissions at crawl time, an approach it calls early binding, so items a user cannot open are filtered out before results are built. Its ServiceNow source documentation states that ServiceNow permissions are only partially supported, so user criteria must be tested.

Whatever the platform, test with real accounts from different groups before launch, including HR and executive content. Our article on permission-aware enterprise search explains early binding and what to check.

Which platform can do it

Three options come up most often. Microsoft 365 Copilot and Microsoft Search use Copilot connectors, including one for ServiceNow knowledge, and fit organizations that work mostly in Microsoft 365. Glean is a work assistant with prebuilt connectors across workplace apps. Coveo is a search platform with native connectors for ServiceNow and SharePoint that can also serve your website and support portal.

Our Coveo vs Microsoft 365 Copilot vs Glean comparison explains when each one fits. For the wider approach, see search and discovery.

What to look for in a consultant

Large integrators and specialized firms can both do this work. Ask each one the same questions:

1. Do they start with an assessment? A good partner reviews sources, connectors, search logs and permissions before recommending a tool.
2. Can they explain ServiceNow user criteria? Ask how they will handle article-level rules, "Cannot Read" rules, script-based criteria and HR-scoped knowledge.
3. Will they test permissions with real accounts? Ask for the test plan, not a promise.
4. Are they neutral on the platform? A partner who sells only one product will recommend that product. Ask when they would advise against it.
5. Do they handle French and English? Bilingual relevance needs tuning and testing in both languages, on real queries.
6. Do they clean the content? Duplicate and outdated articles pollute results and AI answers.
7. Who owns search after launch? Search needs an owner. Ask how the partner will train yours.

How Sengo approaches it

Sengo rebuilds intranet search across SharePoint, ServiceNow and the CMS. Our intranet search assessment covers sources and connectors (SharePoint, ServiceNow, file shares and CMS content), whether search results and AI answers respect who can open each document, search logs in French and English, content hygiene, AI assistant readiness, and the options: native Microsoft search, Coveo or another platform, with a three-year cost view.

We are an official Coveo implementation partner with a former Coveo backend developer on the team, and we tell clients when Microsoft 365 Copilot or another tool fits better. See our smart intranet approach and our Coveo partner page.

Frequently asked questions

Do we need to move articles out of ServiceNow?

No. Connectors index articles where they are. Authors keep publishing in ServiceNow, and the index picks up changes on each crawl.

Can Microsoft 365 Copilot search our ServiceNow knowledge base?

Yes, through Microsoft's ServiceNow Knowledge Copilot connector. Check which permission flow fits your user criteria before you turn it on, and set access to "Only people with access to this data source".

Is federated search safer than a central index?

Not by default. Federated search relies on each system to filter results at query time. A central index with early binding filters results with permissions captured at crawl time. Both are safe only when they are configured and tested.

Should we hire a large integrator or a specialist?

Pick the team that will test your ServiceNow permissions, tune results in both languages and train your search owner. Hands-on search experience with your mix of sources matters more than size.

Where do we start?

Start with an inventory of sources, permissions and search logs. The intranet search assessment covers these and ends with options and a roadmap.

Start with an intranet search assessment

Sources & References

1. Deploy the ServiceNow Knowledge Copilot connector: Microsoft Learn
   learn.microsoft.com
2. Copilot connectors overview: Microsoft Learn
   learn.microsoft.com
3. ServiceNow connector overview: Glean documentation
   docs.glean.com
4. Management of security identities and item permissions: Coveo Platform
   docs.coveo.com
5. Add a ServiceNow source: Coveo Platform
   docs.coveo.com