Microsoft Entra ID

Reference for extending Microsoft Entra attribute mappings with custom call-outs using LCW extensibility workflows

23 September 2026Doc update+1 / −1 lines

In brief

The article title no longer includes “(preview)” for custom call-outs using LCW extensibility workflows.

What Entra admins need to know

Administrators will see the updated title when locating this guidance; no action is specified.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Reference for extending Microsoft Entra attribute mappings with custom call-outs using LCW extensibility workflows (preview)

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.

@@ -7,7 +7,7 @@ ms.reviewer: addimitu ai-usage: ai-assisted --- -# Reference for extending Microsoft Entra attribute mappings with custom call-outs using LCW extensibility workflows (preview)+# Reference for extending Microsoft Entra attribute mappings with custom call-outs using LCW extensibility workflows  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.