Microsoft Entra ID Governance
GovernanceExtend Application Attributes
In brief
The documentation now uses clearer wording for configuring LCW extensibility workflow mappings, creating an Azure Logic App and workflow, and configuring provisioning jobs with attribute mappings.
What Entra admins need to know
No administrative action is required; the setup guidance is easier to follow.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
When you configure provisioning, one of the types of attribute mappings that you can specify is the Lifecycle Workflows (LCW) extensibility workflow mapping type. This mapping type allows you to extend attribute mappings beyond the basic transformations that are supported by the expression mapping type, enabling you to fulfill scenarios where custom business logic may be required.
To configure the LCW extensibility workflow mapping type, you will need to create anleverage the LCW extensibility workflow that invokes an Azure Logic App to generate a value. The value generated by the Azure Logic App is then applied to a target attribute.
Prerequisites
You will need toTo create an Azure Logic App. For that,App, ensure you should have:
- An Azure subscription (required for creating and using an Azure Logic App)
- At least a Logic App Contributor role
You will need toTo create an LCW extensibility workflow to trigger the Azure Logic App. For that,App, ensure you should have:
- An Entra ID Governance license
- At least a Lifecycle Workflows Administrator role
To configure a provisioning job, including attribute mappings, ensure you will need:have:
- At least an Application Administrator role. If you are configuring inbound provisioning to an on-prem Active Directory, the the Hybrid Identity Administrator role is also required
@@ -11,20 +11,20 @@ ai-usage: ai-assisted When you configure provisioning, one of the types of attribute mappings that you can specify is the Lifecycle Workflows (LCW) extensibility workflow mapping type. This mapping type allows you to extend attribute mappings beyond the basic transformations that are supported by the [expression mapping type](~/identity/app-provisioning/functions-for-customizing-application-data.md), enabling you to fulfill scenarios where custom business logic may be required. -To configure the LCW extensibility workflow mapping type, you will need to create an LCW extensibility workflow that invokes an Azure Logic App to generate a value. The value generated by the Azure Logic App is then applied to a target attribute.+To configure the LCW extensibility workflow mapping type, you will leverage the LCW extensibility workflow that invokes an Azure Logic App to generate a value. The value generated by the Azure Logic App is then applied to a target attribute. ## Prerequisites -You will need to create an Azure Logic App. For that, you should have:+To create an Azure Logic App, ensure you have: - An [Azure subscription](https://azure.microsoft.com/pricing/purchase-options/azure-account) (required for creating and using an Azure Logic App) - At least a [Logic App Contributor](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/integration#logic-app-contributor) role -You will need to create an LCW extensibility workflow to trigger the Azure Logic App. For that, you should have:+To create an LCW extensibility workflow to trigger the Azure Logic App, ensure you have: - An [Entra ID Governance license](~/id-governance/licensing-fundamentals.md) - At least a [Lifecycle Workflows Administrator](~/identity/role-based-access-control/permissions-reference.md#lifecycle-workflows-administrator) role -To configure a provisioning job, including attribute mappings, you will need:+To configure a provisioning job, including attribute mappings, ensure you have: - At least an [Application Administrator](~/identity/role-based-access-control/permissions-reference.md#application-administrator) role. If you are configuring inbound provisioning to an on-prem Active Directory, the the [Hybrid Identity Administrator](~/identity/role-based-access-control/permissions-reference.md#hybrid-identity-administrator) role is also required