Merge pull request #231083 from OWinfreyATL/owinfreyATL-LicensingCheck

Licensing feature updates
Fixed Acrolinx errors.

Author: Jill Grant

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

@@ -21,9 +21,7 @@ Workflows can be created and customized for common scenarios using templates, or
 
 ## Prerequisites
 
-- Azure AD Premium P2
-
-For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements)
+The Lifecycle Workflows preview requires Azure AD Premium P2. For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements).
 
 ## Create a Lifecycle workflow using a template in the Azure portal
 

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

@@ -20,9 +20,7 @@ You can remove workflows that are no longer needed. Deleting these workflows all
 
 ## Prerequisites
 
-- Azure AD Premium P2
-
-For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements)
+The Lifecycle Workflows preview requires Azure AD Premium P2. For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements).
 
 ## Delete a workflow using the Azure portal
 

articles/active-directory/governance/tutorial-offboard-custom-workflow-portal.md

@@ -28,9 +28,8 @@ You may learn more about running a workflow on-demand [here](on-demand-workflow.
 
 ## Prerequisites
 
-- Azure AD Premium P2
+The Lifecycle Workflows preview requires Azure AD Premium P2. For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements).
 
-For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements)
 
 ##  Before you begin
 

articles/active-directory/governance/tutorial-onboard-custom-workflow-portal.md

@@ -16,25 +16,23 @@ ms.custom: template-tutorial
 
 # Automate employee onboarding tasks before their first day of work with Azure portal (preview)
 
-This tutorial provides a step-by-step guide on how to automate pre-hire tasks with Lifecycle workflows using the Azure portal. 
+This tutorial provides a step-by-step guide on how to automate prehire tasks with Lifecycle workflows using the Azure portal. 
 
-This pre-hire scenario will generate a temporary access pass for our new employee and send it via email to the user's new manager.  
+This prehire scenario generates a temporary access pass for our new employee and sends it via email to the user's new manager.  
 
 :::image type="content" source="media/tutorial-lifecycle-workflows/arch-2.png" alt-text="Screenshot of the lifecycle workflow scenario." lightbox="media/tutorial-lifecycle-workflows/arch-2.png":::
 
 ## Prerequisites
 
