resolving Absolute links

Author: whhender

articles/purview/concept-best-practices-migration.md

@@ -89,7 +89,7 @@ This section provides high level guidance on required tasks to copy assets, glos
 
 ### Create the new account
 You will need to create a new Azure Purview account by following below instruction:
-* [Quickstart: Create an Azure Purview account in the Azure portal](https://docs.microsoft.com/azure/purview/create-catalog-portal)
+* [Quickstart: Create an Azure Purview account in the Azure portal](create-catalog-portal.md)
 
 It’s crucial to plan ahead on configuration items that you cannot change later:
 * Account name
@@ -98,7 +98,7 @@ It’s crucial to plan ahead on configuration items that you cannot change later
 * Manage resource group name
 
 ### Migrate configuration items
-Below steps are referring to [Azure Purview API documentation](https://docs.microsoft.com/rest/api/purview) so that you can programmatically stand up the backup account quickly:
+Below steps are referring to [Azure Purview API documentation](/rest/api/purview/) so that you can programmatically stand up the backup account quickly:
 
 |Task|Description|
 |-------------|-----------------|
@@ -109,7 +109,7 @@ Below steps are referring to [Azure Purview API documentation](https://docs.micr
 |**Resource set rule**|Create and maintain resource set rule. You can call the [Get resource set rule API](/rest/api/purview/accountdataplane/resource-set-rules/get-resource-set-rule) to get the rule details|
 |**Data sources**|Call the [Get all data sources API](/rest/api/purview/scanningdataplane/scans/list-by-data-source) to list data sources with details. You also have to get the triggers by calling [Get trigger API](/rest/api/purview/scanningdataplane/triggers/get-trigger). There is also [Create data sources API](/rest/api/purview/scanningdataplane/data-sources/create-or-update) if you need to re-create the sources in bulk in the new account.|
 |**Credentials**|Create and maintain credentials used while scanning. There is no API to extract credentials, so this must be redone in the new account.|
-|**Self-hosted integration runtime (SHIR)**|Get a list of SHIR and get updated keys from the new account then update the SHIRs. This must be done [manually inside the SHIRs' hosts](https://docs.microsoft.com/azure/purview/manage-integration-runtimes#create-a-self-hosted-integration-runtime)|
+|**Self-hosted integration runtime (SHIR)**|Get a list of SHIR and get updated keys from the new account then update the SHIRs. This must be done [manually inside the SHIRs' hosts](manage-integration-runtimes.md#create-a-self-hosted-integration-runtime).|
 |**ADF connections**|Currently an ADF can be connected to one Purview at a time. You must disconnect ADF from failed Purview account and reconnect it to the new account later.|
 
 
@@ -325,7 +325,7 @@ To complete the asset migration, you must remap the relationships. There are thr
 > Before migrating terms, you need to migrate the term templates. This step should be already covered in the custom `typedef` migration.
 
 #### Using Azure Purview Portal
-The quickest way to migrate glossary terms is to [export terms to a .csv file](https://review.docs.microsoft.com/azure/purview/how-to-create-import-export-glossary?branch=main). You can do this using the Purview Studio.
+The quickest way to migrate glossary terms is to [export terms to a .csv file](how-to-create-import-export-glossary.md). You can do this using the Purview Studio.
 
 #### Using Azure Purview API
 To automate glossary migration, you first need to get the glossary `guid` (`glossaryGuid`) via [List Glossaries API](/rest/api/purview/catalogdataplane/glossary/list-glossaries). The `glossaryGuid` is the top/root level glossary `guid`.

articles/purview/concept-best-practices-sensitivity-labels.md

@@ -31,7 +31,7 @@ It also abstracts the data itself, so you use labels to track the type of data,
 ### Label considerations
 
 - If you already have Microsoft 365 sensitivity labels in use in your environment, it is recommended that you continue to use your existing labels rather than making duplicate or more labels for Purview. This allows you to maximize the investment you have already made in the Microsoft 365 compliance space and ensures consistent labeling across your data estate.
-- If you have not yet created Microsoft 365 sensitivity labels, it is recommended that you review the documentation to [Get started with sensitivity labels](https://docs.microsoft.com/microsoft-365/compliance/get-started-with-sensitivity-labels?view=o365-worldwide). Creating a classification schema is a tenant-wide operation and should be discussed thoroughly before enabling it within your organization.
+- If you have not yet created Microsoft 365 sensitivity labels, it is recommended that you review the documentation to [Get started with sensitivity labels](/microsoft-365/compliance/get-started-with-sensitivity-labels). Creating a classification schema is a tenant-wide operation and should be discussed thoroughly before enabling it within your organization.
 
 ### Label recommendations
 
@@ -52,6 +52,6 @@ It also abstracts the data itself, so you use labels to track the type of data,
 
 ## Next steps
 
-- [Get started with sensitivity labels](https://docs.microsoft.com/microsoft-365/compliance/get-started-with-sensitivity-labels?view=o365-worldwide).
+- [Get started with sensitivity labels](/microsoft-365/compliance/get-started-with-sensitivity-labels).
 
-- [How to automatically apply sensitivity labels to your data in Azure Purview](https://docs.microsoft.com/azure/purview/how-to-automatically-label-your-content).
+- [How to automatically apply sensitivity labels to your data in Azure Purview](how-to-automatically-label-your-content.md).