Tutorial: Configure Gong for automatic user provisioning
This tutorial describes the steps you need to perform in both Gong and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to Gong using the Azure AD 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.
- Create users in Gong.
- Remove users in Gong when they do not require access anymore.
- Keep user attributes synchronized between Azure AD and Gong.
- Provision groups and group memberships in Gong.
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
- An Azure AD tenant.
- A user account in Azure AD with permission to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
- A user account in Gong with Technical Administrator privilege.
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 Azure AD and Gong.
Step 2. Configure Gong to support provisioning with Azure AD
Go to your company settings page > PEOPLE area > Team Member Provisioning.
Select Azure AD as the provisioning source.
To assign data capture, workspace, and permission settings to Azure AD groups:
- In the Assign settings area, click ADD ASSIGNMENT.
- Give the assignment a name.
- In the Azure AD groups area, select the Azure AD group you want to define the settings for.
- In the Data capture area, select the home workspace and the data capture settings for people that belong to this group.
- In the Workspaces and permissions area, set the permissions profile for other workspaces in your org.
- In the Update settings area, define how settings can be managed for this assignment:
- Select Manual editing to manage data capture and permission settings for users in this assignment in Gong. After you create the assignment: if you make changes to group settings in Azure AD, they will not be pushed to Gong. However, you can edit the group settings manually in Gong.
- (Recommended) Select Automatic updates to give Azure AD governance over data capture and permission settings in Gong. Define data capture and permission settings in Gong only when creating an assignment. Thereafter, other changes will only be applied to users in groups with this assignment when pushed from Azure AD.
- Click ADD ASSIGNMENT.
For org's that don't have assignments (step 3), select the permission profile to apply to for automatically provisioned users.
In the Manager's provisioning settings area:
- Select Notify direct managers with recorded teams when a new team member is imported to keep your team managers in the loop.
- Select Managers can turn data capture on or off for their team to give your team managers some autonomy.
For more information, see "What are Manager's provisioning settings" in the FAQ for team member provisioning article.
Click Update to save your settings.
If you later change the provisioning source from Azure AD and then want to return to Azure AD provisioning, you will need to re-authenticate to Azure AD .
Step 3. Add Gong from the Azure AD application gallery
Add Gong from the Azure AD application gallery to start managing provisioning to Gong. If you have previously setup Gong for SSO, you can use the same application. However it is recommended that 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 Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / 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 Gong
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Gong based on user and/or group assignments in Azure AD.
To configure automatic user provisioning for Gong in Azure AD:
Sign in to the Azure portal. Select Enterprise Applications, then select All applications.
In the applications list, select Gong.
Select the Provisioning tab.
Set the Provisioning Mode to Automatic.
In the Admin Credentials section, click on Authorize, make sure that you enter your Gong account's Admin credentials. Click Test Connection to ensure Azure AD can connect to Gong. If the connection fails, ensure your Gong 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.
Under the Mappings section, select Synchronize Azure Active Directory Users to Gong.
Review the user attributes that are synchronized from Azure AD to Gong in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Gong for update operations. If you choose to change the matching target attribute, you will need to ensure that the Gong API supports filtering users based on that attribute. Select the Save button to commit any changes.
Attribute Type Supported for filtering Required by Gong userName String ✓ ✓ urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager String active Boolean title String emails[type eq "work"].value String ✓ name.givenName String ✓ name.familyName String ✓ phoneNumbers[type eq "work"].value String externalId String locale String timezone String urn:ietf:params:scim:schemas:extension:Gong:2.0:User:stateOrProvince String urn:ietf:params:scim:schemas:extension:Gong:2.0:User:country String
Under the Mappings section, select Synchronize Azure Active Directory Groups to Gong.
Review the group attributes that are synchronized from Azure AD to Gong in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the groups in Gong for update operations. Select the Save button to commit any changes.
Attribute Type Supported for filtering Required by Gong displayName String ✓ ✓ members Reference
To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.
To enable the Azure AD provisioning service for Gong, change the Provisioning Status to On in the Settings section.
Define the users and/or groups that you would like to provision to Gong 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 cycle of all users and groups 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 Azure AD 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 is 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.
- 03/23/2022 - Added support for Group Provisioning.
- 04/21/2022 - emails[type eq "work"].value has been marked as required attribute.
- Managing user account provisioning for Enterprise Apps
- What is application access and single sign-on with Azure Active Directory?