Merge pull request #234498 from OWinfreyATL/owinfreyATL-Task-Acrolinx

Tasks acrolinx check

Author: prmerger-automator[bot]

articles/active-directory/governance/lifecycle-workflow-tasks.md

@@ -12,7 +12,7 @@ ms.date: 01/26/2023
 ---
 # Lifecycle Workflow built-in tasks (Preview)
 
-Lifecycle Workflows come with many pre-configured tasks that are designed to automate common lifecycle management scenarios. These built-in tasks can be utilized to make customized workflows to suit your organization's needs. These tasks can be configured within seconds to create new workflows. These tasks also have categories based on the Joiner-Mover-Leaver model so that they can be easily placed into workflows based on need. In this article you'll get the complete list of tasks, information on common parameters each task has, and a list of unique parameters needed for each specific task.
+Lifecycle Workflows come with many pre-configured tasks that are designed to automate common lifecycle management scenarios. These built-in tasks can be utilized to make customized workflows to suit your organization's needs. These tasks can be configured within seconds to create new workflows. These tasks also have categories based on the Joiner-Mover-Leaver model so that they can be easily placed into workflows based on need. In this article you get the complete list of tasks, information on common parameters each task has, and a list of unique parameters needed for each specific task.
 
 
 ## Supported tasks
@@ -30,10 +30,10 @@ Common task parameters are the non-unique parameters contained in every task. Wh
 |---------|---------|
 |category     |  A  read-only string that identifies the category or categories of the task. Automatically determined when the taskDefinitionID is chosen.     |
 |taskDefinitionId     | A string referencing a taskDefinition that determines which task to run.       |
-|isEnabled     | A boolean value that denotes whether the task is set to run or not. If set to “true" then the task will run. Defaults to true.       |
+|isEnabled     | A boolean value that denotes whether the task is set to run or not. If set to “true" then the task runs. Defaults to true.       |
 |displayName     |  A unique string that identifies the task.       |
 |description     | A string that describes the purpose of the task for administrative use. (Optional)         |
