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:
- Develops custom workflows using GRAPH
Item Description Documentation Inbound Provisioning You have a process to create user accounts for employees in Microsoft Entra such as HR inbound from Workday or SuccessFactors, or MIM.
Alternatively you have a process to create user accounts in Active Directory and those accounts are provisioned to Microsoft Entra ID.Workday to Active Directory
Workday to Microsoft Entra ID
SuccessFactors to Active DirectorySuccessFactors to Microsoft Entra ID
Microsoft Entra Connect
Microsoft Entra Connect cloud sync
API-driven inbound provisioning (Public preview)Attribute synchronization The accounts in Microsoft Entra ID have the employeeHireDate and employeeLeaveDateTime attributes populated. The values might be populated when the accounts are created from an HR system or synchronized from AD using Microsoft Entra Connect or cloud sync. You have extra attributes that are used to determine the scope such as department, populated or the ability to populate, with data. How to synchronize attributes for Lifecycle Workflows
- Develops custom workflows using GRAPH
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 AccountSend Welcome EmailAdd User To Groups |
| Real-time employee termination | Remove user from all groupsRemove user from all TeamsDelete User Account |
| Pre-Offboarding of an employee | Remove user from selected groupsRemove 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.
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.
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
@@ -12,7 +12,7 @@ ms.custom: sfi-image-nochange [Lifecycle Workflows](what-are-lifecycle-workflows.md) 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. +- **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.@@ -25,8 +25,8 @@ Lifecycle Workflows are a [Microsoft Entra ID Governance](identity-governance-ov - 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? - + - 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](~/architecture/deployment-plans.md).@@ -63,7 +63,7 @@ For Lifecycle Workflows, you'll likely include representatives from the followin - **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 + * Identifies and suggests alternate attributes that could be mapped to employeeHireDate and employeeLeaveDateTime - **Development teams** build and maintain applications for your organization. This team: * Develops custom workflows using GRAPH@@ -95,13 +95,13 @@ The following is important information about your organization and the technolog |Item|Description|Documentation| |-----|-----|-----| |Inbound Provisioning|You have a process to create user accounts for employees in Microsoft Entra such as HR inbound from Workday or SuccessFactors, or MIM.<br><br> Alternatively you have a process to create user accounts in Active Directory and those accounts are provisioned to Microsoft Entra ID.|[Workday to Active Directory](~/identity/saas-apps/workday-inbound-tutorial.md)<br><br>[Workday to Microsoft Entra ID](~/identity/saas-apps/workday-inbound-tutorial.md)<br><br>[SuccessFactors to Active Directory](~/identity/saas-apps/sap-successfactors-inbound-provisioning-tutorial.md)</br></br>[SuccessFactors to Microsoft Entra ID](~/identity/saas-apps/sap-successfactors-inbound-provisioning-cloud-only-tutorial.md)<br><br>[Microsoft Entra Connect](~/identity/hybrid/connect/whatis-azure-ad-connect-v2.md)<br><br>[Microsoft Entra Connect cloud sync](~/identity/hybrid/cloud-sync/what-is-cloud-sync.md)<br><br>[API-driven inbound provisioning (Public preview)](~/identity/app-provisioning/inbound-provisioning-api-configure-app.md)|-|Attribute synchronization|The accounts in Microsoft Entra ID have the employeeHireDate and employeeLeaveDateTime attributes populated. The values might be populated when the accounts are created from an HR system or synchronized from AD using Microsoft Entra Connect or cloud sync. You have extra attributes that are used to determine the scope such as department, populated or the ability to populate, with data.|[How to synchronize attributes for Lifecycle Workflows](how-to-lifecycle-workflow-sync-attributes.md)+|Attribute synchronization|The accounts in Microsoft Entra ID have the employeeHireDate and employeeLeaveDateTime attributes populated. The values might be populated when the accounts are created from an HR system or synchronized from AD using Microsoft Entra Connect or cloud sync. You have extra attributes that are used to determine the scope such as department, populated or the ability to populate, with data.|[How to synchronize attributes for Lifecycle Workflows](how-to-lifecycle-workflow-sync-attributes.md)| ## 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](understanding-lifecycle-workflows.md) document uses the portal to explain the parts of a workflow. The [Developer API reference Lifecycle Workflows](/graph/api/resources/identitygovernance-workflow) document uses a Graph example to explain the parts of a workflow. +The [Understanding Lifecycle Workflows](understanding-lifecycle-workflows.md) document uses the portal to explain the parts of a workflow. The [Developer API reference Lifecycle Workflows](/graph/api/resources/identitygovernance-workflow) 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. @@ -142,7 +142,7 @@ Before building a Lifecycle Workflow in the portal, you should determine which s |Scenario|Predefined Tasks| |-----|-----|-|Onboard prehire employee| Generate TAP and Send Email| +|Onboard prehire employee| Generate TAP and Send Email| |Onboard new hire employee|Enable User Account</br>Send Welcome Email</br>Add User To Groups| |Real-time employee termination|Remove user from all groups</br>Remove user from all Teams</br>Delete User Account| |Pre-Offboarding of an employee|Remove user from selected groups</br>Remove user from selected Teams|@@ -165,7 +165,7 @@ An Execution condition is the part of a workflow that defines the scope of **who 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. +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.@@ -173,7 +173,7 @@ The scope of a workflow uses attributes under the rule section. You can add the - And not - Or - Or not- + You can also choose from the numerous user attributes as well. [](media/lifecycle-workflows-deployment/attribute-1.png#lightbox)@@ -182,7 +182,7 @@ However before selecting an attribute to use in your execution condition, you ne 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 +### 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.@@ -216,14 +216,14 @@ Now that you've determined the scenario and the who and when, you should conside |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| +|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](lifecycle-workflow-tasks.md). ### 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. +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. [](media/lifecycle-workflows-deployment/group-1.png#lightbox) @@ -232,13 +232,13 @@ By selecting the task, you're presented with a navigation bar to add or remove g [](media/lifecycle-workflows-deployment/group-2.png#lightbox) ### 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. +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. +- **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. +- **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](lifecycle-workflow-extensibility.md) ## Create your workflow@@ -280,7 +280,7 @@ You can also get more information from the audit logs. These logs can be access |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.+|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 


