minor updates

zeinab-mk · zeinab-mk · commit f03477e5bd5b · 2022-03-16T01:08:17.000-04:00
diff --git a/articles/purview/tutorial-azure-purview-checklist.md b/articles/purview/tutorial-azure-purview-checklist.md
@@ -16,7 +16,7 @@ This article lists prerequisites that help you get started quickly on Azure Purv
 
 |No.  |Prerequisite / Action  |Required Permission  |Additional guidance and recommendations  |
 |:---------|:---------|:---------|:---------|
-|1    | Azure Active Directory Tenant        |N/A         |An [Azure Active Directory tenant](../active-directory/fundamentals/active-directory-access-create-new-tenant.md) should be associated with your subscription. <ul><li>*Global Administrator* or *Information Protection Administrator* role is required, if you plan to [extend M365 Sensitivity Labels to Azure Purview for files and db columns](create-sensitivity-label.md)</li><li> *Global Administrator* or *Power BI Administrator* role is required, if you're planning to [scan Power BI tenants](register-scan-power-bi-tenant.md).</li></ul>         |
+|1    | Azure Active Directory Tenant        |N/A         |An [Azure Active Directory tenant](../active-directory/fundamentals/active-directory-access-create-new-tenant.md) should be associated with your subscription. <ul><li>*Global Administrator* or *Information Protection Administrator* role is required, if you plan to [extend Microsoft 365 Sensitivity Labels to Azure Purview for files and db columns](create-sensitivity-label.md)</li><li> *Global Administrator* or *Power BI Administrator* role is required, if you're planning to [scan Power BI tenants](register-scan-power-bi-tenant.md).</li></ul>         |
 |2     |An active Azure Subscription          |*Subscription Owner*         |An Azure subscription is needed to deploy Azure Purview and its managed resources. If you don't have an Azure subscription, create a [free subscription](https://azure.microsoft.com/free/) before you begin.          |
 |3     |Define whether you plan to deploy an Azure Purview with managed Event Hub      |  N/A |A managed Event Hub is created as part of Azure Purview account creation, see Azure Purview account creation. You can publish messages to the Event Hub kafka topic ATLAS_HOOK and Azure Purview will consume and process it. Azure Purview will notify entity changes to Event Hub kafka topic ATLAS_ENTITIES and user can consume and process it.This quickstart uses the new Azure.Messaging.EventHubs library.      |  
 |4     |Register the following resource providers: <ul><li>Microsoft.Storage</li><li>Microsoft.EventHub (optional)</li><li>Microsoft.Purview</li></ul>       |*Subscription Owner* or custom role to register Azure resource providers (_/register/action_)         | [Register required Azure Resource Providers](/azure-resource-manager/management/resource-providers-and-types.md) in the Azure Subscription that is designated for Azure Purview Account. Review [Azure resource provider operations](../role-based-access-control/resource-provider-operations.md).          |
@@ -47,11 +47,11 @@ This article lists prerequisites that help you get started quickly on Azure Purv
 |29     | Create a new connection to Azure Key Vault from Azure Purview Studio | *Data source admin*    | Use this step if you are planing to use any of the following authentication options to scan a data source in Azure Purview: <ul><li>Account key</li><li>Basic Authentication</li><li>Delegated Auth</li><li>SQL Authentication</li><li>Service Principal</li><li>Consumer Key</li></ul> 
 |30     |Deploy a private endpoint for Power BI tenant         |*Power BI Administrator* <br> *Network contributor*          |Use this step if you're planning to register a Power BI tenant as data source and your Azure Purview Purview account is set to **deny public access**. <br> For more information, see [How to configure private endpoints for accessing Power BI](/power-bi/enterprise/service-security-private-links).        |
 |31     |Connect Azure Data Factory to Azure Purview from Azure Data Factory Portal.  **Manage** -> **Azure Purview**. Select **Connect to a Purview account**. <br> Validate if Azure resource tag **catalogUri** exists in ADF Azure resource.         |Azure Data Factory Contributor / Data curator          |Use this step if you have **Azure Data Factory**.         |
-|32     |Verify if you have at least one **Microsoft 365 required license** in your Azure Active Directory tenant to use sensitivity labels in Azure Purview.         |Azure Active Directory *Global Reader*         |Perform this step if you are interested in extending **Sensitivity Labels from Microsoft 365 to Azure Purview** <br> For more information see, [Azure Purview labeling licensing requirements](sensitivity-labels-frequently-asked-questions.md).         |
-|33     |Consent "**Extend labeling to assets in Azure Purview**"         |Compliance Administrator <br> Azure Information Protection Administrator          |Use this step if you are interested in extending Sensitivity Labels from Microsoft 365 to Azure Purview. <br> Use this step if you are interested in extending **Sensitivity Labels** from M365 to Azure Purview         |
-|34     |Create new collections and assign roles in Azure Purview         |*Collection admin*         | [Create a collection and assign permissions in Azure Purview](/quickstart-create-collection.md)       |
+|32     |Verify if you have at least one **Microsoft 365 required license** in your Azure Active Directory tenant to use sensitivity labels in Azure Purview.         |Azure Active Directory *Global Reader*         |Perform this step if you're planning  in extending **Sensitivity Labels from Microsoft 365 to Azure Purview** <br>         |
+|33     |Consent "**Extend labeling to assets in Azure Purview**"         |Compliance Administrator <br> Azure Information Protection Administrator          |Use this step if you are interested in extending Sensitivity Labels from Microsoft 365 to Azure Purview. <br> Use this step if you are interested in extending **Sensitivity Labels** from Microsoft 365 to Azure Purview.         |
+|34     |Create new collections and assign roles in Azure Purview         |*Collection admin*         | [Create a collection and assign permissions in Azure Purview](/quickstart-create-collection.md).       |
 |36     |Register and scan Data Sources in Azure Purview          |*Data Source admin* <br> *Data Reader* or *Data Curator*         | For more information, see [supported data sources and file types](azure-purview-connector-overview.md)        |
-|35     |Grant access to data roles in the organization          |*Collection admin*          |Provide access to other admins to use Azure Purview: <ul><li> Data curator</li><li> Data reader </li><li> Collection admin  </li><li> Data source admin </li></ul>        |
+|35     |Grant access to data roles in the organization          |*Collection admin*          |Provide access to other teams to use Azure Purview: <ul><li> Data curator</li><li>Data reader</li><li>Collection admin</li><li>Data source admin</li><li>Policy Author</li><li>Workflow admin</li></ul> <br> For more information, see [Access control in Azure Purview](catalog-permissions.md).      |
 
 ## Next steps
 -  [Review Azure Purview deployment best practices](./deployment-best-practices.md)