-|executionSequence     | A read-only integer that states in what order the task will run in a workflow. For more information about executionSequence and workflow order, see: [Configure Scope](understanding-lifecycle-workflows.md#configure-scope).       |
+|executionSequence     | A read-only integer that states in what order the task runs in a workflow. For more information about executionSequence and workflow order, see: [Configure Scope](understanding-lifecycle-workflows.md#configure-scope).       |
 |continueOnError     |  A boolean value that determines if the failure of this task stops the subsequent workflows from running.        |
 |arguments     |  Contains unique parameters relevant for the given task.       |
 
@@ -43,7 +43,7 @@ Emails, sent from tasks, are able to be customized. If you choose to customize t
 
 - **Subject:** Customizes the subject of emails.
 - **Message body:** Customizes the body of the emails being sent out.
-- **Email language translation:** Overrides the email recipient's language settings. Custom text is not customized, and it is recommended to set this language to the same language as the custom text. 
+- **Email language translation:** Overrides the email recipient's language settings. Custom text isn't customized, and it's recommended to set this language to the same language as the custom text. 
 
 :::image type="content" source="media/lifecycle-workflow-task/customize-email-concept.png" alt-text="Screenshot of the customization email options.":::
 
@@ -87,7 +87,7 @@ The Azure AD prerequisite to run the **Send welcome email to new hire** task is:
 - A populated mail attribute for the user.
 
 
-For Microsoft Graph the parameters for the **Send welcome email to new hire** task are as follows:
+For Microsoft Graph, the parameters for the **Send welcome email to new hire** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -141,7 +141,7 @@ The Azure AD prerequisite to run the **Send onboarding reminder email** task is:
 - A populated manager's mail attribute for the user.
 
 
-For Microsoft Graph the parameters for the **Send onboarding reminder email** task are as follows:
+For Microsoft Graph, the parameters for the **Send onboarding reminder email** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -204,7 +204,7 @@ The Azure AD prerequisites to run the **Generate Temporary Access Pass and send
 > [!IMPORTANT]
 > A user having this task run for them in a workflow must also not have any other authentication methods, sign-ins, or AAD role assignments for this task to work for them.
 
-For Microsoft Graph the parameters for the **Generate Temporary Access Pass and send via email to user's manager** task are as follows:
+For Microsoft Graph, the parameters for the **Generate Temporary Access Pass and send via email to user's manager** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -256,14 +256,14 @@ For Microsoft Graph the parameters for the **Generate Temporary Access Pass and
 ### Add user to groups
 
 
-Allows users to be added to Microsoft 365 and cloud-only security groups. Mail-enabled, distribution, dynamic and role-assignable groups are not supported. To control access to on-premises applications and resources, you need to enable group writeback. For more information, see [Azure AD Connect group writeback](../hybrid/how-to-connect-group-writeback-v2.md). 
+Allows users to be added to Microsoft 365 and cloud-only security groups. Mail-enabled, distribution, dynamic and role-assignable groups aren't supported. To control access to on-premises applications and resources, you need to enable group writeback. For more information, see [Azure AD Connect group writeback](../hybrid/how-to-connect-group-writeback-v2.md). 
 
 
 You're able to customize the task name and description for this task.
 :::image type="content" source="media/lifecycle-workflow-task/add-group-task.png" alt-text="Screenshot of Workflows task: Add user to group task.":::
 
 
-For Microsoft Graph the parameters for the **Add user to groups** task are as follows:
+For Microsoft Graph, the parameters for the **Add user to groups** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -299,7 +299,7 @@ You're able to add a user to an existing static team. You're able to customize t
 :::image type="content" source="media/lifecycle-workflow-task/add-team-task.png" alt-text="Screenshot of Workflows task: add user to team.":::
 
 
-For Microsoft Graph the parameters for the **Add user to teams** task are as follows:
+For Microsoft Graph, the parameters for the **Add user to teams** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -331,12 +331,12 @@ For Microsoft Graph the parameters for the **Add user to teams** task are as fol
 
 ### Enable user account
 
-Allows cloud-only user accounts to be enabled. Users with Azure AD role assignments are not supported, nor are users with membership or ownership of role-assignable groups. You can utilize Azure Active Directory's HR driven provisioning to on-premises Active Directory to disable and enable synchronized accounts with an attribute mapping to `accountDisabled` based on data from your HR source. For more information, see: [Workday Configure attribute mappings](../saas-apps/workday-inbound-tutorial.md#part-4-configure-attribute-mappings) and [SuccessFactors Configure attribute mappings](../saas-apps/sap-successfactors-inbound-provisioning-tutorial.md#part-4-configure-attribute-mappings). You're able to customize the task name and description for this task in the Azure portal.
+Allows cloud-only user accounts to be enabled. Users with Azure AD role assignments aren't supported, nor are users with membership or ownership of role-assignable groups. You can utilize Azure Active Directory's HR driven provisioning to on-premises Active Directory to disable and enable synchronized accounts with an attribute mapping to `accountDisabled` based on data from your HR source. For more information, see: [Workday Configure attribute mappings](../saas-apps/workday-inbound-tutorial.md#part-4-configure-attribute-mappings) and [SuccessFactors Configure attribute mappings](../saas-apps/sap-successfactors-inbound-provisioning-tutorial.md#part-4-configure-attribute-mappings). You're able to customize the task name and description for this task in the Azure portal.
 
 :::image type="content" source="media/lifecycle-workflow-task/enable-task.png" alt-text="Screenshot of Workflows task: enable user account.":::
 
 
-For Microsoft Graph the parameters for the **Enable user account** task are as follows:
+For Microsoft Graph, the parameters for the **Enable user account** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -370,7 +370,7 @@ The Azure AD prerequisite to run the **Run a Custom Task Extension** task is:
 
 - A Logic App that is compatible with the custom task extension. For more information, see: [Lifecycle workflow extensibility](lifecycle-workflow-extensibility.md).
 
-For Microsoft Graph the parameters for the **Run a Custom Task Extension** task are as follows:
+For Microsoft Graph, the parameters for the **Run a Custom Task Extension** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -405,12 +405,12 @@ For more information on setting up a Logic app to run with Lifecycle Workflows,
 
 ### Disable user account
 
-Allows cloud-only user accounts to be disabled. Users with Azure AD role assignments are not supported, nor are users with membership or ownership of role-assignable groups. You can utilize Azure Active Directory's HR driven provisioning to on-premises Active Directory to disable and enable synchronized accounts with an attribute mapping to `accountDisabled` based on data from your HR source. For more information, see: [Workday Configure attribute mappings](../saas-apps/workday-inbound-tutorial.md#part-4-configure-attribute-mappings) and [SuccessFactors Configure attribute mappings](../saas-apps/sap-successfactors-inbound-provisioning-tutorial.md#part-4-configure-attribute-mappings). You're able to customize the task name and description for this task in the Azure portal.
+Allows cloud-only user accounts to be disabled. Users with Azure AD role assignments aren't supported, nor are users with membership or ownership of role-assignable groups. You can utilize Azure Active Directory's HR driven provisioning to on-premises Active Directory to disable and enable synchronized accounts with an attribute mapping to `accountDisabled` based on data from your HR source. For more information, see: [Workday Configure attribute mappings](../saas-apps/workday-inbound-tutorial.md#part-4-configure-attribute-mappings) and [SuccessFactors Configure attribute mappings](../saas-apps/sap-successfactors-inbound-provisioning-tutorial.md#part-4-configure-attribute-mappings). You're able to customize the task name and description for this task in the Azure portal.
 
 :::image type="content" source="media/lifecycle-workflow-task/disable-task.png" alt-text="Screenshot of Workflows task: disable user account.":::
 
 
-For Microsoft Graph the parameters for the **Disable user account** task are as follows:
+For Microsoft Graph, the parameters for the **Disable user account** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -435,15 +435,15 @@ For Microsoft Graph the parameters for the **Disable user account** task are as
 
 ### Remove user from selected groups
 
-Allows users to be removed from Microsoft 365 and cloud-only security groups. Mail-enabled, distribution, dynamic and role-assignable groups are not supported. To control access to on-premises applications and resources, you need to enable group writeback. For more information, see [Azure AD Connect group writeback](../hybrid/how-to-connect-group-writeback-v2.md). 
+Allows users to be removed from Microsoft 365 and cloud-only security groups. Mail-enabled, distribution, dynamic and role-assignable groups aren't supported. To control access to on-premises applications and resources, you need to enable group writeback. For more information, see [Azure AD Connect group writeback](../hybrid/how-to-connect-group-writeback-v2.md). 
 
 
 You're able to customize the task name and description for this task in the Azure portal.
 :::image type="content" source="media/lifecycle-workflow-task/remove-group-task.png" alt-text="Screenshot of Workflows task: Remove user from select groups.":::
 
 
 
-For Microsoft Graph the parameters for the **Remove user from selected groups** task are as follows:
+For Microsoft Graph, the parameters for the **Remove user from selected groups** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -475,7 +475,7 @@ For Microsoft Graph the parameters for the **Remove user from selected groups**
 
 ### Remove users from all groups
 
-Allows users to be removed from every Microsoft 365 and cloud-only security group they're a member of. Mail-enabled, distribution, dynamic and role-assignable groups are not supported. To control access to on-premises applications and resources, you need to enable group writeback. For more information, see [Azure AD Connect group writeback](../hybrid/how-to-connect-group-writeback-v2.md).
+Allows users to be removed from every Microsoft 365 and cloud-only security group they're a member of. Mail-enabled, distribution, dynamic and role-assignable groups aren't supported. To control access to on-premises applications and resources, you need to enable group writeback. For more information, see [Azure AD Connect group writeback](../hybrid/how-to-connect-group-writeback-v2.md).
 
 
 
@@ -484,7 +484,7 @@ You're able to customize the task name and description for this task in the Azur
  :::image type="content" source="media/lifecycle-workflow-task/remove-all-groups-task.png" alt-text="Screenshot of Workflows task: remove user from all groups.":::
 
 
-For Microsoft Graph the parameters for the **Remove users from all groups** task are as follows:
+For Microsoft Graph, the parameters for the **Remove users from all groups** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -513,7 +513,7 @@ For Microsoft Graph the parameters for the **Remove users from all groups** task
 Allows a user to be removed from one or multiple static teams. You're able to customize the task name and description for this task in the Azure portal.
 :::image type="content" source="media/lifecycle-workflow-task/remove-user-team-task.png" alt-text="Screenshot of Workflows task: remove user from teams.":::
 
-For Microsoft Graph the parameters for the **Remove User from Teams** task are as follows:
+For Microsoft Graph, the parameters for the **Remove User from Teams** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -547,7 +547,7 @@ For Microsoft Graph the parameters for the **Remove User from Teams** task are a
 Allows users to be removed from every static team they're a member of. You're able to customize the task name and description for this task in the Azure portal.
 :::image type="content" source="media/lifecycle-workflow-task/remove-user-all-team-task.png" alt-text="Screenshot of Workflows task: remove user from all teams.":::
 
-For Microsoft Graph the parameters for the **Remove users from all teams** task are as follows:
+For Microsoft Graph, the parameters for the **Remove users from all teams** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -578,7 +578,7 @@ Allows all direct license assignments to be removed from a user. For group-based
 You're able to customize the task name and description for this task in the Azure portal.
 :::image type="content" source="media/lifecycle-workflow-task/remove-license-assignment-task.png" alt-text="Screenshot of Workflows task: remove all licenses from users.":::
 
-For Microsoft Graph the parameters for the **Remove all license assignment from user** task are as follows:
+For Microsoft Graph, the parameters for the **Remove all license assignment from user** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -604,11 +604,11 @@ For Microsoft Graph the parameters for the **Remove all license assignment from
 
 ### Delete User
 
-Allows cloud-only user accounts to be deleted. Users with Azure AD role assignments are not supported, nor are users with membership or ownership of role-assignable groups. You're able to customize the task name and description for this task in the Azure portal.
+Allows cloud-only user accounts to be deleted. Users with Azure AD role assignments aren't supported, nor are users with membership or ownership of role-assignable groups. You're able to customize the task name and description for this task in the Azure portal.
 :::image type="content" source="media/lifecycle-workflow-task/delete-user-task.png" alt-text="Screenshot of Workflows task: Delete user account.":::
 
 
-For Microsoft Graph the parameters for the **Delete User** task are as follows:
+For Microsoft Graph, the parameters for the **Delete User** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -692,7 +692,7 @@ The Azure AD prerequisite to run the **Send email on user last day** task are:
 - A populated manager attribute for the user.
 - A populated manager's mail attribute for the user.
 
-For Microsoft Graph the parameters for the **Send email on user last day** task are as follows:
+For Microsoft Graph, the parameters for the **Send email on user last day** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|
@@ -742,7 +742,7 @@ The Azure AD prerequisite to run the **Send email to users manager after their l
 - A populated manager's mail attribute for the user.
 
 
-For Microsoft Graph the parameters for the **Send email to users manager after their last day** task are as follows:
+For Microsoft Graph, the parameters for the **Send email to users manager after their last day** task are as follows:
 
 |Parameter |Definition  |
 |---------|---------|