Understanding lifecycle workflows
In brief
The documentation now describes one Time based attribute trigger supporting exact day offsets and relative time ranges, with Equal to, Between, and Within comparisons. Separate preview-choice wording was removed.
What Entra admins need to know
Admins should use the updated trigger terminology and comparison guidance when configuring lifecycle workflows.
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.
Understanding lifecycle workflows
- Attribute changes
- Group membership change
- Time based attribute
- Sign-in inactivity
The type of workflow you choose determines which trigger you use.
Scope
To view a detailed guide on customizing the schedule of a workflow, see: Customize the schedule of workflows
To view a detailed guide on customizing the schedule of a workflow, see: Customize the schedule of workflows.
@@ -3,8 +3,8 @@ title: 'Understanding lifecycle workflows' description: Describes an overview of Lifecycle workflows and the various parts. ms.subservice: lifecycle-workflows ms.topic: concept-article-ms.date: 11/03/2026-ms.custom: sfi-image-nochange, msecd-doc-authoring-1026+ms.date: 11/10/2026+ms.custom: sfi-image-nochange #Customer Intent: As an IT admin, I want to understand lifecycle workflows and their components so that I can effectively use them to automate identity lifecycle processes. --- # Understanding lifecycle workflows @@ -127,13 +127,13 @@ The supported scheduled triggers are: - Attribute changes - Group membership change-- Time based+- Time based attribute - Sign-in inactivity The type of workflow you choose determines which trigger you use. > [!IMPORTANT]-> Relative time-based comparisons expand the time-based attribute trigger and are in public preview. During public preview, the Microsoft Entra admin center temporarily shows **Time based attribute** and **Time based attribute V2 (Preview)** as separate choices. Both choices represent the same time-based trigger capability, and the V2 choice can also reproduce the standard time-based behavior. At general availability, customers will see only one time-based trigger choice that includes relative comparisons. For supported comparisons and configuration details, see [Time based attribute trigger](lifecycle-workflow-execution-conditions.md#time-based-attribute-trigger). For more information about previews, see [Universal License Terms for Online Services](https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all).+> The **Time based attribute** trigger supports exact day offsets and relative time ranges. For supported comparisons and configuration details, see [Time based attribute trigger](lifecycle-workflow-execution-conditions.md#time-based-attribute-trigger). ## Scope @@ -157,7 +157,7 @@ Once scheduling is enabled, the workflow is evaluated based on the interval that [](media/understanding-lifecycle-workflows/workflow-10.png#lightbox) >[!NOTE]-> The standard time based attribute choice processes a user at a specific point in time based on the workflow configuration (e.g., seven days before the user’s hire date) and user account configuration. For reliable workflow execution, the user account must be configured with all relevant details (e.g., trigger and scoping attributes) in advance of the scheduled workflow execution. Once the designated time arrives, the next scheduled workflow run will process the user if it meets the execution conditions. If the workflow or user account is configured after the intended processing time (e.g., due to a delay in the HR system), Lifecycle Workflows will still attempt to process the user—provided the necessary setup is completed within three days of the original processing time. This catch-up behavior doesn't apply when you select **Time based attribute V2 (Preview)** during public preview.+> The **Time based attribute** trigger processes users whose date attribute meets the configured **Equal to**, **Between**, or **Within** comparison and whose accounts meet the scope rules. Configure the relevant trigger and scoping attributes before users need to meet the execution conditions. New workflows that use the updated trigger don't have an automatic three-day catch-up window. Existing workflows aren't affected by this change and retain their current catch-up behavior. To allow for delays in user data updates in new workflows, configure a relative time range with **Between** or **Within**. For details and examples, see [Time based attribute trigger](lifecycle-workflow-execution-conditions.md#time-based-attribute-trigger). To view a detailed guide on customizing the schedule of a workflow, see: [Customize the schedule of workflows](customize-workflow-schedule.md). 
