# Connecting SailPoint and Microsoft Azure DevOps

To connect SailPoint with Azure DevOps, 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 **Configure**.
5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
6. 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.
7. 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](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
8. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
9. 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](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
10. 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. (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](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information.
5. (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](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
6. (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.
7. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the Azure DevOps source based on the selected **Grant Type**.

> [!NOTE]
>
> For existing sources, with added Grant Type field in UI, please select the correct one and save the configuration whether you wish to continue to existing or switch to new Grant Type.

Select one of the following **Grant Types** based on your requirements:

- **Personal Access Token** - for PAT-based authentication
- **Client Credentials** - for client-secret-based authentication
- **JWT Certificate Credentials** - for JWT client certificate assertion-based authentication

> [!NOTE]
>
> **Personal Access Token**
>
> > **Screenshot**
> >
> > [![Connection Settings - Personal Access Token](<https://documentation.sailpoint.com/connectors/microsoft/azure_devops/saas/help/img/connection_settings_pat.png>)](<https://documentation.sailpoint.com/connectors/microsoft/azure_devops/saas/help/img/connection_settings_pat.png>)
>
> 1. In the **Grant Type** dropdown list, select **Personal Access Token**.
> 2. Enter the **Base URL** for the Azure DevOps system. SailPoint recommends using HTTPS for a secured connection.
> 3. Enter the **Organization Name** of the Azure DevOps organization.
> 4. Enter the **Personal Access Token** (PAT) generated in the source. For more information, refer to [Prerequisites](<https://documentation.sailpoint.com/connectors/microsoft/azure_devops/saas/help/index.html#prerequisites>).
> 5. Select **Save**.

> [!NOTE]
>
> **Client Credentials**
>
> > **Screenshot**
> >
> > [![Connection Settings - Client Credentials](<https://documentation.sailpoint.com/connectors/microsoft/azure_devops/saas/help/img/connection_settings_client_credentials.png>)](<https://documentation.sailpoint.com/connectors/microsoft/azure_devops/saas/help/img/connection_settings_client_credentials.png>)
>
> 1. In the **Grant Type** dropdown list, select **Client Credentials**.
> 2. Enter the **Base URL** for the Azure DevOps system. SailPoint recommends using HTTPS for a secured connection.
> 3. Enter the **Organization Name** of the Azure DevOps organization.
> 4. In the **Client ID** field, enter the Microsoft Entra ID application Client ID that has access to the Azure DevOps organization.
> 5. In the **Client Secret** field, enter the Microsoft Entra ID application Client Secret value that has access to the Azure DevOps organization.
> 6. In the **Domain Name** field, enter the name of the Microsoft Entra ID domain to be managed. For example, `contoso.onmicrosoft.com`.
> 7. Select **Save**.

> [!NOTE]
>
> **JWT Certificate Credentials**
>
> > **Screenshot**
> >
> > [![Connection Settings - JWT Certificate Credentials](<https://documentation.sailpoint.com/connectors/microsoft/azure_devops/saas/help/img/connection_settings_jwt_certificate.png>)](<https://documentation.sailpoint.com/connectors/microsoft/azure_devops/saas/help/img/connection_settings_jwt_certificate.png>)
>
> 1. In the **Grant Type** dropdown list, select **JWT Certificate Credentials**.
> 2. Enter the **Base URL** for the Azure DevOps system. SailPoint recommends using HTTPS for a secured connection.
> 3. Enter the **Organization Name** of the Azure DevOps organization.
> 4. In the **Client ID** field, enter the Microsoft Entra ID application Client ID that has access to the Azure DevOps organization.
> 5. In the **Certificate** field, provide the contents of the certificate file used to sign the JWT assertion and uploaded in the Microsoft Entra ID application.
> 6. Enter the contents of the **Private Key** file used for encrypting the JWT assertion.
>
>    > **Important**
>    >
>    > Generate and use an RSA encrypted private key. Unencrypted private keys are not supported.
> 7. Enter the **Private Key Password** used to decrypt the private key.
> 8. In the **Domain Name** field, enter the name of the Microsoft Entra ID domain to be managed. For example, `contoso.onmicrosoft.com`.
> 9. Select **Save**.

## Aggregation Settings

Change settings related to aggregation processes.

### Manage Service Principals as Accounts

By default, the connector only aggregates User data, and ignores Service Principals and Managed Identities during account aggregation. You can include Service Principles and Managed Identities in account aggregation processes, and enable the connector to manage these as well. To include Service Principals and Managed Identities in account aggregation:

1. Select **Manage Service Principals as Accounts**.
2. Select **Save**.

## Azure DevOps REST API Version Configuration

You can configure the connector to use a specific version of Azure DevOps Service REST API using the `apiVersion` parameter.

> [!NOTE]
>
> **apiVersion**
>
> This parameter sets a specific Azure DevOps REST API version to use with the source.
>
> string

To configure a specific version in the source, set the `apiVersion` parameter to the required REST API version. Upload the change using SailPoint's REST API. For example:

`<entry key="apiVersion" value="7.2-preview.1"/>`

> [!NOTE]
>
> For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication](<https://developer.sailpoint.com/docs/api/authentication/>) and [REST API - Update Source (Partial)](<https://developer.sailpoint.com/docs/api/update-source-v-1/>) in the SailPoint Developer Community.

## 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](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.