Microsoft Entra IDCustomize Application Attributes
In brief
> [!NOTE]
Documentation change
- 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.
- 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.
diff --git a/docs/identity/app-provisioning/customize-application-attributes.md b/docs/identity/app-provisioning/customize-application-attributes.md index 4cabbc9aafd..9acb43d50ce 100644 --- a/docs/identity/app-provisioning/customize-application-attributes.md +++ b/docs/identity/app-provisioning/customize-application-attributes.md @@ -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).