Skip to main content
Microsoft SharePoint Logo

​
Microsoft SharePoint

Document management and collaboration platform

✅ Ready📝 Documentation Available

​
Overview

SharePoint is a web-based collaborative platform developed by Microsoft. It’s primarily used for document management and storage, acting as a secure place where teams can store, organize, share, and access information from almost any device.

​
Key Functions of SharePoint

  • Intranets & Team Sites: Serves as a centralized intranet and a secure digital space for team collaboration and internal communication.
  • Document Management: Offers secure storage, version control, and organization for all documents and files.
  • Content & Data Tracking: Allows users to create custom lists (e.g., tasks, contacts, issues) and manage company data.
  • Workflow Automation: Enables the building of simple custom applications and forms to automate business processes.
The SharePoint connector uses OAuth 2.0 with Application Permissions via Microsoft Entra ID (formerly Azure AD), granting it the ability to execute background, server-to-server operations on SharePoint sites, lists, and documents without an interactive user sign-in.

​
Configuration Setup

​
Step 1: Register Application in Azure Portal

Sign in to Azure Portal:
  • Navigate to portal.azure.com and sign in with your Microsoft 365 administrator account
Access App Registrations:
  • Search for “App registrations” in the top search bar
  • Or navigate to Microsoft Entra ID → App registrations
Create New Registration:
  • Enter application details:
    • Name: Enter app name (e.g., “PipesHub Connector”)
    • Supported account types: Select “Accounts in this organizational directory only (Single tenant)”
    • Select a platform: Web
    • Redirect URI: Leave blank
  • Click “Register”
SharePoint
Single-tenant configuration ensures the application only works within your organization for better security.

​
Step 2: Copy Application Credentials

After registration, you’ll see the Overview page. Copy the following values (you’ll need these later):
  • Application (client) ID: Found under “Essentials” section
  • Directory (tenant) ID: Found under “Essentials” section
SharePoint Application Credentials
Copy the “Application (client) ID” NOT the “Object ID”. These are different values.

​
Step 3: Configure API Permissions

Configure Microsoft Graph Permissions:
  • On the overview page, click on Manage > API Permissions
  • Click Add a permission
  • Select Microsoft Graph
  • Choose Application permissions (not Delegated permissions) and add the following:
    • User.Read.All
    • GroupMember.Read.All
    • Group.Read.All
    • Files.ReadWrite.All
    • Reports.Read.All
    • Sites.FullControl.All
    • Member.Read.Hidden
Configure SharePoint Permissions:
  • Click Add a permission and select SharePoint
  • Choose Application permissions and add the following:
    • Sites.FullControl.All
  • Click Add permissions
  • On the API permissions page, click “Grant admin consent for [Your Organization]”
  • Confirm by clicking “Yes”
  • Wait for the status to show green checkmarks
SharePoint Admin Consent Page
Important: The administrator granting consent should use the same email address as the PipesHub account configuring this connector. Using a different email will cause permission issues on the PipesHub platform.
Admin consent is required for application permissions. Only Global Administrators or Application Administrators can grant this consent.

​
Step 5: Setup Certificate & Secret

Install OpenSSL:OpenSSL is installed by default on Linux and OS X terminals. If you are using Windows, follow these instructions:
  • Download the relevant OpenSSL installation manager for your version of Windows. OpenSSL offers a list of third-party binary distributions, with Shining Light Productions as an option.
  • During the installation process, select the option to copy the OpenSSL binaries into the /bin directory.
  • Open a new PowerShell instance. In PowerShell, you can run the following command to make use of OpenSSL binaries:
$env:Path += ";C:\\Program Files\\OpenSSL-Win64\\bin"
Generate Certificate and Private Key:Run the following commands line by line. Microsoft SDK requires the certificate to be verified with a private key in PKCS#8 syntax:
openssl genrsa -out tempprivatekey.key 2048
openssl pkcs8 -topk8 -inform PEM -outform PEM -in tempprivatekey.key -out privatekey.key -nocrypt
openssl req -new -key privatekey.key -out request.csr
openssl x509 -req -days 365 -in request.csr -signkey privatekey.key -out certificate.crt
Verify Certificate Files:Verify that both certificate.crt and privatekey.key exist. Open each file, and ensure the files conform to the following formats:
  • The certificate file must start with BEGIN CERTIFICATE and end with END CERTIFICATE
  • The private key should begin with BEGIN PRIVATE KEY and end with END PRIVATE KEY. It must not include RSA in the headers, nor be encrypted.
Upload to PipesHub:
  • Upload the certificate.crt in PipesHub under Client Certificate
  • Upload the privatekey.key in PipesHub under Private Key
Uploading certificate and private key in PipesHub
Upload Certificate to Azure:
  • Navigate back to Microsoft Entra ID > Manage > App registrations and click on the app you created earlier
  • Click Manage > Certificates & secrets
  • Click the Certificates section and Upload certificate
  • Upload the certificate.crt file that you generated
  • After uploading, the application must now list the new certificate
Uploading certificate to Azure App

​
FAQ

There are three common causes:
  1. Email mismatch - The email used during connector authentication doesn’t match your PipesHub account email. This causes permission issues preventing you from accessing synced data.
    • Fix: Reconfigure the connector and authenticate using the same email as your PipesHub account.
  2. Records show in “All Records” but not in search - Documents display in the All Records section but don’t appear in search query results.
    • Fix: Verify sync filters in the connector settings and ensure indexing has completed. Check that the data matches your search query criteria.
  3. Data not yet indexed - The connector is still syncing or hasn’t completed the initial indexing process.
    • Fix: Go to Settings > Connectors, check the sync status, and wait for indexing to complete.
Yes. When creating a SharePoint connector, the admin has the option to apply filters and select specific SharePoint sites for indexing. This allows you to limit the scope of indexed content to only the sites that are relevant to your organization’s needs.
Yes. You can achieve this by following these steps:
  1. Create a dedicated connector instance — Create a SharePoint connector instance for the site that contains the subfolders you want to index.
  2. Select Manual Indexing — When configuring the connector, choose the Manual Indexing option. This gives you granular control over which content gets indexed.
  3. Select the SharePoint site — Use the filters to select the specific SharePoint site that contains the subfolders you want to index.
  4. Navigate to specific folders — Go to All Records in the navigation bar, then browse to the specific files or folders you want to index within the selected SharePoint site.
This approach gives you full control over exactly which subfolders and files are indexed from each SharePoint site.