# Connecting SailPoint and Microsoft SharePoint Online To connect SailPoint with Microsoft SharePoint Online, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. Select **Virtual Appliance**. A virtual appliance is a Linux-based virtual machine that connects to your sources and apps using SailPoint APIs, connectors, and integrations. For more information about configuring and deploying virtual appliances, refer to [SailPoint Virtual Appliances](). 4. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 5. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 6. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. Under **Connection Type**, select **Direct Connection** or **Flat File**. - **Direct Connection** - A direct connection fetches data from the **Virtual Appliance Cluster** you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the [Virtual Appliance Reference Guide](). - **Flat File** - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable. 5. If you selected **Direct Connection**, in **Virtual Appliance Cluster**, select the virtual appliance cluster that will be used as the application connector for the source. 6. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 7. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 8. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. In the **Virtual Appliance Cluster** dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to [SailPoint Virtual Appliances](). 4. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 5. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 6. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 7. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 8. Select **Save**. ## Connection Settings To configure a direct connection between the Microsoft SharePoint Online source and SailPoint, specify the authentication type and grant type. > [!NOTE] > > Microsoft recommends using JWT Certificate Credentials for authentication, as other grant types (Client Credentials, SAML Bearer Assertion, Refresh Token/Auth Code) are deprecated and will stop working after April 2, 2026. Use JWT Certificate Credentials for all new and existing source configurations. > [!NOTE] > > **JWT Certificate Credentials (Recommended)** > > The JWT Certificate Credentials method supports authentication based on a JWT assertion prepared from a certificate and private key. > > [![JWT Certificate Credentials]()]() > > 1. Select **JWT Certificate Credentials** from the **Grant Type** drop-down list. > 2. Enter the **Client ID** of the application registered in Microsoft Entra ID. For more information, refer to [Registering an Application Using the Azure AD Portal](). > 3. Enter the valid **Certificate** details of the source created on the SharePoint Online managed system. > 4. Enter the valid **Private Key** text that is used to sign the JWT assertion and the corresponding **Private Key Password**. For more information, refer to [Creating OAuth2.0 JWT Certificate Credentials](). > 5. Enter the SharePoint Online **Domain Name**. For example, `contoso.sharepoint.com`. > 6. In **Authentication Endpoint URL**, enter the URL that corresponds to the Microsoft Azure Active Directory authentication endpoint deployed on a national cloud. > > For example, for the US government, enter `https://login.microsoftonline.us`, or for China enter `https://login.partner.microsoftonline.cn`. > 7. Select **Save**. > [!NOTE] > > **Client Credentials (Deprecated)** > > Use the Client Credentials with the ID and Secret parameters. > > [![Client Credentials]()]() > > 1. Select **Client Credentials** from the **Grant Type** drop-down list. > 2. Enter the **Client ID** and **Client Secret** of the source created on the SharePoint Online managed system. For more information, refer to [Registering Application with OAuth Client Credentials from SharePoint Portal](). > 3. Enter the SharePoint Online **Domain Name**. For example, `contoso.sharepoint.com`. > 4. (*Optional*) In **Authentication Endpoint URL**, enter the URL that corresponds to the Microsoft Azure Active Directory authentication endpoint deployed on a national cloud. > > For example, for the US government, enter `https://login.microsoftonline.us`, or for China enter `https://login.accesscontrol.chinacloudapi.cn`. > 5. Select **Save**. > [!NOTE] > > **Refresh Token / Auth Code (Deprecated)** > > The Auth Code / Refresh Token grant type is a client credentials-based authentication protocol. In addition to client credentials, it uses a Refresh Token to authenticate. > > [![Refresh Token / Auth Code]()]() > > 1. Select **Refresh Token / Auth Code** from the **Grant Type** drop-down list. > 2. Enter the **Client ID** and **Client Secret** of the source created on the SharePoint Online managed system. For more information, refer to [Registering Application with OAuth Client Credentials from SharePoint Portal](). > 3. Enter the valid **Refresh Token** obtained after registering the app with the Azure Active Directory Portal. For more information, refer to [Generating a Refresh Token](). > 4. Enter the SharePoint Online **Domain Name**. For example, `contoso.sharepoint.com`. > 5. In **Authentication Endpoint URL**, enter the URL that corresponds to the Microsoft Azure Active Directory authentication endpoint deployed on a national cloud. > > For example, for the US government, enter `https://login.microsoftonline.us`, or for China enter `https://login.partner.microsoftonline.cn`. > 6. Select **Save**. > [!NOTE] > > **SAML Bearer Assertion (Deprecated)** > > The SAML Bearer Assertion method is password-based user authentication with ADFS environment. SAML assertion issued by ADFS after authentication is used to get the access token from the Azure Active Directory. > > [![SAML Bearer Assertion]()]() [![SAML Bearer Assertion]()]() > > 1. Select **SAML Bearer Assertion** from the **Grant Type** drop-down list. > 2. Enter the **Client ID** and **Client Secret** of the source created on the SharePoint Online managed system. For more information, refer to [Registering Application with OAuth Client Credentials from SharePoint Portal](). > 3. Enter the SAML **Username** and corresponding **Password** for SAML authorization. > 4. Enter the server URL for the **Authorization Endpoint**. > 5. Enter the **Request Body** details for the SAML Bearer assertion. For more information, refer to [SAML Request Body](). > 6. Enter the SharePoint Online **Domain Name**. For example, `contoso.sharepoint.com`. > 7. In **Authentication Endpoint URL**, enter the URL that corresponds to the Microsoft Azure Active Directory authentication endpoint deployed on a national cloud. > > For example, for the US government, enter `https://login.microsoftonline.us`, or for China enter `https://login.partner.microsoftonline.cn`. > 8. Select **Save**. ### OAuth 2.0 Authentication Methods The Microsoft SharePoint Online connector supports OAuth 2.0 authentication with the following grant types: > [!NOTE] > > Microsoft recommends using JWT Certificate Credentials for authentication, as other grant types (Client Credentials, SAML Bearer Assertion, Refresh Token/Auth Code) are deprecated and will stop working after April 2, 2026. Use JWT Certificate Credentials for all new and existing source configurations. - JWT Certificate Credentials *(Recommended)* - Refresh Token/Auth Code *(Deprecated)* - SAML Bearer Assertion *(Deprecated)* > [!NOTE] > > **JWT Certificate Credentials and Refresh Token/Auth Code** > > *Prerequisites* > > - Obtain the **Client ID** and **Client Secret** from Microsoft Entra ID by registering the application. For more information, refer to [Registering an Application Using the Azure AD Portal](). > > > **Note** > > > > It is mandatory to use the Global Admin and Admin of all Sites User in SharePoint Online to create the application in Microsoft Entra ID. > - If the grant type is **JWT**: > > The Certificate (self-signed or CA signed) must be uploaded and registered at the Azure Active Directory portal. To register the certificate with the Microsoft Identity Platform, complete the following: > > 1. Sign in to the **Azure Portal**. > 2. In the Azure app registrations for client application, select the client application. > 3. Select **Certificates & secrets**. > > Select **Upload certificate** and then select the certificate file that you want to upload. > 4. Select **Add**. > 5. Obtain the values for the following: > > - Private Key: The private key text file. > - Private Key Password: The password for the private key. > - Certificate: The text file of the same certificate that was uploaded to the Azure portal. > - If the grant type is **Refresh Token/Auth Code**, generate a refresh token. For more information, refer to [Generating a Refresh Token](). > > Assign the following required permissions to the application: > > 1. In the Azure Active Directory console of the registered app, select **API permissions**. > 2. Select **Add a permission**. > 3. On the **Request API permissions** page, a list of supported APIs is displayed. > > - **Microsoft Graph** is under the commonly used Microsoft API. > - **Azure Active Directory Graph** under supported Legacy API. > - **SharePoint** is under Microsoft API. > 4. Under **What type of permissions does your application require?**, select the permission type as **Delegated** or **Application**. See the following table for the type: > > | Permission | Type | Purpose | > | --- | --- | --- | > | **Microsoft GRAPH API** | | | > | Directory.ReadWrite.All | Delegated | Read, Update, and Delete Group
Add membership | > | Directory.AccessAsUser.All | Delegated | Change Password and Delete User | > | User.ReadWrite.All | Delegated | Read and Update any User | > | Group.ReadWrite.All | Delegated | Read and write all groups | > | GroupMember.ReadWrite.All | Delegated | Read and write group memberships | > | Sites.FullControl.All | Delegated | Have full control of all site collections | > | **SharePoint Online API** | | | > | AllSites.FullControl | Delegated | Have full control of all site collections | > | AllSites.Manage | Delegated | Read and write items and lists in all site collections | > | Sites.FullControl.All | Application | Have full control of all site collections | > | Sites.Search.All | Delegated | Run search queries as a user | > | User.ReadWrite.All | Delegated | Read and write user profiles | > | User.ReadWrite.All | Application | Read and write user profiles | > 5. Under **Select permissions**, select the required permissions. > 6. Select **Add permissions**. > 7. In **Grant consent**, select **Grant Admin Consent** for your configuration and directory. Select **Yes** when prompted in the pop-up dialog box. > [!NOTE] > > **SAML Bearer Assertion (Deprecated)** > > *Prerequisite* > > - Obtain the **Client ID** and **Client Secret** from Microsoft Entra ID by registering the application. For more information, refer to [Registering an Application Using the Azure AD Portal](). > > > **Note** > > > > It is mandatory to use the Global Admin and Admin of all Sites User in SharePoint Online to create the application in Microsoft Entra ID. > > Note the following: > > - The authentication user must be synchronized in Azure Active Directory. > - Assign the user the **User Administrator** permission role in Azure Active Directory. > > > **Note** > > > > It is mandatory to use the Global Admin and Admin of all Sites User in SharePoint Online to create the application in Azure Active Directory. > - You must enable the ADFS endpoint required to authenticate the user. > - The ADFS machine time zone must be in sync with Azure time zone, that is, UTC. > > Assign the following required permissions to the application: > > 1. In the Azure Active Directory console of the registered app, select **API permissions**. > 2. Select **Add a permission**. > 3. On the **Request API permissions** page, a list of supported APIs is displayed. > > - **Microsoft Graph** is under the commonly used Microsoft API. > - **Azure Active Directory Graph** under supported Legacy API. > - **SharePoint** is under Microsoft API. > 4. Under **What type of permissions does your application require?**, select the permission type as **Delegated** or **Application**. See the following table for the type: > > | Permission | Type | Purpose | > | --- | --- | --- | > | **Microsoft GRAPH API** | | | > | Directory.ReadWrite.All | Delegated | Read and write directory data | > | Group.Read.All | Delegated / Application | Read all groups | > | Group.ReadWrite.All | Delegated / Application | Read and write all groups | > | GroupMember.Read.All | Delegated / Application | Read group memberships | > | GroupMember.ReadWrite.All | Delegated / Application | Read and write group memberships | > | Sites.FullControl.All | Delegated / Application | Have full control of all site collections | > | Site.Manage.All | | | > | Site.Read.All | Delegated / Application | Read items in all site collections | > | Site.ReadWrite.All | Delegated / Application | Edit or delete items in all site collections | > | User.Invite.All | Application | Invite guest users to the organization | > | User.Read | Delegated | Sign in and read user profile | > | **SharePoint Online API** | | | > | AllSites.FullControl | Delegated | Have full control of all site collections | > 5. Under **Select permissions**, select the required permissions. > 6. Select **Add permissions**. > 7. In **Grant consent**, select **Grant Admin Consent** for your configuration and directory. Select **Yes** when prompted in the pop-up dialog box. ## Aggregation Settings Use the aggregation parameters to set up the aggregation of data from the managed sites. > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() [![Aggregation Settings]()]() 1. Enable **Manage All Sites** if you want to manage all the sites. 2. In **Include Site Collections**, enter the list of all the site collections that are to be managed. 3. In **Exclude Site Collections**, enter the list of all the site collections that are to be excluded. 4. Enter the **Page Size**. This is the number of objects to fetch in a single page for a Site Collection. The default size is 500. 5. Select **Save**. ## IQService Settings IQService is a native Windows service that enables SailPoint to participate in a Windows environment and access information only available through Windows APIs. It is a lightweight service that must be installed on any supported Windows Server that has connectivity to the target systems you want to manage in SailPoint. The IQService is used for the Before and After Script and connector rules for the Microsoft SharePoint Online connector. > [!NOTE] > > **Screenshot** > > [![IQService Settings]()]() #### Download IQService To download the IQService installation complete the following: 1. Select the **Download IQService** button. Download, install, and configure IQService by following the steps mentioned in the [Identity Security Cloud IQService Administrator's Guide]() for [Installing and Registering IQService](). > [!NOTE] > > **Screenshot** > > [![IQService configuration]()]() Configure the IQService details: 1. (*Optional*) In the **IQService Host** field, enter the host name or IP address of the system where IQService is installed. 2. (*Optional*) Enter the **IQService Port** number used to connect. If you enable TLS, configure the corresponding IQService TLS port. The default is 5050. 3. (*Optional*) Enter the **IQService User** for client authentication. 4. (*Optional*) Enter the **IQService Password** for the IQService user. 5. (*Optional*) Select **Enable Transport Layer Security (TLS)** if the connection is over TLS. For more information, refer to [IQService: TLS and client authentication configuration for Identity Security Cloud](). 6. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation.