Microsoft Entra ID

Configure Harness for automatic user provisioning with Microsoft Entra ID

In brief

Learn how to configure Microsoft Entra ID to automatically provision and deprovision user accounts to Harness.

What Entra admins need to know

Review the documentation change to determine whether it affects tenant configuration, security posture, or rollout plans.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

Open on Microsoft Learn ↗

The comparison below is an extract of the Microsoft Learn article showing only the changed content. Open the full article for complete context.


Configure Harness for automatic user provisioning with Microsoft Entra ID

In this article, you learnThis article explains how to configure Microsoft Entra ID to automatically provision and deprovision users or groups to Harness. Automatic provisioning eliminates manual user management by synchronizing user lifecycle changes from your identity provider to Harness.

Prerequisites

The scenario outlined in this article assumes that you already have the following prerequisites:

[!INCLUDE common-prerequisites.md]

Assign users to Harness

Before you configure provisioning, you must assign users or groups to the Harness application in Microsoft Entra ID. Microsoft Entra ID uses a concept called assignments to determine which users should receive access to selected apps.applications. In the context of automatic user provisioning, only the users or groups that have been assigned to an application in Microsoft Entra ID are synchronized.

Before you configure and enable automatic user provisioning, decide which users or groups in Microsoft Entra ID need access to Harness. You can then assign these users or groups to Harness by following the instructions in Assign a user or group to an enterprise app.

Important tips

Recommendations for assigning usersuser assignment

Start with a small test group before you roll out provisioning to Harness

  • We recommended that you assignyour entire organization. Assign a single Microsoft Entra user to Harness to test the automatic user provisioning configuration. AdditionalAfter you verify that provisioning works correctly, you can assign additional users or groups can be assigned later.groups.

  • When you assign a user to Harness, you must select anya valid application-specific role (if available) in the Assignment dialog box. Users with the Default Access role are excluded from provisioning.

  • If you currently have a Harness FirstGen App Integration setup in Microsoft Entra ID and are now trying to set up one for Harness NextGen, make sureHarness, ensure that the user information is also included in the FirstGen App Integration before attemptingyou attempt to log into Harness NextGen through SSO.

Set up Harness for provisioning

You must generate a SCIM API token in Harness before you can configure provisioning in Microsoft Entra ID. This token allows Microsoft Entra ID to securely connect to the Harness SCIM endpoint and provision users.

  1. Sign in to your Harness Admin Console, select your profile at the bottom left corner of the page, and then go to Continuous Security > Access ManagementProfile Overview.

    Screenshot of the Harness Admin Console with the profile menu used to open Profile Overview.

  2. SelectUnder My API Keys, select +API Key. The window to create an API key opens.

    Screenshot of the Harness Profile Overview page showing the +API Key button under My API Keys.

  3. SelectSpecify a Add API KeyName and select Save. Harness creates an API key for your account.

    Screenshot of the Harness new API key dialog with the Name box and Save button.

  4. In theTo create a token for your API key, select Add Api Key+Token pane, do the following:

    Harness Add Api Key paneunder your newly created API key.

    a. In the Name box, provideProvide a name for the key.
    b. In theand select Permissions Inherited from drop-down list, select an option.

  5. Select SubmitGenerate token.

  6. b. Copy the Key for later usetoken value to a safe location. You'll need this token to configure the connection in this article.Microsoft Entra ID.

    Harness Create Tokenc. Select Close.

    Screenshot of the Harness token dialog showing the Generate token and Close buttons.

Add Harness from the gallery

Before you configureYou must add the Harness for automatic user provisioning with Microsoft Entra ID, you need to add Harnessapplication from the Microsoft Entra application gallery to your list ofbefore you can configure automatic user provisioning. This registers Harness as a managed SaaS applications.application in your Microsoft Entra tenant.

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Entra ID > Enterprise apps.

    The "All applications" link

  3. To add a new application, select the New application button at the top of the pane.

    The "New application" button

  4. In the search box, enter Harness, select Harness in the results list, and then select the Add button to add the application.

    Harness in the results listScreenshot of the Microsoft Entra gallery search results with Harness selected and the Add button.

Configure automatic user provisioning to Harness

After you add Harness from the gallery and generate a SCIM token, you can configure the provisioning connection. This section guides youwalks through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users or groups in Harness based on user or group assignments in Microsoft Entra ID.

To configure automatic user provisioning for Harness in Microsoft Entra ID, do the following:

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Entra ID > Enterprise apps.

    Enterprise applications blade

  3. In the applications list, select Harness.

    The Harness link in the applications list

  4. Select the Provisioning tab.

    Provisioning tab

  5. SetSelect + New configuration.

    Screenshot of Provisioning tab automatic.

  6. Under Admin Credentials, do the following:

    Tenant URL + Token

    • In the Tenant URL box, enter https://app.harness.io/gateway/api/scim/account/<your_harness_account_ID>. You can obtain your Harness account ID from the URL in your browser when you're are logged into Harness.

    • In the Secret Token box, enter the SCIM Authentication Token value that you saved in step 63 of the "Set up Harness for provisioning" section.

    • Select Test Connection to ensure that Microsoft Entra ID can connect to Harness. If the connection fails, ensure that your Harness account has Admin permissions, and then try again.

      Screenshot of Provisioning test connection.

    Screenshot of Provisioning test connection.

  7. Select Create to create your configuration.

  8. Select Properties in the Overview page.

  9. Select the pencil to edit the properties. Enable notification emails and provide an email to receive quarantine emails. Enable accidental deletions prevention. Select Apply to save the changes.

    Screenshot of Provisioning properties.

  10. Select Attribute Mapping in the left panel and select users.

  11. Review the user attributes that are synchronized from Microsoft Entra ID to Harness in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accounts in Harness for update operations. Select the Save button to commit any changes.

    Harness user "Attribute Mappings" pane

  12. Under Mappings, select Synchronize Microsoft Entra groups to Harness.

  13. Review the usergroup attributes that are synchronized from Microsoft Entra ID to Harness in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accountsgroups in Harness for update operations. Select the Save button to commit any changes.

    Harness group "Attribute Mappings" pane

  14. To configure scoping filters, refer to the following instructions provided in the Scoping filter article.

  15. Use on-demand provisioning to validate sync with a small number of users before deploying more broadly in your organization.

  16. When you're are ready to provision, select Start Provisioning from the Overview page.

Monitor your deployment

After you start provisioning, monitor the provisioning logs to verify that users and groups sync correctly between Microsoft Entra ID and Harness.

[!INCLUDE monitor-deployment.md]

Additional resources

Related content