-- Azure AD Premium P2
-
-For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements)
+The Lifecycle Workflows preview requires Azure AD Premium P2. For more information, see [License requirements](what-are-lifecycle-workflows.md#license-requirements).
 
 ##  Before you begin
 
 Two accounts are required for this tutorial, one account for the new hire and another account that acts as the manager of the new hire. The new hire account must have the following attributes set:
 
 -	employeeHireDate must be set to today
--	department must be set to sales
--	manager attribute must be set, and the manager account should have a mailbox to receive an email
+-	Department must be set to sales
+-	Manager attribute must be set, and the manager account should have a mailbox to receive an email
 
 For more comprehensive instructions on how to complete these prerequisite steps, you may refer to the [Preparing user accounts for Lifecycle workflows tutorial](tutorial-prepare-azure-ad-user-accounts.md). The [TAP policy](../authentication/howto-authentication-temporary-access-pass.md#enable-the-temporary-access-pass-policy) must also be enabled to run this tutorial.
 
@@ -47,7 +45,7 @@ Detailed breakdown of the relevant attributes:
  |employeeHireDate|Used to trigger the workflow|Employee|
  |department|Used to provide the scope for the workflow|Employee|
 
-The pre-hire scenario can be broken down into the following:
+The prehire scenario can be broken down into the following:
   - **Prerequisite:** Create two user accounts, one to represent an employee and one to represent a manager
   - **Prerequisite:** Editing the attributes required for this scenario in the portal
   - **Prerequisite:** Edit the attributes for this scenario using Microsoft Graph Explorer
@@ -57,9 +55,9 @@ The pre-hire scenario can be broken down into the following:
   - Verifying the workflow was successfully executed
 
 ## Create a workflow using pre-hire template
-Use the following steps to create a pre-hire workflow that will generate a TAP and send it via email to the user's manager using the Azure portal.
+Use the following steps to create a prehire workflow that will generate a TAP and send it via email to the user's manager using the Azure portal.
 
- 1.  Sign in to Azure portal
+ 1.  Sign in to Azure portal.
  2.  On the right, select **Azure Active Directory**.
  3.  Select **Identity Governance**.
  4.  Select **Lifecycle workflows (Preview)**.
@@ -69,23 +67,23 @@ Use the following steps to create a pre-hire workflow that will generate a TAP a
  6. From the templates, select **select** under **Onboard pre-hire employee**.
   :::image type="content" source="media/tutorial-lifecycle-workflows/select-template.png" alt-text="Screenshot of selecting workflow template." lightbox="media/tutorial-lifecycle-workflows/select-template.png":::
 
- 7.  Next, you will configure the basic information about the workflow.  This information includes when the workflow will trigger, known as **Days from event**.  So in this case, the workflow will trigger two days before the employee's hire date.  On the onboard pre-hire employee screen, add the following settings and then select **Next: Configure Scope**.
+ 7.  Next, you'll configure the basic information about the workflow.  This information includes when the workflow triggers, known as **Days from event**.  So in this case, the workflow triggers two days before the employee's hire date.  On the onboard prehire employee screen, add the following settings and then select **Next: Configure Scope**.
 
      :::image type="content" source="media/tutorial-lifecycle-workflows/configure-scope.png" alt-text="Screenshot of selecting a configuration scope." lightbox="media/tutorial-lifecycle-workflows/configure-scope.png":::
 
-   8.  Next, you will configure the scope. The scope determines which users this workflow will run against.  In this case, it will be on all users in the Sales department.  On the configure scope screen, under **Rule** add the following settings and then select **Next: Review tasks**. For a full list of supported user properties, see: [Supported user properties and query parameters](/graph/api/resources/identitygovernance-rulebasedsubjectset?view=graph-rest-beta&preserve-view=true#supported-user-properties-and-query-parameters)
+   8.  Next, you'll configure the scope. The scope determines which users this workflow runs against.  In this case, it is on all users in the Sales department.  On the configure scope screen, under **Rule** add the following settings and then select **Next: Review tasks**. For a full list of supported user properties, see [Supported user properties and query parameters](/graph/api/resources/identitygovernance-rulebasedsubjectset?view=graph-rest-beta&preserve-view=true#supported-user-properties-and-query-parameters).
 
        :::image type="content" source="media/tutorial-lifecycle-workflows/review-tasks.png" alt-text="Screenshot of selecting review tasks." lightbox="media/tutorial-lifecycle-workflows/review-tasks.png":::
 
-   9. On the following page, you may inspect the task if desired but no additional configuration is needed. Select **Next: Review + Create** when you are finished.
+   9. On the following page, you may inspect the task if desired but no additional configuration is needed. Select **Next: Review + Create** when you're finished.
    :::image type="content" source="media/tutorial-lifecycle-workflows/onboard-review-create.png" alt-text="Screenshot of reviewing an on-board workflow." lightbox="media/tutorial-lifecycle-workflows/onboard-review-create.png":::
 
    10.  On the review blade, verify the information is correct and select **Create**.
    :::image type="content" source="media/tutorial-lifecycle-workflows/onboard-create.png" alt-text="Screenshot of creating an onboard workflow." lightbox="media/tutorial-lifecycle-workflows/onboard-create.png":::
 
 
 ## Run the workflow 
-Now that the workflow is created, it will automatically run the workflow every 3 hours. Lifecycle workflows will check every 3 hours for users in the associated execution condition and execute the configured tasks for those users.  However, for the tutorial, we would like to run it immediately. To run a workflow immediately, we can use the on-demand feature.
+Now that the workflow is created, it will automatically run the workflow every 3 hours. Lifecycle workflows check every 3 hours for users in the associated execution condition and execute the configured tasks for those users.  However, for the tutorial, we would like to run it immediately. To run a workflow immediately, we can use the on-demand feature.
 
 >[!NOTE]
 >Be aware that you currently cannot run a workflow on-demand if it is set to disabled.  You need to set the workflow to enabled to use the on-demand feature.
@@ -101,12 +99,12 @@ To run a workflow on-demand, for users using the Azure portal, do the following
 
 ## Check tasks and workflow status
 
-At any time, you may monitor the status of the workflows and the tasks. As a reminder, there are three different data pivots, users runs, and tasks which are currently available in public preview. You may learn more in the how-to guide [Check the status of a workflow (preview)](check-status-workflow.md). In the course of this tutorial, we will look at the status using the user focused reports.
+At any time, you may monitor the status of the workflows and the tasks. As a reminder, there are three different data pivots, users runs, and tasks that are currently available in public preview. You may learn more in the how-to guide [Check the status of a workflow (preview)](check-status-workflow.md). In the course of this tutorial, we'll look at the status using the user focused reports.
 
  1. To begin, select the **Workflow history (Preview)** tab on the left to view the user summary and associated workflow tasks and statuses.  
  :::image type="content" source="media/tutorial-lifecycle-workflows/workflow-history.png" alt-text="Screenshot of workflow History status." lightbox="media/tutorial-lifecycle-workflows/workflow-history.png":::
 
-1. Once the **Workflow history (Preview)** tab has been selected, you will land on the workflow history page as shown.
+1. Once the **Workflow history (Preview)** tab has been selected, you'll land on the workflow history page as shown.
  :::image type="content" source="media/tutorial-lifecycle-workflows/user-summary.png" alt-text="Screenshot of workflow history overview" lightbox="media/tutorial-lifecycle-workflows/user-summary.png":::
 
 1. Next, you may select **Total tasks** for the user Jane Smith to view the total number of tasks created and their statuses. In this example, there are three total tasks assigned to the user Jane Smith.  
@@ -126,4 +124,4 @@ After running your workflow on-demand and checking that everything is working fi
 
 ## Next steps
 - [Tutorial: Preparing user accounts for Lifecycle workflows (preview)](tutorial-prepare-azure-ad-user-accounts.md)
-- [Automate employee onboarding tasks before their first day of work using Lifecycle Workflows APIs](/graph/tutorial-lifecycle-workflows-onboard-custom-workflow)
+- [Automate employee onboarding tasks before their first day of work using Lifecycle Workflows APIs](/graph/tutorial-lifecycle-workflows-onboard-custom-workflow)