Microsoft Entra IDCustomize Application Attributes
In brief
The application attribute customization article now links to guidance on extending attribute mappings with LCW extensibility workflows.
What Entra admins need to know
Administrators can use the new link to find more information about this mapping type; no product behavior change is indicated.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
Open on Microsoft Learn ↗The comparison below is an extract of the Microsoft Learn article showing only the changed content. Open the full article for complete context.
- LCW extensibility workflow - The target attribute is populated with the value generated by an Azure Logic app, which is triggered by an LCW extensibility workflow. For more information about this mapping type, see Extend attribute mappings with LCW extensibility workflows.
- None - the target attribute is left unmodified. However, if the target attribute is ever empty, it populates with the default value that you specify.
Along with these four basic types, custom attribute-mappings support the concept of an optional default value assignment. The default value assignment ensures that a target attribute is populated with a value if there's not a value in Microsoft Entra ID or on the target object. The most common configuration is to leave this blank. For more information about mapping attributes, see How Application Provisioning works in Microsoft Entra ID.
@@ -61,7 +61,7 @@ There are four different mapping types supported: > [!NOTE] > The maximum supported length for a single attribute mapping expression is **10,000 characters**. -- **LCW extensibility workflow** - The target attribute is populated with the value generated by an Azure Logic app, which is triggered by an LCW extensibility workflow.+- **LCW extensibility workflow** - The target attribute is populated with the value generated by an Azure Logic app, which is triggered by an LCW extensibility workflow. For more information about this mapping type, see [Extend attribute mappings with LCW extensibility workflows](~/identity/app-provisioning/extend-application-attributes.md). - **None** - the target attribute is left unmodified. However, if the target attribute is ever empty, it populates with the default value that you specify. Along with these four basic types, custom attribute-mappings support the concept of an optional **default** value assignment. The default value assignment ensures that a target attribute is populated with a value if there's not a value in Microsoft Entra ID or on the target object. The most common configuration is to leave this blank. For more information about mapping attributes, see [How Application Provisioning works in Microsoft Entra ID](~/identity/app-provisioning/how-provisioning-works.md#mapping-attributes).