To sync your Active Directory with our system, you'll want to start with the PowerShell template we provide. It can be easily configured and/or modified to connect to your Active Directory, export users to a CSV file, and upload the CSV to our servers for processing. To use this template, you will need to be familiar with the following:
PowerShell (version 3 or above)
The names of the Organization Unit(s) in ActiveDirectory to be synced with our system
Scheduling jobs with the PowerShell script
From the web portal, navigate to the Active Directory Integration page to find our Powershell template. This page provides detailed instructions for using the script and the script itself. You can cross-reference the column titles for the CSV conversion here.
If you have multiple locations, you will need to specify this for each contact. Verify that the location is spelled exactly as it is on your account under Locations > edit > identifier (no capitals or spaces). If you would like a single contact in more than one location, duplicate the contact, one for each location with the proper location identifier for each. If your configuration is global, they will automatically be added to All Locations.
What about LDAP?
If your organization uses vanilla LDAP instead of Active Directory, the PowerShell template should give you a good idea of what a script must do to sync with our system. If you have an account with us, the Contact Import Integration page is another resource that outlines the details of the CSV file that you will need to create, and how that file will need to be transmitted to us.
Please note: Our PaaS no longer supports TLS 1.1 and 1.0 connections as of July 31st, 2021. Unfortunately, PowerShell will use these older versions of TLS by default. In order to correct this, you should add the following command just before the
Invoke-RestMethod line in your script to force TLS 1.2 to be used:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12