Integrate with Azure Active Directory

Integrating Limeade Listening Engage with your company's existing Azure Active Directory will simplify user management through automation. No longer will you have to manually add users one by one, or send an import file to the Limeade Listening Customer Success Team. Complete the Active Directory integration one time and users will sync automatically into Limeade Listening.

( ! ) This integration is only for user management and is not for Single Sign-On. If you would like to set up a Single Sign-On integration with Azure Active Directory, please reach out to our Support team so that they can help you build out this integration.


In this article:


To complete this integration, you'll need these three things:

  1. An Azure Active Directory instance at your company 
  2. Global Admin rights to your Azure AD instance 
  3. Super Admin rights in Limeade Listening

( !If you are missing any one of these three things, please contact your in-house technical team for assistance before proceeding.


Integrating Limeade Listening with Azure AD


Whether you are new to Limeade Listening or you have been pulsing for years, the Azure Active Directory integration will significantly decrease your time spent housekeeping employees in Limeade Listening


1. Log in to Limeade Listening and navigate to the Integrations page under the Settings tab. 

2. Locate the Azure Active Directory 'card' in the list and click to open it.  


3. Click Connect.


4. Enter your Active Directory login credentials and Sign In.


5. You will be asked to grant permission to Limeade Listening to the Azure AD instance. Read the message and Accept to return back to Limeade Listening.


6. Now that you are integrated, you still have to import the Azure AD groups to Limeade Listening. Select the group(s) from the dropdown list that you would like to sync and click Add when you are done.



If you are new to Limeade Listening and have not invited any users yet, but your account has launched, clicking Add will send invitation emails to new users immediately. Once they get the email, employees can set their Limeade Listening password and will have full access to respond to their Engage survey, send Cheers, give anonymous suggestions, and more.

If your account has not launched yet, then your users will be added to your account, but they will not be sent an invitation to join Limeade Listening until your account has launched.


If you have been pulsing for a while and are just looking to simplify user management going forward, existing Limeade Listening users will be unaffected by the sync. They will not get any sort of notification from Limeade Listening. However, if there are any Limeade Listening users in your account that do not appear in Azure AD, they will be deactivated immediately. Azure AD serves as the one source of truth so please make sure that all of your Limeade Listening users belong to one of the Azure AD groups you have synced.


Changing Your Update Preferences

When you select Azure AD groups to sync to Limeade Listening, they will import instantly and groups will be auto-synced once per day on weekdays after that at Midnight UTC. (Not sure where you land by comparison? The World Clock can help!)  

The default setting is to sync selected Azure AD groups automatically. You can opt for manual updates by going to the Apps section and switching automatic updates off. When you switch to manual update mode, an Update button will appear so you can manually sync users between Azure AD and Limeade Listening on demand. 


Turn off auto-updates for more control of your imports. However, we recommend keeping auto-updates on, especially if you have a dedicated Azure AD group for Limeade Listening use. See below for more information about creating a new Azure AD group.


Sync Segments*

Segments have been replaced by Primary Attributes for better qualitative and quantitative reporting. If you are new to Limeade Listening, we recommend leaving the "Segments Sync" feature off for your Azure AD integration.

Create a group specifically for Limeade Listening in Azure Active Directory

We recommend creating one group in Azure Active Directory specifically for Limeade Listening, especially if you have a large organization and not everyone needs access. Use this group to prevent syncing employees who actually do not need Limeade Listening and will count against your per-seat subscription size. Instead of inviting and deactivating employees directly in Limeade Listening, you can simply add or remove them from the AD group and they will be synced for you.

For detailed instructions on how to create a new Azure AD group for your Limeade Listening application, please see the Azure AD documentation for Managing Groups.

Frequently Asked Questions

Will my existing users get overwritten if I import them from Azure AD? 
If the employee's email address from Azure AD matches the one in Limeade Listening then they will not be overwritten. They will still keep their Cheers, Pulse Streaks, and Attributes, the only difference is their name will update if there is a mismatch between Azure AD and Limeade Listening. Azure AD is considered the source of truth so the sync will update the name in Limeade Listening to match.

What happens if an existing Limeade Listening user does not belong to any of the Azure AD groups I have synced to Limeade Listening? 
Once you have completed your configuration, any users who do not belong to one of the synced Azure AD groups will be deactivated in Limeade Listening. To avoid any disruption to your users and admin team, make sure that all Limeade Listening users belong to an Azure AD group that is being synced to Limeade Listening.

Can I use Onboard for new hires with the Azure AD integration? 
At this time, all users synced from Azure AD will get Engage Pulse surveys by default; new hires will not get Onboard Surveys. 
Please contact our Support team for assistance with moving newly hired employees from Engage to Onboard. 

How do I deactivate a user when using Azure AD integration? 
You have to remove them from the Azure AD group itself. We recommend having one specific Azure AD group just for Limeade Listening and you can add or remove users as needed (see below). If you deactivate the user in Limeade Listening without removing them from the Azure AD group, they will just get reactivated during the next sync. 

What happens if I deactivate a user in Limeade Listening but they still belong to the Azure AD group? 
They will get reactivated during the next sync. See above. 

What happens if a deactivated Limeade Listening user gets synced from Azure AD? 
The deactivated Limeade Listening user will reactivate if they belong to an imported Azure AD group. Remove the employee from the Azure AD group in order to keep them deactivated in Limeade Listening. 

What happens when a user gets removed from the Azure AD group? 
They will be deactivated in Limeade Listening and will not count against your per-seat subscription size.

Fields that we pull from Azure AD 

  1. Supported standard properties are documented here: User Resource Type - Microsoft Graph v1.0 
    However, we currently only pull id, displayName, givenName, jobTitle, mail, officeLocation, surname, userPrincipalName, department and employeeHireDate.
  2. Regarding manager-related information, we are still pulling manager_email and manager_employee_id. But please note that these fields will not appear in the payload if the HRIS integration is configured on our end to not sync managers.
  3. For extension attributes, if you request it of us, we will sync all of them, which are documented here: Microsoft Extensibility Overview - Extension Attributes 
  4. For custom fields, we will need you to provide us the list of fields you would like to sync to Limeade Listening.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.