Microsoft Entra ID HRIS Integration

The Microsoft Entra ID HRIS integration allows you to sync HRIS data between Microsoft Entra ID and your application through Kombo’s unified API. The tool slug for this connector is entraid.

Guides and Resources

Connection Setup Guide

Step-by-step instructions to connect your Microsoft Entra ID account to Kombo.

Supported Features & Coverage

Models
Actions
Features
Create Employee with Form

Legal Entities

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

Work Locations

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

Employees

Field	Notes
id
remote_id
changed_at
remote_deleted_at
employee_number
first_name
last_name
display_full_name
job_title
work_email
personal_email
mobile_phone_number
employment_status
employment_type
avatar
work_location_id
legal_entity_id
manager_id
home_address
start_date
termination_date
remote_created_at
custom_fields
integration_fields
remote_data

Groups

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
type
remote_data

Employee <> Group

Field	Notes
employee_id
team_id
id
changed_at
remote_deleted_at

Create employee

Azure / entra requires a password to be set when creating a user. The user has to use the password on his initial sign-in and will be forced to change the password once signed in. The work_email field is required. The domain of the submitted email has to be one of the verified domains in the organization.

Input Field	Notes
first_name
last_name
work_email
job_title
home_address.street_1
home_address.city
home_address.zip_code
home_address.country
date_of_birth

Create employee (v2)

For detailed information about creating employees with form, please see the Create Employee with Form tab above.

Input Field	Notes
properties

Feature	Notes
Connection Guide
Prerequisites
OAuth
API Passthrough
Additional Scopes
Group Types
DEPARTMENT
COST_CENTER
Custom Field Explorer
Employees

Some optional form fields are referencing the following data models:

Groups

Consider enabling these in your scope configuration.

firstName

text

required

First Name
The first name of the employee
Unified field: first_name

lastName

text

required

Last Name
The last name of the employee
Unified field: last_name

workEmail

text

required

Work Email
The email address of the employee
Unified field: work_email

password

text

required

Password
Azure / entra requires a password to be set when creating a user. The user has to use the password on his initial sign-in and will be forced to change the password once signed in.

businessPhones

text

Business Phones
The telephone numbers for the user.
Unified field: mobile_phone_number

mobilePhone

text

Mobile Phone Number
The mobile phone number of the employee
Unified field: mobile_phone_number

faxNumber

text

Fax Number
The fax number of the user.

otherMails

array

Other Mails
A list of additional email addresses for the user; for example: [‘[email protected]’, ‘[email protected]’]. This cannot contain accent characters.

Show items

Item

text

city

text

City
The city in which the user is located.
Unified field: home_address.city

country

text

Country or Region
The country or region in which the user is located; for example, US or UK.
Unified field: home_address.country

postalCode

text

Postal Code
The postal code for the user’s postal address. The postal code is specific to the user’s country/region. In the United States of America, this attribute contains the ZIP code.
Unified field: home_address.zip_code

state

text

State
The state or province in the user’s address.
Unified field: home_address.state

streetAddress

text

Street Address
The street address of the user’s place of business.
Unified field: home_address.street_1

officeLocation

text

Office Location
The office location in the user’s place of business.

companyName

text

Company Name
The company name which the user is associated. This property can be useful for describing the company that an external user comes from.

department

text

Department
The name for the department in which the user works.

employeeId

text

Employee ID
The employee identifier assigned to the user by the organization.

employeeHireDate

date

Start Date
Start date of the employee. Also considered to be the hire date
Unified field: start_date

employeeType

single_select

Employee Type
Captures the type of employment for the user.

jobTitle

text

Job Title
The user’s job title.
Unified field: job_title

employeeOrgData

object

Employee Organization Data
Represents organization data (for example, division and costCenter).

Show properties

costCenter

single_select

Cost Center
The cost center associated with the user.
References /v1/hris/groups?types=COST_CENTER

division

single_select

Division
The name of the division in which the user works.
References /v1/hris/groups?types=DEPARTMENT

Integration Variants

Current connector: Current Microsoft Entra ID integration (recommended for new connections) For Microsoft Entra ID, we also offer the following other connector variants:

Microsoft Azure AD

Legacy Azure AD integration. Microsoft rebranded Azure AD to Entra ID. Both variants work, but consider using Entra ID for new connections

You can only use one variant at a time.

General

Features

Guides

HRIS API Reference

General API Reference

DATEV

Microsoft Entra ID HRIS Integration

Guides and Resources

Connection Setup Guide

Supported Features & Coverage

Integration Variants

Microsoft Azure AD

General

Features

Guides

HRIS API Reference

General API Reference

DATEV

​Guides and Resources

Connection Setup Guide

​Supported Features & Coverage

​Integration Variants

Microsoft Azure AD

Guides and Resources

Supported Features & Coverage

Integration Variants