Overview
Our managed integration with Microsoft Entra ID (formerly Azure AD) syncs users from your Entra directory into Tribal Habits. This article covers the details and options specific to the Entra integration. For a general overview of managed integrations, see How do managed integrations work?
Important: This integration is available on Business plans as an annual add-on. It isn't available on Lite plans. If you’d like it activated, please contact our team at [email protected].
Key concepts
Entra Group: The group in Microsoft Entra ID whose members are synced to Tribal Habits.
App registration: The record in Entra that lets the integration read your users and Groups.
Client secret: A password-like value created in the app registration, with an expiry date you choose.
Microsoft Graph: Microsoft’s API, which the integration uses to read your Entra data.
One-way sync: User data flows from Entra to Tribal Habits only. Training records can’t be sent to Entra.
What the integration does
Once connected, Entra holds the master record for your users, and changes made to mapped fields in Entra are applied in Tribal Habits automatically:
When this happens | The result |
User added to Entra Group | Tribal Habits user created or reactivated |
User’s mapped field(s) updated in Entra | Tribal Habits user’s mapped field(s) updated |
User disabled, deleted or removed from Entra Group | Tribal Habits user deactivated, training history kept |
How the integration works
The Entra integration is a one-way, read-only sync that reads the members of your Entra Group through the Microsoft Graph API.
Sync frequency
Sync frequency
The Entra integration syncs every four hours by default. The schedule can be customised to suit your business processes.
Which users are synced
Which users are synced
Every member of the Entra Group you nominate, including members of nested groups. This can be an existing group (for example, All Employees) or one created just for this integration (for example, Tribal Habits LMS).
Entra’s dynamic membership groups can add and remove members automatically based on their properties, such as department or employee type, so the right people are always included. (Dynamic membership groups require Microsoft Entra ID P1 licences.)
If group membership alone doesn’t capture who should be synced, we can add custom logic to include or exclude users based on their properties.
Contractors and other non-employees are synced the same way, as long as they have an account in your Entra tenant and are in the Entra Group. See Guest users under Best practices.
Username options
Username options
Any of these Entra properties can be used as the Tribal Habits username, listed in order of preference:
Entra object ID:
id, if Entra is your only source of user data.Employee ID:
employeeId, if it’s filled in for every user.Work email:
mailoruserPrincipalName. Email is usually the only property shared by every system involved, so it suits organisations that also sync users from another system, or that use a third-party identity provider (IdP) for SSO.
User properties synced by default
These Entra user properties are available by default. At kick-off we agree which to map and where they go in Tribal Habits, usually into Tribal Habits custom fields.
Category | Entra properties (Microsoft Graph name) | Typical use in Tribal Habits |
Identity |
| Matching users and setting the username |
Name |
| User’s name |
Job |
| Reporting, filtering and enrolment rules |
Location |
| Reporting by site and enrolment rules |
Manager |
| Manager name and email |
Status |
| Active or deactivated |
Other |
(extension attributes 1–15) | Any additional data you hold in Entra |
Other properties can be added on request.
Security and permissions
All Microsoft Graph permissions the integration uses are read permissions; it never creates, changes or deletes anything in your directory.
How the connection is authorised
How the connection is authorised
Your Entra admin creates an app registration for Tribal Habits and grants admin consent for its permissions. During the set-up call, an Entra admin account signs in to authorise the connection via OAuth.
Use a service account for this sign-in, as described in the best practices for all managed integrations. The account needs the permissions required to authorise the connection and give the app access to your users and groups.
Microsoft Graph permissions requested
Microsoft Graph permissions requested
Application permissions:
User.Read.AllDirectory.Read.AllGroupMember.Read.AllGroup.Read.All
Delegated permissions:
User.ReadUser.ReadBasic.AllUser.Read.AllDirectory.Read.AllGroupMember.Read.AllGroup.Read.All
Best practices
These practices are specific to Entra and add to those for all managed integrations.
Plan for client secret expiry: You choose the client secret’s expiry period when you create it. Before it expires, create a new secret and securely send us its value, otherwise the sync will stop when the old one expires. Set a reminder well ahead of the expiry date. See Rotating your client secret under After go-live.
Guest users: Contractors added to your tenant as B2B guest users can be synced, but their properties often differ from members’ properties:
Their
userPrincipalNamelooks likejane_contractor.com#EXT#@yourtenant.onmicrosoft.com.Their
mailproperty holds their external email.Properties such as job title and department are often blank.
If guests will be synced, we’ll agree at kick-off which property to use as their username.
Setting up the integration
Step 1: Kick-off call (30 min)
As well as the general kick-off topics, we agree:
The Entra Group to sync and any custom inclusion or exclusion logic
Which username option to use (see username options under How the integration works)
Which Entra user properties to map and the Tribal Habits fields they map to
Step 2: Preparation
Your Entra admin prepares the app registration and Entra Group using the steps below.
Create the app registration
Sign in to the Microsoft Entra admin center and go to App registrations → New registration.
Enter the following settings:
Name: A unique name. We recommend ‘Tribal Habits LMS’.
Supported account types: Usually Accounts in this organizational directory only.
Redirect URI: Select Web, then enter https://www.workato.com/oauth/callback.
Click Register.
Add API permissions
Go to API permissions → Add a permission → Microsoft Graph.
Add the application and delegated permissions listed under Microsoft Graph permissions requested, in Security and permissions.
Grant admin consent
Click Grant admin consent and confirm.
Check that each permission’s status shows as granted.
This is how the permissions look after admin consent is granted.
Create a client secret
Go to Certificates & secrets → New client secret.
Enter a description (for example, ‘Tribal Habits LMS’) and choose an expiry period.
Click Add, then copy the secret’s Value.
Important: Copy the secret’s Value immediately and store it securely. Entra only shows it once and we’ll need it at the set-up call. Copy the Value, not the Secret ID.
Preparing your Entra Group
Choose or create the Entra Group whose members should be synced, and note its Object ID. We’ll need it at the set-up call.
Step 3: Set-up call (30–60 min)
Your Entra admin signs in with the service account to authorise the connection, then stays on the call while we test the sync.
What to have ready for the set-up call
The Application (client) ID, from the app registration’s Overview page
The Directory (tenant) ID, from the same page
The client secret Value you saved in Step 2
The Entra Group’s Object ID
Sign-in details for the service account that will authorise the connection
After go-live
These tasks are specific to Entra. For other changes, see After go-live for all managed integrations.
Rotating your client secret
In the Microsoft Entra admin center, open your Tribal Habits app registration and go to Certificates & secrets.
Create a new client secret and copy its Value.
Send the Value to our Support team securely, before the current secret expires.
Once we confirm the integration is using the new secret, delete the old one.
Changing the account that authorised the connection
If the authorising account needs to change (for example, moving from an individual’s user account to a service account), contact our Support team to arrange a short call to re-authorise the connection.
Troubleshooting
These issues are specific to Entra. For other issues, see Troubleshooting for all managed integrations.
A user isn’t syncing
Likely causes: The user isn’t in (or has been removed from) the Entra Group, their account is disabled in Entra or the change was made after the last sync. The Entra integration runs on a schedule rather than in real time, so changes aren’t applied until the next sync.
What to do: In Entra, check the user’s group membership and that their account is enabled, then wait for the next scheduled sync.
When to contact us: If the user still hasn’t synced after the next scheduled sync.
The sync has stopped
Likely causes: The client secret has expired, or the account that authorised the connection has been disabled, deleted or lost access.
What to do: We’re notified automatically if the sync stops, and we’ll contact you if we need anything from you. If the secret has expired, follow Rotating your client secret under After go-live. If the authorising account has changed, contact us to re-authorise the connection.
When to contact us: If neither cause applies, or the sync hasn’t resumed after you’ve sent a new secret.
FAQs
Is this the same as using Entra for single sign-on?
No. The integration manages who is Active in Tribal Habits; SSO handles how they sign in. They’re set up separately and work best together. Learn more about setting up SSO with Azure AD.
Does training data flow back to Entra?
No. Entra is an identity directory and has nowhere to store training records, so completions, certificates and progress remain in Tribal Habits reporting.
Do we need Entra ID P1 licences?
Only if you use a dynamic membership group as your Entra Group. A standard group with manually assigned members works without P1 licences.
Does it still work if we call it Azure AD?
Yes. Microsoft renamed Azure Active Directory to Microsoft Entra ID in 2023. Same service, same integration.










