search mobile facets autocomplete spellcheck crawler rankings weights synonyms analytics engage api customize documentation install setup technology content domains user history info home business cart chart contact email activate analyticsalt analytics autocomplete cart contact content crawling custom documentation domains email engage faceted history info install mobile person querybuilder search setup spellcheck synonyms weights engage_search_term engage_related_content engage_next_results engage_personalized_results engage_recent_results success add arrow-down arrow-left arrow-right arrow-up caret-down caret-left caret-right caret-up check close content conversions-small conversions details edit grid help small-info error live magento minus move photo pin plus preview refresh search settings small-home stat subtract text trash unpin wordpress x alert case_deflection advanced-permissions keyword-detection predictive-ai sso

OneDrive Connector Guide

Ingest all of your OneDrive files into Enterprise Search.

The OneDrive Connector requires that you create an OAuth App within OneDrive.


First, sign in to and click on Azure Active Directory:

OneDrive - Accessing Azure Active Directory.
Azure active directory is a busy place. The picture indicates the Azure Active Directory link highlighted in the left-hand sidebar. It's in the bottom third of the menu items.

Next, click on App Registrations:

OneDrive - Registering an app.
App registrations is also in a busy menu, but now the menu is nested. It's in the top third. The image has it highlighted.

Then New Registration:

OneDrive - Registering a new application.
Clicking into app registration reveals a sort of table. There are three menu items at the top. The first is new registration and it has a plus sign icon.

Give your App a name - like "Enterprise Search" - and make it Multitenant; the middle option.

If your app is left as single tenant, it will not be able to access the appropriate APIs.

Leave the "redirect URIs" blank for now.

We will need two - one for Organizational Sources and the other for Personal Sources - so we'll add this as another step.

Finally, hit the Register button.

OneDrive - Clicking that good ol' button.
The image shows the above fields filled in with text. It's a standard form. The register button is blue. A sort of corporate-y blue. It isn't too stimulating or energetic.

Retrieve the Client ID - we'll need it within Enterprise Search.

Next, add two redirect URIs.

Click the Add Redirect URIs link in the header:

OneDrive - Adding a pair of redirect URIs.
The next image reveals a set of values. It's quite busy, but the image indicates via pink circles that the Application (client) id is the key that we want. In a table next to the client id there is a button to add redirect URIs. It might be tricky to tab to.

The two redirect URIs are:

  1. http://localhost:3002/ent/sources/one_drive/create
  2. http://localhost:3002/ent/org/sources/one_drive/create

Remember: the hostname must be relative to your own hostname.

If you are also using Sharepoint, you can add all four redirects.

Once you've added them both, press that sweet Save button in the upper left.

OneDrive - Save us.
The save icon is at the top of the form table. It has a disk icon. The redirect URIs are entered into typical fields.

Now let's get ourselves the Client Secret, so we have everything we need to configure the connector in Enterprise Search.

Navigate to Certificates & Secrets:

OneDrive - Keep it secret. Keep it safe.
Certificates and secrets is in list of links in a subnav. The image shows it highlighted.

Pick a name for your client secret, like Enterprise Search.

Select "never" as the expiration date, then give that Add button a click:

OneDrive - Never expire.
Another nested form. Fill it in as suggested then click Add. Another blue button. This one isn't too moving, either.

Now secure your Client Secret value before you leave this screen.

Keep this secret!

A few more things to do...

OneDrive - API Permissions.
The warning at the top of the page is highlighted. It reminds you to keep the key secret. The key itself is also highlighted. It's at the bottom of the page.

We must set up the permissions the Application will request from the Admin.

Navigate to API Permissions and click Add Permission.

Add "delegated" permissions until the list resembles the one below:

OneDrive - A set of permissions.
The API permissions item is nested under the certificates & secrets item. Once clicked, a button is also revealed to add permission at the top of another table.

If you are also using Sharepoint, OneDrive uses the same permissions.

Finally, at the bottom of the page click Grant admin consent for [YOUR_ORG_NAME].

That's it for OneDrive!

For the final steps, you must return back to Enterprise Search.

Login to Enterprise Search.

Within the administrative dashboard, click Settings on the sidebar.

Navigate to Content Source Connectors:

OneDrive - Click Sources within the sidebar.
A picture of the sidebar within the administrative dashboard. The item

Select the OneDrive Connector and click Connect.

Fill in the Client ID and Client Secret then click Save Changes.

OneDrive Connector, created!

Click Settings if you ever need to change tokens or remove the Connector.

Now, click Sources within the sidebar.

OneDrive - Click Sources within the sidebar.
A picture of the sidebar within the administrative dashboard. The item

Click Add under the OneDrive source.

First, you'll need to click I understand.

Why the hurdle? We want to make it clear that you're adding a public source.

All of its contents will be accessible by those with the right permissions.

If you're comfortable with that, click the button.

You'll then be presented with an OAuth screen from OneDrive.

Once you accept, you have added OneDrive as a content source to your organization.

Congratulations! It's time to search.

You can now make the source available to various groups and scale its relevance priority.

Enjoying the beta? Something broken? Lost? Please send us your feedback or visit the Enterprise Search community.