Keep your employee information up to date on monday service by syncing user attributes from Active Directory. Once set up, requester details will appear automatically when a new ticket is submitted. It means your team can hit the ground running, with all the details already in place.
Get your Tenant ID from Microsoft Entra
To begin, head to the Microsoft Entra admin center and log in with one of the following roles:
- Application Administrator
- Cloud Application Administrator
- Application Owner
From the left pane, go to Identity and select Overview:
Under Basic information, you'll see your Tenant ID. Copy this value—we’ll use it in the next step.
Sync your employee details to monday service
To set up the sync, create a new workflow in the workflow builder. We recommend using a trigger of type Every time period so your data stays up to date.
Add an action block and search for Entra Directory User Sync:
Once added, click Add new account to connect your Microsoft Entra account. Paste the Tenant ID you copied earlier, approve the connection, and select the new provider from the list:
Choose a board to sync your users into. The Employee Directory board works best, but any board can be used as an alternative. Then, select the Entra attributes you want to sync and map each one to a column on your board. The Email field must be mapped for the sync to work. All other attributes are optional.
You can review the supported Entra attributes, how they appear in the workflow block, and their default monday.com column types in the table below:
|
Attribute name from Entra
|
Normalized attribute name (in workflow block)
|
Mapped monday.com column type
|
Notes
|
|---|---|---|---|
| displayName | Full Name | name | Always maps to the name column (first column) of the board. |
| Must be selected for the sync; all other non-name attributes are optional. | |||
| jobTitle | Job Title | dropdown | |
| department | Department | dropdown | |
| managerName | Manager Name | text | Not a true Entra attribute; attribute value is received by parsing the user's "manager" Entra value and pulling the "name" value from it. |
| managerEmail | Manager Email | Not a true Entra attribute; attribute value is received by parsing the user's "manager" Entra value and pulling the "email" or "userPrincipalName" value from it (in that order). | |
| mobilePhone | Mobile Phone | phone | |
| businessPhones | Work Phones | dropdown | Can have multiple values, hence we store it in a dropdown column at the moment. |
| officeLocation | Office / Room | dropdown | |
| streetAddress | Address (Street) | text | |
| city | City | dropdown | |
| state | State / Province | dropdown | |
| country | Country / Region | dropdown | |
| employeeId | Employee ID | text | |
| givenName | First Name | text | |
| surname | Last Name | text | |
| userPrincipalName | Login / UPN | text | |
| postalCode | ZIP / Postal Code | text | Text chosen instead of number so that it can have a leading 0. |
| employeeType | Employee Type | text | |
| userType | User Type | text | |
| employeeHireDate | Hire Date | date | |
| employeeLeaveDateTime | Termination Date | date | |
| preferredLanguage | Preferred Language | text | |
| mailNickname | Alias | text | |
| otherMails | Secondary Emails | dropdown | Dropdown because there could be multiple values, otherwise would be stored as email. |
| imAddresses | Chat addresses | dropdown | |
| accountEnabled | Account Enabled | status | Status used for easier filtering/interactions, etc. When synchronizing, if the following labels don't exist, "accountEnabled - true" and "accountEnabled - false" they'll be created and used for true/false values accordingly. |
| createdDateTime | Created Date | date | |
| creationType | Creation Type | text | |
| externalUserState | External User State | text | |
| externalUserStateChangeDateTime | External State Updated | date | |
| isManagementRestricted | Management Restricted | status | Status used for easier filtering/interactions, etc. When synchronizing, if the following labels don't exist, "isManagementRestricted - true" and "isManagementRestricted - false" they'll be created and used for true/false values accordingly. |
| isResourceAccount | Resource Account | status | Status used for easier filtering/interactions, etc. When synchronizing, if the following labels don't exist, "isResourceAccount - true" and "isResourceAccount - false" they'll be created and used for true/false values accordingly. |
| lastPasswordChangeDateTime | Last Password Change | date | |
| ExtensionAttribute1 | Extension attribute 1 | text | |
| ExtensionAttribute2 | Extension attribute 2 | text | |
| ExtensionAttribute3 | Extension attribute 3 | text | |
| ExtensionAttribute4 | Extension attribute 4 | text | |
| ExtensionAttribute5 | Extension attribute 5 | text | |
| ExtensionAttribute6 | Extension attribute 6 | text | |
| ExtensionAttribute7 | Extension attribute 7 | text | |
| ExtensionAttribute8 | Extension attribute 8 | text | |
| ExtensionAttribute9 | Extension attribute 9 | text | |
| ExtensionAttribute10 | Extension attribute 10 | text | |
| ExtensionAttribute11 | Extension attribute 11 | text | |
| ExtensionAttribute12 | Extension attribute 12 | text | |
| ExtensionAttribute13 | Extension attribute 13 | text | |
| ExtensionAttribute14 | Extension attribute 14 | text | |
| ExtensionAttribute15 | Extension attribute 15 | text | |
| onPremisesDomainName | AD Domain | text | |
| onPremisesDistinguishedName | DN | text | |
| onPremisesImmutableId | Immutable ID | text | |
| onPremisesSamAccountName | SAM Account Name | text | |
| onPremisesSyncEnabled | Sync Enabled | status | Status used for easier filtering/interactions, etc. When synchronizing, if the following labels don't exist, "onPremisesSyncEnabled - true" and "onPremisesSyncEnabled - false" they'll be created and used for true/false values accordingly. |
| onPremisesUserPrincipalName | On-prem UPN | text | |
| preferredDataLocation | Data Residency | text | |
| proxyAddresses | Email Aliases | dropdown | |
| signInSessionsValidFromDateTime | Session Valid From | date | |
| usageLocation | Licensing Location | text |
When everything’s set, click Publish workflow! Your synced board will look something like this:
View synced details in ticket submissions
Once the workflow is running, your Employee Directory board will be populated with data from Microsoft Entra ID. From there, requester details will appear automatically in the Employee details widget on the Tickets board.
Open a Ticket overview, and the requester’s synced information will appear, giving you instant context without any manual lookup:
Set up a cross-board automation
If you’re syncing Active Directory data to a different board than the default Employee Directory, set up the following cross-board automation to connect ticket data with requester details:
Use this recipe: When an item is created in this board, connect the item where ‘User email’ matches ‘Email’ in [your employee board] by adding a new matched item:
This ensures that when a new ticket is created, requester details are pulled in automatically, based on a matching email address.
If you have any questions, please reach out to our team right here. We’re available 24/7 and happy to help.