Connecting SailPoint and Databricks
To connect SailPoint with Databricks, 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:
- Sign in to SailPoint.
- Go to Admin > Connections > Sources.
- Select Create New.
- Search for the connector by entering the name in the search box, and then select Configure.
- In the Source Name field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
- 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.
- 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.
- (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.
- 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.
- 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.
- Enter a unique name and description for the source.
-
In the Source Owner dropdown list, select the identity that owns this source.
- To find a source owner, begin entering their name.
-
(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.
-
Configure the authentication to allow SailPoint to connect to the source. Refer to Connection Settings for more information.
-
(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.
-
(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.
-
-
Select Save.
Connection Settings
This section contains the information that the source uses to connect to and authenticate with the Databricks managed system. After you select Connection Settings the following page is displayed.
The source supports the following authentication types:
- Databricks M2M
- Microsoft Entra
Configuring the Account Host
Complete these steps for every authentication type.
- Select the Cloud Type for your Databricks cloud provider. The source uses the standard account host for that cloud unless you select Use Vanity Account URL.
- (Optional) Select Use Vanity Account URL if the Databricks account uses a custom domain. Authentication still uses the standard account host for the selected Cloud Type.
-
If you selected Use Vanity Account URL, enter the HTTPS URL for the custom domain in Vanity Account URL, such as
https://company.azuredatabricks.net. Do not include a path or a trailing slash.Important
The source uses the vanity account URL for account and workspace API calls only. Allow network access to both the custom domain and the standard Databricks account host for the selected Cloud Type.
Configuring Databricks M2M or Microsoft Entra Authentication
- Select Databricks M2M or Microsoft Entra as the Authentication Type.
- Select a Grant Type for OAuth authentication. The default value is Client Credentials.
- If you use Microsoft Entra authentication, enter the Tenant ID for your Microsoft Entra ID (Azure AD) tenant.
- Enter the Client ID for the Service Principal. The Service Principal must have permissions to manage users, groups, and workspaces.
- Enter the Client Secret for the Service Principal.
- Enter the Account ID of your Databricks account. You can find this in your account console URL or account settings. For more information, refer to Prerequisites.
- Enter the Metastore ID to govern all workspaces within the Unity Catalog metastore.
- Select Save.
Workspace Settings
Configure workspace filtering to control which workspaces are included in aggregation and provisioning flows. If filtering is disabled, all workspaces attached to the metastore will be included.
- Enable Filter Workspaces to filter workspaces by ID.
- Select a Workspace Filter Type to include or exclude the specified workspaces.
- Enter the Workspace IDs to include or exclude. Press Enter after each ID to add it to the list.
- Select Save.
Aggregation Settings
Enable to aggregate Unity Catalog Data Object Privileges. When enabled, select the specific object types to include:
- Catalog: Aggregate privileges for catalog-level objects.
- Schema: Aggregate privileges for schema-level objects.
- Table: Aggregate privileges for table-level objects.
- Volume: Aggregate privileges for volume-level objects.
- Function: Aggregate privileges for function-level objects.
Important
- In the Edit Account and Entitlement Schema, select Include permissions in aggregations before you proceed with aggregation.
- If the specified workspace is unreachable, Unity Catalog privileges will not be included during aggregation. If you do not provide a workspace ID, the connector will randomly select a workspace ID during aggregation.
Default Workspace
Provide the specific default workspace ID for fetching Unity Catalog level privileges within the current Metastore. The connector uses the corresponding workspace host or Fully Qualified Domain Name to perform the fetch operations.
Workspace Bound Data Object Privileges
Select Workspace Bound Data Object Privileges to aggregate data object privileges that are bound to workspaces.
Data Object Owner
Select Include Data Object Owner in Privilege to aggregate ownership information for Unity Catalog securable objects. When enabled, the source fetches the owner for each data object.
Additional Settings
In the Page Size field, enter the number of records to aggregate in a single page when iterating over large datasets. The value can range from 1 to 100. The default is 100.
Agent Governance Settings
Select Enable Databricks Agents to include Databricks Agents in aggregation. Select Save to apply changes.
Important
Agent aggregation is only supported for workspace based agent.
Review and Test
Perform a test to confirm the connection to SailPoint.
- Go to Review and Test.
-
Confirm that the entries in each field are correct.
If you note any mistakes, return to the section and make corrections.
-
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.
Documentation Feedback
Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.






