Tutorial: Configure myPolicies for automatic user provisioning
The objective of this tutorial is to demonstrate the steps to be performed in myPolicies and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to myPolicies.
This tutorial describes a connector built on top of the Azure AD User 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 Azure Active Directory.
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
- An Azure AD tenant.
- A myPolicies tenant.
- A user account in myPolicies with Admin permissions.
Assigning users to myPolicies
Azure Active Directory 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 Azure AD are synchronized.
Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD need access to myPolicies. Once decided, you can assign these users and/or groups to myPolicies by following the instructions here:
Important tips for assigning users to myPolicies
It is recommended that a single Azure AD user is assigned to myPolicies to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.
When assigning a user to myPolicies, you must select any valid application-specific role (if available) in the assignment dialog. Users with the Default Access role are excluded from provisioning.
Setup myPolicies for provisioning
Before configuring myPolicies for automatic user provisioning with Azure AD, you will need to enable SCIM provisioning on myPolicies.
Reach out to your myPolicies representative at email@example.com to obtain the secret token needed to configure SCIM provisioning.
Save the token value provided by the myPolicies representative. This value will be entered in the Secret Token field in the Provisioning tab of your myPolicies application in the Azure portal.
Add myPolicies from the gallery
To configure myPolicies for automatic user provisioning with Azure AD, you need to add myPolicies from the Azure AD application gallery to your list of managed SaaS applications.
To add myPolicies from the Azure AD application gallery, perform the following steps:
In the Azure portal, in the left navigation panel, select Azure Active Directory.
Go to Enterprise applications, and then select All applications.
To add a new application, select the New application button at the top of the pane.
In the search box, enter myPolicies, select myPolicies in the results panel, and then click the Add button to add the application.
Configuring automatic user provisioning to myPolicies
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in myPolicies based on user and/or group assignments in Azure AD.
You may also choose to enable SAML-based single sign-on for myPolicies, following the instructions provided in the myPolicies Single sign-on tutorial. Single sign-on can be configured independently of automatic user provisioning, though these two features compliment each other.
To configure automatic user provisioning for myPolicies in Azure AD:
Sign in to the Azure portal. Select Enterprise Applications, then select All applications.
In the applications list, select myPolicies.
Select the Provisioning tab.
Set the Provisioning Mode to Automatic.
Under the Admin Credentials section, input
https://<myPoliciesCustomDomain>.mypolicies.com/scimin Tenant URL where
<myPoliciesCustomDomain>is your myPolicies custom domain. You can retrieve your myPolicies customer domain, from your URL. Example:
In Secret Token, enter the token value which was retrieved earlier. Click Test Connection to ensure Azure AD can connect to myPolicies. If the connection fails, ensure your myPolicies 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 check the checkbox - Send an email notification when a failure occurs.
Under the Mappings section, select Synchronize Azure Active Directory Users to myPolicies.
Review the user attributes that are synchronized from Azure AD to myPolicies in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accounts in myPolicies for update operations. Select the Save button to commit any changes.
|emails[type eq "work"].value||String|
|addresses[type eq "work"].country||String|
To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.
To enable the Azure AD provisioning service for myPolicies, change the Provisioning Status to On in the Settings section.
Define the users and/or groups that you would like to provision to myPolicies by choosing the desired values in Scope in the Settings section.
When you are ready to provision, click Save.
This operation starts the initial synchronization of all users and/or groups defined in Scope in the Settings section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. You can use the Synchronization Details section to monitor progress and follow links to provisioning activity report, which describes all actions performed by the Azure AD provisioning service on myPolicies.
For more information on how to read the Azure AD provisioning logs, see Reporting on automatic user account provisioning.
- myPolicies always requires userName, email and externalId.
- myPolicies does not support hard deletes for user attributes.
- 09/15/2020 - Added support for "country" attribute for Users.
- Managing user account provisioning for Enterprise Apps
- What is application access and single sign-on with Azure Active Directory?