Merge pull request #219915 from OWinfreyATL/owinfreyATL-LCW-Licensing-Updates

LCW licensing updated text

Author: AnnaMHuff

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

@@ -21,7 +21,9 @@ Workflows can be created and customized for common scenarios using templates, or
 
 ## Prerequisites
 
-[!INCLUDE [Azure AD Premium P2 license](../../../includes/active-directory-p2-license.md)]
+- 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/customize-workflow-schedule.md

@@ -2,7 +2,7 @@
 title: 'Customize workflow schedule - Azure Active Directory'
 description: Describes how to customize the schedule of a Lifecycle Workflow.
 services: active-directory
-author: owinfrey
+author: owinfreyATL
 manager: amycolannino
 ms.service: active-directory
 ms.workload: identity

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

@@ -18,6 +18,11 @@ ms.collection: M365-identity-device-management
 
 You can remove workflows that are no longer needed. Deleting these workflows allows you to make sure your lifecycle strategy is up to date. When a workflow is deleted, it enters a soft delete state. During this period, it's still able to be viewed within the deleted workflows list, and can be restored if needed. 30 days after a workflow enters a soft delete state it will be permanently removed. If you don't wish to wait 30 days for a workflow to permanently delete you can always manually delete it yourself.
 
+## Prerequisites
+
+- 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/lifecycle-workflows-deployment.md

@@ -40,10 +40,10 @@ Planning your Lifecycle Workflow deployment is essential to make sure you achiev
 
 For more information on deployment plans, see [Azure AD deployment plans](../fundamentals/active-directory-deployment-plans.md)
 
-## Licenses
+## License requirements
 
 
-[!INCLUDE [Azure AD Premium P2 license](../../../includes/active-directory-p2-license.md)]
+[!INCLUDE [Azure AD Premium P2 license](../../../includes/lifecycle-workflows-license.md)]
 
 >[!Note]
 >Be aware that if your license expires, any workflows that you have created will stop working.
@@ -104,21 +104,24 @@ This section introduces Lifecycle Workflow concepts you should know before you p
 
 
 ## Prerequisites to deploying Lifecycle Workflows
-The following is important information about your organization and the technologies that need to be in place prior to deploying Lifecycle Workflows.  Ensure that you can answer yes to each of the items before attempting to deploy Lifecycle Workflows.
+
+The following information is important information about your organization and the technologies that need to be in place prior to deploying Lifecycle Workflows.  Ensure that you can answer yes to each of the items before attempting to deploy Lifecycle Workflows.
 
 |Item|Description|Documentation|
 |-----|-----|-----|
 |Inbound Provisioning|You have a process to create user accounts for employees in Azure AD such as HR inbound, SuccessFactors, or MIM.<br><br> Alternatively you have a process to create user accounts in Active Directory and those accounts are provisioned to Azure AD.|[Workday to Active Directory](../saas-apps/workday-inbound-tutorial.md)<br><br>[Workday to Azure AD](../saas-apps/workday-inbound-tutorial.md)<br><br>[SuccessFactors to Active Directory](../saas-apps/sap-successfactors-inbound-provisioning-tutorial.md)</br></br>[SuccessFactors to Azure AD](../saas-apps/sap-successfactors-inbound-provisioning-cloud-only-tutorial.md)<br><br>[Azure AD Connect](../hybrid/whatis-azure-ad-connect-v2.md)<br><br>[Azure AD Connect cloud sync](../cloud-sync/what-is-cloud-sync.md)|
-|Attribute synchronization|The accounts in Azure AD have the employeeHireDate and employeeLeaveDateTime attributes populated.  The values may be populated when the accounts are created from an HR system or synchronized from AD using Azure AD Connect or cloud sync. You have additional attributes, that will be 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 Azure AD have the employeeHireDate and employeeLeaveDateTime attributes populated.  The values may be populated when the accounts are created from an HR system or synchronized from AD using Azure AD Connect or cloud sync. You have additional attributes that will be 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](lifecycle-workflows-developer-reference.md) 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 prior to deploying them.
 
 ## Limitations and constraints
+
 The following table provides information that you need to be aware of as you create and deploy Lifecycle workflows.
 
 |Item|Description|
@@ -133,7 +136,7 @@ The following table provides information that you need to be aware of as you cre
 
 The following is additional information you should be aware of.
 
- -    You cannot enable the schedule for the Real-Time Leaver scenario.  This is by design.
+ -    You can't enable the schedule for the Real-Time Leaver scenario.  This is by design.
 
 
 

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

@@ -26,9 +26,15 @@ This off-boarding scenario will run a workflow on-demand and accomplish the foll
 
 You may learn more about running a workflow on-demand [here](on-demand-workflow.md).
 
+## Prerequisites
+
+- Azure AD Premium P2
+
+For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements)
+
 ##  Before you begin
 
-As part of the prerequisites for completing this tutorial, you will need an account that has group and Teams memberships and that can be deleted during the tutorial. 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).
+As part of the prerequisites for completing this tutorial, you'll need an account that has group and Teams memberships and that can be deleted during the tutorial. 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 leaver scenario can be broken down into the following:
 -	**Prerequisite:** Create a user account that represents an employee leaving your organization
@@ -50,10 +56,10 @@ Use the following steps to create a leaver on-demand workflow that will execute
  6. From the templates, select **Select** under **Real-time employee termination**.
    :::image type="content" source="media/tutorial-lifecycle-workflows/select-template.png" alt-text="Screenshot of selecting template leaver workflow." lightbox="media/tutorial-lifecycle-workflows/select-template.png":::
 
