Microsoft Entra ID Governance
GovernanceLifecycle Workflow Execution Conditions
In brief
Documentation describes relative comparisons using Exactly, Between, or Less than or equal to, with event offsets from 0 to 180 days before or after supported user-attribute dates. The admin center temporarily shows two choices for the same time-based trigger.
What Entra admins need to know
Administrators can create workflows targeting relative periods around events such as hire, leave, or account creation. No configuration change is required.
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.
Relative time-based comparisons (preview)
The preview experience expands the time-based attribute trigger with relative comparisons. It includes the functionality of the standard time-based option and can also match users across a relative period. To configure these comparisons in a new or existing workflow, open Lifecycle Workflows in the Microsoft Entra admin center, and then select Time based attribute V2 (Preview) under Trigger details.
Configure the following trigger timing details:
| Trigger detail | Description |
|---|---|
| Operator | Select Exactly, Between, or Less than or equal to. |
| Days from event | Enter an offset from 0 through 180 days. When you select Between, also enter an offset from 0 through 180 days in Days to event. |
| Event timing | Select Before or After the event attribute date. To use the standard time-based behavior on the attribute date, select Exactly, enter 0 days, and select On. |
| Event attribute | Select any user attribute supported by the time-based trigger, including employeeHireDate, employeeLeaveDateTime, and createdDateTime. |
After configuring the trigger, continue through Configure scope, Review tasks, and Review + create. The workflow and its schedule must both be enabled for the trigger to be evaluated.
Workflow evaluation, scheduling, and processing work the same for both preview choices, except the Time based attribute V2 (Preview) choice doesn't have a three-day catch-up window. Workflows created during preview transition to the unified generally available experience without reconfiguration. Microsoft communicates any schema changes in advance.
Time based attribute scope
The time based attribute scope allows you to define for whom the workflow runs when the time trigger is met.
@@ -4,7 +4,7 @@ description: Conceptual article about Lifecycle workflows execution conditions. ms.subservice: lifecycle-workflows ms.workload: identity ms.topic: concept-article-ms.date: 03/12/2026+ms.date: 08/21/2026 ms.custom: template-concept #Customer Intent: As an IT admin, I want to understand lifecycle workflow execution conditions and scheduling so that I can configure when and how workflows run. ---@@ -52,6 +52,26 @@ When setting a workflow where the trigger type is **Time based attribute**, the > [!NOTE] > The event user attribute must be set within Microsoft Entra ID for users. For more information on this process, see: [How to synchronize attributes for Lifecycle workflows](how-to-lifecycle-workflow-sync-attributes.md). +### Relative time-based comparisons (preview)++> [!IMPORTANT]+> Relative time-based comparisons 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 time-based attribute trigger. When this capability becomes generally available, customers will see only one time-based trigger choice that includes relative comparisons. For more information about previews, see [Universal License Terms for Online Services](https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all).++The preview experience expands the time-based attribute trigger with relative comparisons. It includes the functionality of the standard time-based option and can also match users across a relative period. To configure these comparisons in a new or existing workflow, open [Lifecycle Workflows in the Microsoft Entra admin center](https://aka.ms/LCWRelativeTimeBasedTrigger), and then select **Time based attribute V2 (Preview)** under **Trigger details**.++Configure the following trigger timing details:++|Trigger detail|Description|+|---|---|+|Operator|Select **Exactly**, **Between**, or **Less than or equal to**.|+|Days from event|Enter an offset from 0 through 180 days. When you select **Between**, also enter an offset from 0 through 180 days in **Days to event**.|+|Event timing|Select **Before** or **After** the event attribute date. To use the standard time-based behavior on the attribute date, select **Exactly**, enter 0 days, and select **On**.|+|Event attribute|Select any user attribute supported by the time-based trigger, including `employeeHireDate`, `employeeLeaveDateTime`, and `createdDateTime`.|++After configuring the trigger, continue through **Configure scope**, **Review tasks**, and **Review + create**. The workflow and its schedule must both be enabled for the trigger to be evaluated.++Workflow evaluation, scheduling, and processing work the same for both preview choices, except the **Time based attribute V2 (Preview)** choice doesn't have a three-day catch-up window. Workflows created during preview transition to the unified generally available experience without reconfiguration. Microsoft communicates any schema changes in advance.+ ### Time based attribute scope The time based attribute scope allows you to define for whom the workflow runs when the time trigger is met.