> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/settings-1/integrations/hr-sync-overview/microsoft-entra-id-field-mapping-for-hr-sync.md). # Microsoft Entra ID Field Mapping for HR Sync HR Sync can connect equipme with different HR and identity systems. The fields available for synchronization depend on the connected source system and the configured mapping. This article documents the standard mapping currently used when employee data is synchronized from Microsoft Entra ID to equipme. {% hint style="info" %} **Important:** This overview applies specifically to Microsoft Entra ID. Other HR Sync source systems may provide different fields and mappings. {% endhint %} ### Standard field mapping | **Microsoft Entra ID field** | **Microsoft Graph property** | **Field in equipme** | **Behavior in equipme** | | ---------------------------- | ---------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------- | | First name | `givenName` | First name | The value is transferred to the employee profile | | Last name | `surname` | Last name | The value is transferred to the employee profile | | User principal name | `userPrincipalName` | Username | The UPN is used as the employee’s username | | Job title | `jobTitle` | Position | The value is transferred as the employee’s position | | Department | `department` | Department group | The employee is assigned to the corresponding department group. A new group is created if it does not yet exist | | Employee ID | `employeeId` | Personnel number | The value is transferred as the personnel number | | Office location | `officeLocation` | Location | The employee is assigned to the corresponding location. A new location is created if it does not yet exist | | Business phone | `businessPhones` | Business phone | The value is transferred to the business phone field | | Mobile phone | `mobilePhone` | Mobile number | The value is transferred to the mobile number field | | Email address | `mail` | Business email | The value is transferred as the employee’s business email address | | Cost center | `employeeOrgData.costCenter` | Cost center | The value is transferred as the employee’s cost center | | Manager | `manager` | Supervisor | The manager relationship is used to assign the employee’s supervisor | ### Username and business email Microsoft Entra ID stores the user principal name and the email address separately. The user principal name, or UPN, is transferred to the **Username** field in equipme. The value stored in the Entra email field is transferred separately to the **Business email** field. | **Source in Microsoft Entra ID** | **Target in equipme** | | -------------------------------- | --------------------- | | User principal name | Username | | Email address | Business email | Although both values are often identical, they are treated as separate source fields. ### Departments and locations The department stored in Microsoft Entra ID is mapped to a department group in equipme. The value from the Entra office location field is mapped to a location in equipme. When a matching department group or location does not yet exist, it is created during synchronization. The employee is then assigned to the corresponding structure. | **Source value** | **Result in equipme** | | ------------------------ | --------------------------------------------------------- | | Existing department | The employee is assigned to the existing department group | | New department | A new department group is created and assigned | | Existing office location | The employee is assigned to the existing location | | New office location | A new location is created and assigned | Microsoft Entra ID does not provide a dedicated location object with its own address data. The `officeLocation` field only supplies the location name used for the assignment. As a result, locations created through the Entra synchronization do not contain an address. The address must be added and maintained directly in equipme after the location has been created. Ich würde außerdem die Location-Zeile in der Haupttabelle leicht anpassen: | **Microsoft Entra ID field** | **Microsoft Graph property** | **Field in equipme** | **Behavior in equipme** | | ---------------------------- | ---------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Office location | `officeLocation` | Location | The employee is assigned to the corresponding location. A new location is created if it does not yet exist. Newly created locations do not include an address | ### Personnel number and cost center The Entra employee ID is transferred to the **Personnel number** field in equipme. The standard source for the cost center is: `employeeOrgData.costCenter` The value is transferred to the employee’s **Cost center** field in equipme. Some organizations maintain information such as the cost center or company location in another Entra attribute. In these cases, the source field can be adjusted as part of the HR Sync configuration, provided the required information is available as a suitable single value field. ### Supervisor The manager assigned to a user in Microsoft Entra ID is used to populate the **Supervisor** field in equipme. This allows the reporting relationship maintained in Entra to be represented in the employee structure in equipme. ### Optional home office address The contact address stored in Microsoft Entra ID is not transferred as a home office address in the standard configuration. The address mapping can be enabled separately when the address data in Entra is maintained as the employee’s actual home office address. Before enabling this option, the organization should verify that the Entra address fields contain the intended employee address and not a general company or office address. ### Scope of this overview This table documents the standard Microsoft Entra ID mapping currently used for HR Sync. The mapping is not a universal field list for every HR Sync connection. Other connected systems may provide different employee attributes, and individual mappings may be adjusted during configuration when an organization maintains information in different source fields. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hub.equipme.io/equipme/settings-1/integrations/hr-sync-overview/microsoft-entra-id-field-mapping-for-hr-sync.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.