Skip to content

Configuration steps

Configuration steps

The process of setting up a Sharepoint Online Library Data Intake Process involves several key actions. The different sections of the input form are organized into these main steps:

Step 1. Configure Data Intake Process

Please see on the common Sidra connector plugins section about the parameters needed to configure a Data Intake Process.

Step 2. Configure Provider

Please see on the common Sidra connector plugins section about the parameters needed to create a new Provider.

Step 3. Configure Data Source

The data source represents the connection to the Sharepoint online library. A Data Source abstracts the details of creating a Linked Service in Azure Data Factory. The fields required in this section are the following:

  • Choose an Integration Runtime to use.
  • Site URL: this is the URL of the SharePoint Online site including the library name where the files are hosted. For example, https://contoso.sharepoint.com/sites/siteName/LibraryName.
  • Tenant ID: The tenant ID under which your application resides. You can find it from Azure portal Active Directory overview page.
  • Service Principal ID: The tenant ID under which your application resides. You can find it from Azure portal Active Directory overview page.
  • Service Principal key: The tenant ID under which your application resides. You can find it from Azure portal Active Directory overview page.

Sidra connector plugin for Sharepoint online library will register this new data source in Sidra Metadata and deploy a Linked Service in Azure Data factory with this connection. Default value for Integration Runtime is AutoResolveIntegrationRuntime.

For more details on Linked Services check the Data Factory documentation.

Step 4. Configure Metadata Extractor

Sidra connector plugin for Sharepoint online library creates the needed metadata and orchestrates the data integration. To configure this, several fields are required:

  • Destination Path: The storage destination path where the Please choose one from the list of available Azure Search pipeline templates. A new pipeline of the selected type will be created to configure the full file indexing and ingestion. files from the Sharepoint library will be deposited. See section Destination paths and scope of ingestion automation and Entities mapping for details about this field.
  • Type of Azure Search pipeline to deploy: A pickup field from a list of available Azure Search pipeline templates. A new pipeline of the selected type will be created to configure the full file indexing and ingestion.
  • Entities mapping fields: Entity Name, Source Path, Filter Expression and Format. See section Entities mapping for details about these fields.

Step 5. Configure Trigger

Please see on the common Sidra connector plugins section about the parameters needed to set up a trigger.