Fix links

Simonx Xu · Simonx Xu · commit a6f62cb10178 · 2025-02-28T09:02:36.000+08:00
diff --git a/support/azure/synapse-analytics/dedicated-sql/query-execution-performance/dsql-perf-common-query-errors.md b/support/azure/synapse-analytics/dedicated-sql/query-execution-performance/dsql-perf-common-query-errors.md
@@ -57,4 +57,4 @@ Use the following guidance to troubleshoot common failures, errors, and exceptio
 
 - Query the DMV [sys.dm_pdw_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-pdw-errors-transact-sql) for errors
 - [Troubleshoot dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot)
-- [Troubleshoot a slow query on a dedicated SQL pool](/troubleshoot/azure/synapse-analytics/dedicated-sql/query-execution-performance/troubleshoot-dsql-perf-slow-query)
+- [Troubleshoot a slow query on a dedicated SQL pool](../../../../azure/synapse-analytics/dedicated-sql/query-execution-performance/troubleshoot-dsql-perf-slow-query.md)
diff --git a/support/azure/virtual-machines/windows/allocation-failure.md b/support/azure/virtual-machines/windows/allocation-failure.md
@@ -82,7 +82,7 @@ To work around this issue, use one of the following methods:
 
 - For a new VM deployment, if it can be part of a different availability set, create the VM in a different availability set (in the same region or zone). This new VM can then be added to the same virtual network.
 
-- Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your availability set, use [availability sets - List Available Sizes - REST API](/troubleshoot/azure/virtual-machines/windows/virtual-machines-availability-set-supportability).
+- Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your availability set, use [availability sets - List Available Sizes - REST API](virtual-machines-availability-set-supportability.md).
 
 - Stop (deallocate) all VMs in the same availability set, and then start all applicable VMs in a batch to allow the allocation from all available clusters, rather than just the cluster where the availability set is currently allocated.
   
@@ -110,7 +110,7 @@ To work around this issue, use one of the following methods:
 
 - Resize the VMs
 
-  Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your Availability Set, use [Availability Sets - List Available Sizes - REST API](/troubleshoot/azure/virtual-machines/windows/virtual-machines-availability-set-supportability).
+  Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your Availability Set, use [Availability Sets - List Available Sizes - REST API](virtual-machines-availability-set-supportability.md).
 
 - Change the region or zone
 
@@ -154,7 +154,7 @@ To work around this issue, use one of the following methods:
 
 ### Cause
 
-When the Azure Compute platform can't allocate a VM to meet the required constraints specified in the request, overconstrained allocation failures occur. These failures typically happen when specific requirements can’t be met within the available resources. They are often indicated by errors like `OverconstrainedZonalAllocationRequest` or `OverconstrainedAllocationRequest`.
+When the Azure Compute platform can't allocate a VM to meet the required constraints specified in the request, overconstrained allocation failures occur. These failures typically happen when specific requirements can't be met within the available resources. They are often indicated by errors like `OverconstrainedZonalAllocationRequest` or `OverconstrainedAllocationRequest`.
 
 These constraints usually (but not always) include the following items:
 
@@ -232,7 +232,7 @@ The servers in Azure datacenters are partitioned into clusters. Normally, an all
 
 ### Why allocation failures happen
 
-When an allocation has a large number of restrictions, there's a higher chance of failing to find free resources since the available resource pool is smaller. Furthermore, if your allocation request is restricted (for example, when using proximity placement groups but the type of resource you requested isn’t supported by the set of clusters and nearby ones), your request fails even if the cluster has free resources. The following Diagram 2 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don't have free resources. Diagram 3 illustrates the case where an allocation fails because the candidate clusters associated with the  proximity placement group don’t support the requested VM size, even though the clusters have free resources.
+When an allocation has a large number of restrictions, there's a higher chance of failing to find free resources since the available resource pool is smaller. Furthermore, if your allocation request is restricted (for example, when using proximity placement groups but the type of resource you requested isn't supported by the set of clusters and nearby ones), your request fails even if the cluster has free resources. The following Diagram 2 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don't have free resources. Diagram 3 illustrates the case where an allocation fails because the candidate clusters associated with the  proximity placement group don't support the requested VM size, even though the clusters have free resources.
 
 :::image type="content" source="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png" alt-text="Screenshot of Diagram 2 showing allocation failed with no free resource available and Diagram 3 showing allocation failed with size not supported." lightbox="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png":::
 
diff --git a/support/power-platform/dataverse/email-exchange-synchronization/emails-not-automatically-tracked-or-synchronized.md b/support/power-platform/dataverse/email-exchange-synchronization/emails-not-automatically-tracked-or-synchronized.md
@@ -36,11 +36,11 @@ To get troubleshooting information in the **Server-Side Synchronization Item Lev
 
 2. The **Sync Error** column contains information about why an item didn't synchronize. Selecting the link directs you to an article about the error, if available. For example:
 
-   - This screenshot shows a "Question about service" email that isn't automatically tracked due to an [IsvAborted](/troubleshoot/dynamics-365/sales/unknownincomingemailintegrationerror-2147220891) error that occurs during processing. This error indicates a failure within a plugin or workflow that needs to be addressed by the solution owner.
+   - This screenshot shows a "Question about service" email that isn't automatically tracked due to an [IsvAborted](unknownincomingemailintegrationerror-2147220891.md) error that occurs during processing. This error indicates a failure within a plugin or workflow that needs to be addressed by the solution owner.
 
      :::image type="content" source="media/emails-not-automatically-tracked-or-synchronized/question-about-service-email-example.png" alt-text="Screenshot that shows an IsvAborted error in a Question about service email.":::
 