- 7. Next, you will configure the basic information about the workflow. Select **Next:Review tasks** when you are done with this step. 
+ 7. Next, you'll configure the basic information about the workflow. Select **Next:Review tasks** when you're done with this step. 
    :::image type="content" source="media/tutorial-lifecycle-workflows/real-time-leaver.png" alt-text="Screenshot of review template tasks." lightbox="media/tutorial-lifecycle-workflows/real-time-leaver.png":::
 
- 8. On the following page, you may inspect the tasks if desired but no additional configuration is needed. Select **Next: Select users** when you are finished.
+ 8. On the following page, you may inspect the tasks if desired but no additional configuration is needed. Select **Next: Select users** when you're finished.
    :::image type="content" source="media/tutorial-lifecycle-workflows/real-time-tasks.png" alt-text="Screenshot of template tasks." lightbox="media/tutorial-lifecycle-workflows/real-time-tasks.png":::
 
  9. For the user selection, select **Select users**. This allows you to select users for which the workflow will be executed immediately after creation. Regardless of the selection, you can run the workflow on-demand later at any time as needed.
@@ -62,10 +68,10 @@ Use the following steps to create a leaver on-demand workflow that will execute
  10. Next, select on **+Add users** to designate the users to be executed on this workflow.
    :::image type="content" source="media/tutorial-lifecycle-workflows/real-time-add-users.png" alt-text="Screenshot of real time leaver add users." lightbox="media/tutorial-lifecycle-workflows/real-time-add-users.png":::
 
- 11. A panel with the list of available users will pop-up on the right side of the screen. Select **Select** when you are done with your selection.
+ 11. A panel with the list of available users will pop up on the right side of the screen. Select **Select** when you're done with your selection.
    :::image type="content" source="media/tutorial-lifecycle-workflows/real-time-user-list.png" alt-text="Screenshot of real time leaver template selected users." lightbox="media/tutorial-lifecycle-workflows/real-time-user-list.png":::
 
- 12. Select **Next: Review and create** when you are satisfied with your selection.
+ 12. Select **Next: Review and create** when you're satisfied with your selection.
    :::image type="content" source="media/tutorial-lifecycle-workflows/real-time-review-users.png" alt-text="Screenshot of reviewing template users." lightbox="media/tutorial-lifecycle-workflows/real-time-review-users.png":::
 
  13. On the review blade, verify the information is correct and select **Create**.
@@ -87,12 +93,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-real-time.png" alt-text="Screenshot of real time history overview." lightbox="media/tutorial-lifecycle-workflows/workflow-history-real-time.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-real-time.png" alt-text="Screenshot of real time workflow history." lightbox="media/tutorial-lifecycle-workflows/user-summary-real-time.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.  

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

@@ -22,6 +22,12 @@ This pre-hire scenario will generate a temporary access pass for our new employe
 
 :::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)
+
 ##  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:

articles/active-directory/governance/tutorial-scheduled-leaver-portal.md

@@ -23,6 +23,12 @@ This post off-boarding scenario will run a scheduled workflow and accomplish the
 2. Remove user from all Teams
 3. Delete user account
 
+## Prerequisites
+
+- Azure AD Premium P2
+
+For more information, see: [License requirements](what-are-lifecycle-workflows.md#license-requirements)
+
 ##  Before you begin
 
 As part of the prerequisites for completing this tutorial, you will need an account that has licenses and Teams memberships that can be deleted during the tutorial. 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).

articles/active-directory/governance/understanding-lifecycle-workflows.md

@@ -18,10 +18,14 @@ The following reference document provides an overview of a workflow created usin
 
   [![Diagram of a lifecycle workflow](media/understanding-lifecycle-workflows/workflow-2.png)](media/understanding-lifecycle-workflows/workflow-2.png#lightbox)
 
-## Licenses and Permissions
+## License requirements 
 
 
-[!INCLUDE [Azure AD Premium P2 license](../../../includes/active-directory-p2-license.md)]
+[!INCLUDE [Azure AD Premium P2 license](../../../includes/lifecycle-workflows-license.md)]
+
+## Permissions
+
+The following permissions are required for Lifecycle Workflows:
 
 |Parameter  |Display String  |Description  |Admin Consent Required  |
 |---------|---------|---------|---------|

articles/active-directory/governance/what-are-lifecycle-workflows.md

@@ -68,7 +68,19 @@ You can use Lifecycle workflows to address any of the following conditions.
 - **Automate user account management**: Making sure users who are leaving have their access to resources revoked is a key part of the identity lifecycle process. Lifecycle Workflows allow you to automate the disabling and removal of user accounts.
 - **Integrate with Logic Apps**: Ability to apply logic apps to extend workflows for more complex scenarios using your existing Logic apps.
 
+## License requirements
 
+[!INCLUDE [Azure AD Premium P2 license](../../../includes/lifecycle-workflows-license.md)]
+
+
+### How many licenses must you have?
+
+To utilize the Lifecycle Workflows feature, you must have at least one Azure AD Premium P2 license in your tenant. With one license, you're able to:
+
+- Create, manage, and delete workflows for any, or all, users in your tenant up to the total limit of 50 workflows.
+- Trigger on-demand and scheduled workflow execution.
+- Manage and configure existing tasks to create workflows that are specific to your needs.
+- Create up to 100 custom task extensions to be used in your workflows.
 
 
 ## Next steps

includes/lifecycle-workflows-license.md

@@ -0,0 +1,9 @@
+---
+author: owinfreyATL
+ms.service: active-directory
+ms.topic: include
+ms.date: 11/30/2022
+ms.author: owinfrey
+---
+
+Using the Lifecycle Workflows feature requires an Azure AD Premium P2 license. For more information on this license, see [Compare generally available features of Azure AD](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).