fix

Author: mohitp930

articles/azure-monitor/logs/data-security.md

@@ -95,7 +95,7 @@ Azure Monitor has an incident management process that all Microsoft services adh
 
 While rare, Microsoft notifies each customer within one day if significant loss of any customer data occurs. 
 
-For more information about how Microsoft responds to security incidents, see [Introduction to Azure security](/azure/security/fundamentals/overview).
+For more information about how Microsoft responds to security incidents, see [Introduction to Azure security](../../security/fundamentals/overview.md).
 
 ## Compliance
 The Azure Monitor software development and service team's information security and governance program supports its business requirements and adheres to laws and regulations as described at [Microsoft Azure Trust Center](https://azure.microsoft.com/support/trust-center/) and [Microsoft Trust Center Compliance](https://www.microsoft.com/en-us/trustcenter/compliance/default.aspx). How Azure Monitor Logs establishes security requirements, identifies security controls, manages, and monitors risks are also described there. Annually, we review policies, standards, procedures, and guidelines.

includes/deprecation-announcement-dms-classic-sql.md

@@ -7,4 +7,4 @@ ms.service: sql-database
 ms.topic: include
 ---
 > [!IMPORTANT]  
-> **[Azure Database Migration Service (classic) - SQL scenarios are on a deprecation path](https://azure.microsoft.com/updates/retirement-azure-database-migration-service-classic-sql-server-scenarios-deprecation/)**. Since **August 1, 2023**, you're no longer able to create new Database Migration Service (classic) resources for SQL Server scenarios from Azure portal. The service will be retired on **March 15, 2026** for all customers. For seamless migrations from multiple database sources to Azure SQL Targets, Microsoft recommend using the latest version of [Azure Database Migration Service](https://aka.ms/dmslatest), which is available as [Azure SQL Migration](/azure-data-studio/extensions/azure-sql-migration-extension) an extension in Azure Data Studio, or via [Azure Portal](https://aka.ms/dmsazureportal), or through [Azure PowerShell and Azure CLI](/azure/dms/migration-dms-powershell-cli). For more information, see [Retirement notice: Database Migration Service (classic)](https://aka.ms/dmsclassicportal).
+> **[Azure Database Migration Service (classic) - SQL scenarios are on a deprecation path](https://azure.microsoft.com/updates/retirement-azure-database-migration-service-classic-sql-server-scenarios-deprecation/)**. Since **August 1, 2023**, you're no longer able to create new Database Migration Service (classic) resources for SQL Server scenarios from Azure portal. The service will be retired on **March 15, 2026** for all customers. For seamless migrations from multiple database sources to Azure SQL Targets, Microsoft recommend using the latest version of [Azure Database Migration Service](https://aka.ms/dmslatest), which is available as [Azure SQL Migration](/azure-data-studio/extensions/azure-sql-migration-extension) an extension in Azure Data Studio, or via [Azure Portal](https://aka.ms/dmsazureportal), or through [Azure PowerShell and Azure CLI](../../dms/migration-dms-powershell-cli.md). For more information, see [Retirement notice: Database Migration Service (classic)](https://aka.ms/dmsclassicportal).