Microsoft Entra ID Governance
Governance

Lifecycle Workflows Deployment

In brief

The deployment article was updated across existing workflow, provisioning, task, and rollout guidance, with only minor formatting or punctuation changes visible in the supplied diff.

What Entra admins need to know

No administrator action is required.

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.

Lifecycle Workflows help your organization to manage Microsoft Entra users by increasing automation. With Lifecycle Workflows, you can:

  • Extend your HR-driven provisioning process with other workflows that simplify and automate tasks.
  • Centralize your workflow process so you can easily create and manage workflows all in one location.
  • Troubleshoot workflow scenarios with the Workflow history and Audit logs with minimal effort.
  • Manage user lifecycle at scale. As your organization grows, the need for other resources to manage user lifecycles is lowered.
  • What are those users doing with that access?
  • Is there effective organizational control for managing access?
  • Can auditors verify that the controls are working?
  • Are users ready to go on day one or do they have access removed in a timely manner?

Planning your Lifecycle Workflow deployment is essential to make sure you achieve your desired governance strategy for users in your organization.

For more information on deployment plans, see Microsoft Entra deployment plans.

  • HR Representative - Assists with attribute mapping and population in HR provisioning scenarios. This team:

    • Helps determine attributes that are used to populate employeeHireDate and employeeLeaveDateTime.
    • Ensures source attributes are populated and have values
    • Identifies and suggests alternate attributes that could be mapped to employeeHireDate and employeeLeaveDateTime
  • Development teams build and maintain applications for your organization. This team:

Understanding parts of a workflow

Before you begin planning a Lifecycle Workflow deployment, you should become familiar with the parts of workflow and the terminology around Lifecycle Workflows.

The Understanding Lifecycle Workflows document uses the portal to explain the parts of a workflow. The Developer API reference Lifecycle Workflows document uses a Graph example to explain the parts of a workflow.

You can use this document to become familiar with the parts of workflow before deploying them.

Scenario Predefined Tasks
Onboard prehire employee Generate TAP and Send Email
Onboard new hire employee Enable User Account
Send Welcome Email
Add User To Groups
Real-time employee termination Remove user from all groups
Remove user from all Teams
Delete User Account
Pre-Offboarding of an employee Remove user from selected groups
Remove user from selected Teams

The scope determines who the workflow runs against. This is defined by a rule that will filter users based on a condition. For example, the rule, "rule": "(department eq 'sales')" runs the task only on users who are members of the sales department.

The trigger determines when the workflow runs. This can either be, on-demand, which is immediate, or run on a schedule. Most of the predefined templates in the portal are based to run on a schedule when their trigger is met.

Attribute information

The scope of a workflow uses attributes under the rule section. You can add the following extra conditionals to further refine who the tasks are applied to.

  • And not
  • Or
  • Or not

You can also choose from the numerous user attributes as well.

Screenshot of lifecycle workflow rule

Not all of these attributes are populated by default so you should verify with your HR administrator or IT administrators when using HR inbound cloud only provisioning, Microsoft Entra Connect, or cloud sync.

Time information

The following is some important information regarding time zones that you should be aware of when designing workflows.

  • Workday and SAP SF will always send the time in Coordinated Universal Time or UTC.
  • If you're in a single time zone, it's recommended that you hardcode the time portion to something that works for you. An example would be 5am for new hire scenarios and 10pm for last day of work scenarios. |Request user access package assignment|Request user assignment to selected access packages|Joiner - Mover| |Remove access package assignment for user|Remove user assignment from selected access packages| Leaver - Mover| |Remove all access package assignments for user|Remove all access package assignments for the user. When daysUntilExpiration is set, removal is scheduled rather than immediate.|Leaver - Mover| |Remove selected license assignments from user|Remove select license assignment from user|Leaver - Mover| |Cancel all pending access package assignment requests for users|Cancel all pending access package assignment requests for users|Leaver|

For more information on tasks, see Lifecycle Workflow tasks.

Group and team tasks

If you're using a group or team task, the workflow needs you to specify the group or groups. In the following screenshot, you see the yellow triangle on the task indicating that it's missing information.

Screenshot of onboard new hire.

Screenshot of add groups.

Custom task extensions

Lifecycle Workflows allow you to create workflows that can be triggered based on joiner, mover, or leaver scenarios. While Lifecycle Workflows provide several built-in tasks to automate common scenarios throughout the lifecycle of users, eventually you could reach the limits of these built-in tasks. With the extensibility feature, you're able to utilize the concept of custom task extensions to call-out to external systems as part of a Lifecycle Workflow.

The scenarios for how a custom task extension interacts with Lifecycle Workflows can be one of three ways:

  • Fire-and-forget scenario- The Logic App is started, and the sequential task execution immediately continues with no response expected from the Logic App.
  • Sequential task execution waiting for response from the Logic App - The Logic app is started, and the sequential task execution waits on the response from the Logic App.
  • Sequential task execution waiting for the response of a 3rd party system- The Logic app is started, and the sequential task execution waits on the response from a 3rd party system that triggers the Logic App to tell the Custom Task extension whether or not it ran successfully.
  • For more information on custom extensions, see Lifecycle Workflow extensibility

Create your workflow

|Create the workflow in the portal|Use the predefined template for new hire in the portal.| |Enable and test the workflow| Use the on-demand feature to test the workflow on one user.| |Review the test results|Review the test results and ensure the Lifecycle Workflow is working as intended.| |Roll out the workflow to a broader audience|Communicate with stakeholders, letting them know that it's going live and that HR will no longer need to send an email to the hiring manager.|

Next steps

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…