Microsoft SharePoint Legacy Connector Deployment Overview

Deprecated

The following procedure outlines the steps needed to deploy the Microsoft SharePoint Legacy connector. The steps indicate the order in which you must perform configuration tasks in Microsoft SharePoint and CES.

1. Validate that your environment meets the requirements (see Microsoft SharePoint Legacy Connector Requirements).

2. Identify if the SharePoint environment you want to index is a Classic, Claims, or Online type (see Identifying Your SharePoint Environment).

3. On your SharePoint farm (tenant in SharePoint Online):

   1. Select or create a user that the Legacy connector will use to crawl your SharePoint content. The type of user depends on the type of SharePoint environment (see Type of User to Specify for the User Identity).

   2. Grant appropriate SharePoint permissions to the crawling account you selected (see Granting SharePoint Permissions to the Crawling Account).

   3. For on-premises environments, install the Coveo web service, search box, and search interface on your SharePoint farm (see Installing the Coveo Web Service, Search Box, and Search Interface into SharePoint).

      Note: With this installation procedure, you can also integrate the Coveo search box to SharePoint. This is not needed to deploy the Legacy connector and can be done later.

4. On the Coveo Master server, in the Administration Tool:

   1. Configure the user identity

      Once the crawling account has been set up, you must create a CES user identity for this account (see Adding a User Identity).

   2. When indexing SharePoint Online content, you must install the Windows Azure AD module on the Coveo Master server because it is needed by the Office 365 security provider (see Installing the Windows Azure AD Module for Windows PowerShell).

   3. Determine which security providers are required for your SharePoint environment (see Security Providers to Use).

      Create the required ones:

      • Creating a Claims Security Provider for an On-Premises SharePoint

      • Creating a Claims Security Provider for SharePoint Online

      • Creating an Office 365 Security Provider for SharePoint Online

      • Creating a Security Provider for the SharePoint Legacy Connector

   4. Configure and index the Microsoft SharePoint source

      The Coveo Legacy connector needs to know details about your Microsoft SharePoint server or farm (tenant in SharePoint Online) to be able to index its content (see Configuring and Indexing a Microsoft SharePoint Source With the Legacy Connector).

5. When you provide a Coveo .NET search interface residing outside SharePoint and want users to be able to find Claims-secured SharePoint content without having to log in again to SharePoint, configure the search interface to manage single sign-on (see Manually Configuring a .NET Search Interface Claims SSO for an On-Premises SharePoint).