Skip to main content

Microsoft

How to Configure ServiceNow Catalog Items for Microsoft Search

puzzle pieces, diversity, unique identitiy

If you are using ServiceNow as your IT service management platform, you might want to make your catalog items searchable in Microsoft Search. Microsoft Search is a unified search experience that helps you find what you need across your organization, including files, sites, people, and more. By connecting your ServiceNow catalog items to Microsoft Search, you can enable your users to find and request them directly from the Microsoft 365 apps.

In this blog post, we will show you how to configure ServiceNow catalog items as a data source for Microsoft Search using the Microsoft Graph connector. The Microsoft Graph connector for ServiceNow catalog items allows you to index your catalog items and their properties, such as name, description, category, and availability. You can also apply filters and refinements to your catalog items to make them more relevant and discoverable for your users.

To configure ServiceNow catalog items for Microsoft Search, you will need the following prerequisites:

  • A Microsoft 365 tenant with Microsoft Search enabled.
  • A ServiceNow instance with catalog items that you want to make searchable.
  • An admin account for both Microsoft 365 and ServiceNow.

Once you have the prerequisites, you can follow these steps to configure ServiceNow catalog items for Microsoft Search:

Step 1: Create a data source in Microsoft 365 Admin Center

The first step is to create a data source in the Microsoft 365 Admin Center that will connect to your ServiceNow instance and index your catalog items. To do this, follow these steps:

  • Go to Microsoft 365 Admin Center – https://admin.microsoft.com/
  • Navigate to “Settings” > Search & Intelligence > Data Sources
  • Click “Add”

Sc1

  • Click “ServiceNow”

Sc2

  • Select “ServiceNow Catalog”

Sc3

  • Fill out Name, Description, Display name, Upload logo

Sc4

  • Scroll down, Check the box under “Notice”, Click “Save and Proceed”

Sc5

Step 2: Configure the connection details and authentication

The next step is to configure the connection details and authentication for your ServiceNow instance. To do this, add the following information:

  • ServiceNow instance URL
  • Select the authentication type: ServiceNow OAuth
  • Client ID
  • Client Secret

Sc6

  • Click “Sign in”
  • You will see “Connection Successful” message
  • Select “Only people with access to this data Source” option

Sc7

Step 3: Configure the properties and query string

The third step is to configure the properties and query string for your catalog items. The properties are the metadata fields that will be indexed and displayed for your catalog items in Microsoft Search. The query string is the filter that will be applied to your catalog items to limit the scope of the data source. To do this, follow these steps:

  • Make sure you have all the needed properties in this section. You can add or remove properties as needed.
  • Apply the needed “Query string” to filter your data.

Sc9

  • Select “ME-ID” – If you choose Microsoft Entra ID as the type of identity source, the connector maps the Email IDs of users obtained from ServiceNow directly to UPN property from Microsoft Entra ID.

Sc10

  • Assign Property labels – You can assign semantic labels to your source properties. The properties on this page are pre-selected based on your data source, but you can change this selection if there’s a different property that is better suited for a particular label.

Sc11

  • Manage schema – You can set the search schema attributes to control the search functionality of each source property. A search schema helps determine what results display on the search results page and what information end users can view and access.

Search schema attributes include options to Query, Search, Retrieve, and Refine.

Sc13

Note: You can’t edit this once Connection is configured, so you will need to make properties refinable if you would like to have filters in Verticals. (I learned this the hard way by re-configuring the entire connection)

Sc12

Step 4: Configure the crawl schedule

The fourth step is to configure the crawl schedule for your data source. The crawl schedule determines how often your catalog items will be updated in Microsoft Search. You can choose between incremental crawl and full crawl. Incremental crawl will only index the changes since the last crawl, while full crawl will index all the catalog items in your data source. To do this, follow these steps:

  • Set the schedule for your Incremental Crawl and Full Crawl

Sc14

Sc15

Step 5: Review and publish your data source

The final step is to review and publish your data source. You can preview some of the catalog items that will be indexed and check the connection status. You can also publish your data source to a limited audience for testing purposes before making it available to everyone in your organization. To do this, follow these steps:

  • Here you can “Publish to limited audience” and add users names who can view ServiceNow Search Results in Microsoft Search

Sc16

Sc17

Congratulations! You have successfully configured ServiceNow catalog items for Microsoft Search. Now your users can find and request them from any Microsoft 365 app that supports Microsoft Search. You can also create custom verticals and result types to customize the search experience for your catalog items.

For more information, please refer to the Microsoft Graph connector documentation and the ServiceNow connector documentation.

Disclaimer: Parts of this blog post were generated with the help of artificial intelligence.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Nidhi Shah

Nidhi Shah is a Lead Technical Consultant at Perficient. She has experience working on large scale Microsoft 365 environments and Modern Workplace solutions including Microsoft Viva, SharePoint, Stream, Teams, PowerApps and Power Automate. She has 10+ years of experience in designing and delivering solutions on Microsoft based collaborative platforms.

More from this Author

Follow Us