-   - This screenshot shows a "Can we meet tomorrow?" email that isn't automatically tracked due to a [NoCorrelationMatch](/troubleshoot/dynamics-365/sales/email-fails-to-create-with-nocorrelationmatch-error) error. This error occurs because none of the resolved (known) Dataverse email recipients automatically accept the email based on their [personal option settings](/power-platform/admin/email-message-filtering-correlation).
+   - This screenshot shows a "Can we meet tomorrow?" email that isn't automatically tracked due to a [NoCorrelationMatch](email-fails-to-create-with-nocorrelationmatch-error.md) error. This error occurs because none of the resolved (known) Dataverse email recipients automatically accept the email based on their [personal option settings](/power-platform/admin/email-message-filtering-correlation).
 
      :::image type="content" source="media/emails-not-automatically-tracked-or-synchronized/can-we-meet-tomorrow-email-example.png" alt-text="Screenshot that shows a NoCorrelationMatch error in a Can we meet tomorrow email.":::
 
diff --git a/support/sql/releases/linux/release-history-2019.md b/support/sql/releases/linux/release-history-2019.md
@@ -66,7 +66,7 @@ The following table lists the release history for [!INCLUDE [sql-server-2019](..
 
 ## <a id="CU31"></a> CU 31 (February 2025)
 
-This is the Cumulative Update 31 (CU 31) release of [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 15.0.4420.2. For information about the fixes and improvements in this release, see the [Support article](/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate31).
+This is the Cumulative Update 31 (CU 31) release of [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 15.0.4420.2. For information about the fixes and improvements in this release, see the [Support article](../sqlserver-2019/cumulativeupdate31.md).
 
 > [!IMPORTANT]  
 > This is the final cumulative update for [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)].
diff --git a/support/windows-365/troubleshoot-windows-365-business.md b/support/windows-365/troubleshoot-windows-365-business.md
@@ -38,7 +38,7 @@ If the automatic enrollment of new Cloud PCs into the Microsoft Intune setting i
 
 | Error | Troubleshooting steps |
 | --- | --- |
-| To complete the setup, ask your administrator to update policy settings in Microsoft Intune to enroll this device. | Check the Intune settings you might have previously set on your tenant. For more information, see [Troubleshoot policies and profiles](/troubleshoot/mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune). Once the issue is fixed, either you or the user can reset the Cloud PC. |
+| To complete the setup, ask your administrator to update policy settings in Microsoft Intune to enroll this device. | Check the Intune settings you might have previously set on your tenant. For more information, see [Troubleshoot policies and profiles](../mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune.md). Once the issue is fixed, either you or the user can reset the Cloud PC. |
 | To complete the setup, ask your administrator to remove restrictions preventing Intune from allowing Windows enrollment.| You might have set up enrollment restrictions on your Intune tenant. For more information, see [Enrollment restrictions overview](/mem/intune/enrollment/enrollment-restrictions-set). Once the restrictions are removed, either you or the user can reset the Cloud PC. |
 | To complete the setup, ask your administrator to correct the configuration of the Mobile Device Management discovery URL in Intune.| Confirm that the MDM discovery URL is the default for Intune. Follow steps 1-4 to set it in [Configure automatic MDM enrollment](/mem/intune/enrollment/windows-enroll#configure-automatic-mdm-enrollment). Once the MDM discovery URL is set to the default, either you or the user can reset the Cloud PC. |
 
diff --git a/support/windows-365/windows-365-boot-known-issues.md b/support/windows-365/windows-365-boot-known-issues.md
@@ -159,7 +159,7 @@ If you configured your device for Windows 365 Boot using the [Windows 365 Boot G
 2. Search for the device configuration profile that contains "Windows 365 Boot Device Configuration Policy" in its name.
 3. Make sure that the "Cloud Desktop" configuration is configured with the **Windows 365 Boot Mode** setting set to **Enable Windows 365 Boot Desktop**.
 4. Select **Device assignment status** and make sure that the configuration policy was successfully applied to it.
-5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](/troubleshoot/mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune).
+5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](../mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune.md).
 
 If the problem persists, reinstall the physical device's operating system as explained in [Windows 365 Boot physical device requirements](/windows-365/enterprise/windows-365-boot-physical-device-requirements).
 
@@ -175,7 +175,7 @@ If you configured your device for Windows 365 Boot using the [Windows 365 Boot G
 2. Search for the device configuration profile that contains "Windows 365 Boot Device Configuration Policy" in its name.
 3. Make sure that the "Windows Logon" configuration is configured with the **Override Shell Program** setting set to **Apply Lightweight shell**.
 4. Select **Device assignment status** and make sure that the configuration policy was successfully applied to it.
-5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](/troubleshoot/mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune).
+5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](../mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune.md).
 
 If the problem persists, reinstall the physical device's operating system as explained in [Windows 365 Boot physical device requirements](/windows-365/enterprise/windows-365-boot-physical-device-requirements).
 
