Configure Netskope User Authentication for automatic user provisioning with Microsoft Entra ID

The objective of this article is to demonstrate the steps to be performed in Netskope User Authentication and Microsoft Entra ID to configure Microsoft Entra ID to automatically provision and de-provision users and/or groups to Netskope User Authentication.

Prerequisites

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

• • A Microsoft Entra user account with an active subscription. If you don't already have one, you can Create an account for free.
  • One of the following roles:
    • Application Administrator
    • Cloud Application Administrator
    • Application Owner.
• A Netskope User Authentication tenant
• A user account in Netskope User Authentication with Admin permissions.

Assigning users to Netskope User Authentication

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

Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Microsoft Entra ID need access to Netskope User Authentication. Once decided, you can assign these users and/or groups to Netskope User Authentication by following the instructions here:

• Assign a user or group to an enterprise app

Important tips for assigning users to Netskope User Authentication

• It's recommended that a single Microsoft Entra user is assigned to Netskope User Authentication to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.

• When assigning a user to Netskope User Authentication, you must select any valid application-specific role (if available) in the assignment dialog. Users with the Default Access role are excluded from provisioning.

Set up Netskope User Authentication for provisioning

1. Sign in to your Netskope User Authentication Admin Console. Navigate to Home > Settings.

   

2. Navigate to Tools. Under the Tools menu navigate to Directory Tools > SCIM INTEGRATION.

   

   

3. Scroll down and select Add Token button. In the Add OAuth Client Name dialog box provide a CLIENT NAME and select the Save button.

   

   

4. Copy the SCIM Server URL and the TOKEN. These values are entered in the Tenant URL and Secret Token fields respectively in the Provisioning tab of your Netskope User Authentication application.

   

Add Netskope User Authentication from the gallery

Before configuring Netskope User Authentication for automatic user provisioning with Microsoft Entra ID, you need to add Netskope User Authentication from the Microsoft Entra application gallery to your list of managed SaaS applications.

To add Netskope User Authentication from the Microsoft Entra application gallery, perform the following steps:

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
2. Browse to Entra ID > Enterprise apps > New application.
3. In the Add from the gallery section, type Netskope User Authentication, select Netskope User Authentication in the search box.
4. Select Netskope User Authentication from results panel and then add the app. Wait a few seconds while the app is added to your tenant.

Configuring automatic user provisioning to Netskope User Authentication

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in Netskope User Authentication based on user and/or group assignments in Microsoft Entra ID.

To configure automatic user provisioning for Netskope User Authentication in Microsoft Entra ID:

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

2. Browse to Entra ID > Enterprise apps

   

3. In the applications list, select Netskope User Authentication.

   

4. Select the Provisioning tab.

   

5. Select + New configuration.

   

6. In the Tenant URL field, enter your Netskope User Authentication Tenant URL and Secret Token. Select Test Connection to ensure Microsoft Entra ID can connect to Netskope User Authentication. If the connection fails, ensure your Netskope User Authentication account has the required admin permissions and try again.

   

7. Select Create to create your configuration.

8. Select Properties on the Overview page.

9. In the Notification Email field, enter the email address of a person who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.

   

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

11. Review the user attributes that are synchronized from Microsoft Entra ID to Netskope User Authentication in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Netskope User Authentication for update operations. If you choose to change the matching target attribute, you need to ensure that the Netskope User Authentication API supports filtering users based on that attribute. Select the Save button to commit any changes.

    

12. Review the group attributes that are synchronized from Microsoft Entra ID to Netskope User Authentication in the Attribute Mapping section. The attributes selected as Matching properties are used to match the groups in Netskope User Authentication for update operations. Select the Save button to commit any changes.

    

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

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

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

Additional resources

• Managing user account provisioning for Enterprise Apps
• What is application access and single sign-on with Microsoft Entra ID?

Related content

• Learn how to review logs and get reports on provisioning activity