Merge pull request #192865 from atikmapari/Broken-link-zeinam

Broken link fixed

Author: PRMerger12

articles/purview/tutorial-azure-purview-checklist.md

@@ -19,7 +19,7 @@ This article lists prerequisites that help you get started quickly on Azure Purv
 |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.      |  
-|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).          |
+|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/azure-resource-manager/management/resource-providers-and-types) in the Azure Subscription that is designated for Azure Purview Account. Review [Azure resource provider operations](../role-based-access-control/resource-provider-operations.md).          |
 |5     |Update Azure Policy to allow deployment of the following resources in your Azure subscription: <ul><li>Azure Purview</li><li>Azure Storage</li><li>Azure Event Hub (optional)</li></ul>            |*Subscription Owner*          |Use this step if an existing Azure Policy prevents deploying such Azure resources. If a blocking policy exists and needs to remain in place, please follow our [Azure Purview exception tag guide](create-azure-purview-portal-faq.md) and follow the steps to create an exception for Azure Purview accounts.          |
 |6     | Define your network security requirements.     | Network and Security architects.         |<ul><li> Review [Azure Purview network architecture and best practices](concept-best-practices-network.md) to define what scenario is more relevant to your network requirements. </li><li>If private network is needed, use [Azure Purview Managed IR](catalog-managed-vnet.md) to scan Azure data sources when possible to reduce complexity and administrative overhead. </li></ul>  |
 |7     |An Azure Virtual Network and Subnet(s) for Azure Purview private endpoints.         | *Network Contributor* to create or update Azure VNet.         |Use this step if you're planning to deploy [private endpoint connectivity with Azure Purview](catalog-private-link.md):  <ul><li>Private endpoints for **Ingestion**.</li><li>Private endpoint for Azure Purview **Account**.</li><li>Private endpoint for Azure Purview **Portal**.</li></ul> <br> Deploy [Azure Virtual Network](../virtual-network/quick-create-portal.md) if you need one.      |
@@ -49,7 +49,7 @@ This article lists prerequisites that help you get started quickly on Azure Purv
 |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're planning in extending **Sensitivity Labels from Microsoft 365 to Azure Purview** <br>  For more information, see [licensing requirements to use sensitivity labels on files and database columns in Azure Purview](sensitivity-labels-frequently-asked-questions.yml)       |
 |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).       |
+|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 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).      |