Tutorial: Configure KPN Grip for automatic user provisioning

Article
10/23/2023

This tutorial describes the steps you need to do in both KPN Grip and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users and groups to KPN Grip 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 apps with Microsoft Entra ID.

Capabilities supported

Create users in KPN Grip.
Remove users in KPN Grip when they do not require access anymore.
Keep user attributes synchronized between Microsoft Entra ID and KPN Grip.
Single sign-on to KPN Grip.

Prerequisites

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

A Microsoft Entra tenant.
A user account in Microsoft Entra ID with permission to configure provisioning. For example Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator.
A user account in KPN Grip 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 KPN Grip.

Step 2: Configure KPN Grip to support provisioning with Microsoft Entra ID

To configure KPN Grip to support provisioning with Microsoft Entra ID refer KPN Grip Microsoft Entra Settings.

Step 3: Add KPN Grip from the Microsoft Entra application gallery

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

Step 4: Define who will be in scope for provisioning

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

Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.
If you need additional roles, you can update the application manifest to add new roles.

Step 5: Configure automatic user provisioning to KPN Grip

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

To configure automatic user provisioning for KPN Grip in Microsoft Entra ID:

Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
Browse to Identity > Applications > Enterprise applications
In the applications list, select KPN Grip.
Select the Provisioning tab.
Set the Provisioning Mode to Automatic.
Under the Admin Credentials section, input your KPN Grip Tenant URL and Secret Token. Click Test Connection to ensure Microsoft Entra ID can connect to KPN Grip. If the connection fails, ensure your KPN Grip account has Admin permissions and try again.
In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.
Select Save.
Under the Mappings section, select Synchronize Microsoft Entra users to KPN Grip.

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

Attribute	Type	Supported for filtering	Required by KPN Grip
userName	String	✓	✓
displayName	String		✓
active	Boolean
name.givenName	String
name.familyName	String
emails[type eq "work"].value	String
emails[type eq "alternate"].value	String
phoneNumbers[type eq "work"].value	String
phoneNumbers[type eq "mobile"].value	String
addresses[type eq "work"].region	String
addresses[type eq "work"].streetAddress	String
addresses[type eq "work"].locality	String
addresses[type eq "work"].postalCode	String
addresses[type eq "work"].country	String
externalId	String
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager	String
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber	String

To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.
To enable the Microsoft Entra provisioning service for KPN Grip, change the Provisioning Status to On in the Settings section.
Define the users and groups that you would like to provision to KPN Grip by choosing the appropriate values in Scope in the Settings section.
When you're ready to provision, click Save.

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

Step 6: 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 will go into quarantine. Learn more about quarantine states here.

More resources

Next steps

Learn how to review logs and get reports on provisioning activity