Attribute mapping - Active Directory to Microsoft Entra ID
In brief
The article received minor Markdown formatting and whitespace corrections, including the attribute table header and instructional text.
What Entra admins need to know
No administrator action is required; the guidance is easier to read.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Attribute mapping - Active Directory to Microsoft Entra ID
You can use the cloud sync attribute mapping feature to map attributes between your on-premises user or group objects and the objects in Microsoft Entra ID.
:::image type="content" source="media/how-to-attribute-mapping/new-ux-mapping-1.png" alt-text="Screenshot of new UX screen attribute mapping." lightbox="media/how-to-attribute-mapping/new-ux-mapping-1.png":::
The list of new mappings that were added.
| Attribute Added | Mapping Type | Added with Agent Version |
|---|---|---|
| preferredDatalocation | Direct | 1.1.359.0 |
| EmployeeNumber | Direct | 1.1.359.0 |
Source attribute: The user attribute from the source system (example: Active Directory).
Target attribute: The user attribute in the target system (example: Microsoft Entra ID).
Default value if null (optional): The value that is passed to the target system if the source attribute is null. This value is provisioned only when a user is created. It won't be provisioned when you're updating an existing user.
Apply this mapping:
- Always: Apply this mapping on both user-creation and update actions.
- Only during creation: Apply this mapping only on user-creation actions. The following are the attributes supported by an expression mapping:
Expression: This expression is the expression that is going to be applied to the target attribute. For more information, see Expression Builder and Writing expressions for attribute mappings in Microsoft Entra ID.
Default value if null (optional): The value that is passed to the target system if the source attribute is null. This value is provisioned only when a user is created. It won't be provisioned when you're updating an existing user.
Target attribute: The user attribute in the target system (example: Microsoft Entra ID).
Apply this mapping:
- Always: Apply this mapping on both user-creation and update actions.
- Only during creation: Apply this mapping only on user-creation actions.
Select the mapping type. This can be one of the following:
- Direct: The target attribute is populated with the value of an attribute of the linked object in Active Directory.
- Constant: The target attribute is populated with a specific string that you specify.
- Expression: The target attribute is populated based on the result of a script-like expression.
- None: The target attribute is left unmodified.
Depending on what you have selected in the previous step, different options are available for filling in.
Select when to apply this mapping, and then select Apply. :::image type="content" source="media/how-to-attribute-mapping/new-ux-mapping-4.png" alt-text="Screenshot of saving an attribute mapping." lightbox="media/how-to-attribute-mapping/new-ux-mapping-4.png":::
Test your attribute mapping
To test your attribute mapping, you can use on-demand provisioning:
[!INCLUDE sign in] 3. Under Configuration, select your configuration. 4. On the left, select Provision on demand. 5. Enter the distinguished name of a user and select the Provision button.
:::image type="content" source="media/how-to-on-demand-provision/new-ux-2.png" alt-text="Screenshot of user distinguished name." lightbox="media/how-to-on-demand-provision/new-ux-2.png":::
- A success screen appears with four green check marks. Any errors appear to the left.
:::image type="content" source="media/how-to-on-demand-provision/new-ux-3.png" alt-text="Screenshot of on-demand success." lightbox="media/how-to-on-demand-provision/new-ux-3.png":::
@@ -8,7 +8,7 @@ ms.subservice: hybrid-cloud-sync --- # Attribute mapping - Active Directory to Microsoft Entra ID-You can use the cloud sync attribute mapping feature to map attributes between your on-premises user or group objects and the objects in Microsoft Entra ID. +You can use the cloud sync attribute mapping feature to map attributes between your on-premises user or group objects and the objects in Microsoft Entra ID. :::image type="content" source="media/how-to-attribute-mapping/new-ux-mapping-1.png" alt-text="Screenshot of new UX screen attribute mapping." lightbox="media/how-to-attribute-mapping/new-ux-mapping-1.png"::: @@ -41,7 +41,7 @@ Cloud sync occasionally updates the schema and the list of default attributes th The list of new mappings that were added. -Attribute Added | Mapping Type | Added with Agent Version+|Attribute Added | Mapping Type | Added with Agent Version| | ----- | -----| -----| |preferredDatalocation|Direct|1.1.359.0| |EmployeeNumber|Direct|1.1.359.0|@@ -61,7 +61,7 @@ The following are the attributes supported by a direct mapping: - **Source attribute**: The user attribute from the source system (example: Active Directory). - **Target attribute**: The user attribute in the target system (example: Microsoft Entra ID).-- **Default value if null (optional)**: The value that is passed to the target system if the source attribute is null. This value is provisioned only when a user is created. It won't be provisioned when you're updating an existing user. +- **Default value if null (optional)**: The value that is passed to the target system if the source attribute is null. This value is provisioned only when a user is created. It won't be provisioned when you're updating an existing user. - **Apply this mapping**: - **Always**: Apply this mapping on both user-creation and update actions. - **Only during creation**: Apply this mapping only on user-creation actions.@@ -81,9 +81,9 @@ The following are the attributes supported by a constant mapping: The following are the attributes supported by an expression mapping: - **Expression**: This expression is the expression that is going to be applied to the target attribute. For more information, see [Expression Builder](how-to-expression-builder.md) and [Writing expressions for attribute mappings in Microsoft Entra ID](reference-expressions.md).-- **Default value if null (optional)**: The value that is passed to the target system if the source attribute is null. This value is provisioned only when a user is created. It won't be provisioned when you're updating an existing user. +- **Default value if null (optional)**: The value that is passed to the target system if the source attribute is null. This value is provisioned only when a user is created. It won't be provisioned when you're updating an existing user. - **Target attribute**: The user attribute in the target system (example: Microsoft Entra ID).- + - **Apply this mapping**: - **Always**: Apply this mapping on both user-creation and update actions. - **Only during creation**: Apply this mapping only on user-creation actions.@@ -103,10 +103,10 @@ Use the following steps for configuring attribute mapping with a [AD to Microsof 7. Select the mapping type. This can be one of the following: - **Direct**: The target attribute is populated with the value of an attribute of the linked object in Active Directory. - **Constant**: The target attribute is populated with a specific string that you specify.- - **Expression**: The target attribute is populated based on the result of a script-like expression. - - **None**: The target attribute is left unmodified. - - 8. Depending on what you have selected in the previous step, different options are available for filling in. + - **Expression**: The target attribute is populated based on the result of a script-like expression.+ - **None**: The target attribute is left unmodified.++ 8. Depending on what you have selected in the previous step, different options are available for filling in. 9. Select when to apply this mapping, and then select **Apply**. :::image type="content" source="media/how-to-attribute-mapping/new-ux-mapping-4.png" alt-text="Screenshot of saving an attribute mapping." lightbox="media/how-to-attribute-mapping/new-ux-mapping-4.png"::: @@ -120,18 +120,18 @@ Use the following steps for configuring attribute mapping with a [AD to Microsof ## Test your attribute mapping -To test your attribute mapping, you can use [on-demand provisioning](how-to-on-demand-provision.md): +To test your attribute mapping, you can use [on-demand provisioning](how-to-on-demand-provision.md): [!INCLUDE [sign in](../../../includes/cloud-sync-sign-in.md)] 3. Under **Configuration**, select your configuration. 4. On the left, select **Provision on demand**. 5. Enter the distinguished name of a user and select the **Provision** button.- - :::image type="content" source="media/how-to-on-demand-provision/new-ux-2.png" alt-text="Screenshot of user distinguished name." lightbox="media/how-to-on-demand-provision/new-ux-2.png"::: ++ :::image type="content" source="media/how-to-on-demand-provision/new-ux-2.png" alt-text="Screenshot of user distinguished name." lightbox="media/how-to-on-demand-provision/new-ux-2.png"::: 6. A success screen appears with four green check marks. Any errors appear to the left. - :::image type="content" source="media/how-to-on-demand-provision/new-ux-3.png" alt-text="Screenshot of on-demand success." lightbox="media/how-to-on-demand-provision/new-ux-3.png"::: + :::image type="content" source="media/how-to-on-demand-provision/new-ux-3.png" alt-text="Screenshot of on-demand success." lightbox="media/how-to-on-demand-provision/new-ux-3.png"::: 