Configure N-able User Provisioning for automatic user provisioning

This article describes the steps you need to perform in both N-able User Provisioning and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and deprovisions users to N-able User Provisioning using the Microsoft Entra provisioning service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Microsoft Entra ID.

Supported capabilities

• Create users in N-able User Provisioning.
• Remove users in N-able User Provisioning when they do not require access anymore.
• Keep user attributes synchronized between Microsoft Entra ID and N-able User Provisioning.

Bemærk

To use the OAuth2 flow, users should use the https://portal.azure.com/?feature.userProvisioningV2Authentication=true url to access the Azure portal.

Prerequisites

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

• A Microsoft Entra tenant
• One of the following roles: Application Administrator, Cloud Application Administrator, or Application Owner.
• A user account in N-able User Provisioning with Admin permissions.

Step 1: Plan your provisioning deployment

• Learn about how the provisioning service works.
• Determine who will be in scope for provisioning.
• Determine what data to map between Microsoft Entra ID and N-able User Provisioning.

Step 2: Add N-able User Provisioning from the Microsoft Entra application gallery

Add N-able User Provisioning from the Microsoft Entra application gallery to start managing provisioning to N-able User Provisioning. If you have previously setup N-able User Provisioning for SSO, you can use the same application. However it's recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 3: Define who will be in scope for provisioning

The Microsoft Entra provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users to the application. If you choose to scope who will be provisioned based solely on attributes of the user, you can use a scoping filter as described here.

• Start small. Test with a small set of users before rolling out to everyone. When scope for provisioning is set to assigned users, you can control this by assigning one or two users to the app. When scope is set to all users, you can specify an attribute based scoping filter.

• If you need more roles, you can update the application manifest to add new roles.

Step 4: Configure automatic user provisioning to N-able User Provisioning

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users in N-able User Provisioning based on user assignments in Microsoft Entra ID.

To configure automatic user provisioning for N-able User Provisioning in Microsoft Entra ID:

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

2. Browse to Identity > Applications > Enterprise applications

   

3. In the applications list, select N-able User Provisioning.

   

4. Select the Provisioning tab.

   

5. Set the Provisioning Mode to Automatic.

   

6. In the Admin Credentials section, enter your N-able User Provisioning Tenant URL, Token Endpoint, Client Identifier and Client Secret. Click Test Connection to ensure Microsoft Entra ID can connect to N-able User Provisioning. If the connection fails, ensure your N-able User Provisioning account has Admin permissions and try again.

   Bemærk

   To use the OAuth2 flow, users should use the https://portal.azure.com/?feature.userProvisioningV2Authentication=true url to access the Azure portal.

   

7. 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.

   

8. Select Save.

9. Under the Mappings section, select Synchronize Microsoft Entra users to N-able User Provisioning.

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

    Attribute	Type	Supported for filtering	Required by N-able User Provisioning
    userName	String	✓	✓
    active	Boolean		✓
    name.givenName	String		✓
    name.familyName	String		✓

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

12. To enable the Microsoft Entra provisioning service for N-able User Provisioning, change the Provisioning Status to On in the Settings section.

    

13. Define the users that you would like to provision to N-able User Provisioning by choosing the desired values in Scope in the Settings section.

    

14. When you're ready to provision, click Save.

    

This operation starts the initial synchronization cycle of all users defined in Scope in the Settings section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running.

Step 5: Monitor your deployment

Once you've configured provisioning, use the following resources to monitor your deployment:

• Use the provisioning logs to determine which users have been provisioned successfully or unsuccessfully
• Check the progress bar to see the status of the provisioning cycle and how close it's to completion
• If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states here.

More 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