Merge pull request #8062 from rwestMSFT/rw-0116-linux-release

Add note, and fix relative links

Author: aartig13

support/sql/releases/linux/release-history-2022.md

@@ -49,7 +49,10 @@ The following table lists the release history for [!INCLUDE [sql-server-2022](..
 
 ## <a id="CU17"></a> CU 17 (January 2025)
 
-This is the Cumulative Update 17 (CU 17) release of [!INCLUDE [sql-server-2022](../../includes/versions/sql-server-2022.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 16.0.4175.1. For information about the fixes and improvements in this release, see the [Support article](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate17).
+This is the Cumulative Update 17 (CU 17) release of [!INCLUDE [sql-server-2022](../../includes/versions/sql-server-2022.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 16.0.4175.1. For information about the fixes and improvements in this release, see the [Support article](../sqlserver-2022/cumulativeupdate17.md).
+
+> [!IMPORTANT]  
+> The Microsoft Entra managed identity feature for SQL Server on Azure VM isn't supported on Linux. For more information, see [Improvement: Microsoft Entra managed identity support for backup and restore database operations and for EKM with AKV in SQL Server on Azure VMs](../sqlserver-2022/microsoft-entra-managed-identity-support-for-backup-restore-database-ekm-akv.md).
 
 ### Package details
 

support/windows-365/troubleshoot-windows-365-business.md

@@ -57,7 +57,7 @@ If the automatic enrollment of new Cloud PCs into Microsoft Intune setting is tu
 
 | Error | Troubleshooting steps |
 | --- | --- |
-| To complete the setup, ask your administrator to resolve the following: - Update policy settings in Microsoft Intune to enroll this device. | Check the Intune settings you may have previously set on your tenant. For more, see [Troubleshoot policies and profiles](/troubleshoot/mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune). Once the issue has been fixed, either you or the user can reset the Cloud PC. |
+| To complete the setup, ask your administrator to resolve the following: - Update policy settings in Microsoft Intune to enroll this device. | Check the Intune settings you may have previously set on your tenant. For more, see [Troubleshoot policies and profiles](../mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune.md). Once the issue has been fixed, either you or the user can reset the Cloud PC. |
 | To complete the setup, ask your administrator to resolve the following: - Remove restrictions preventing Intune from allowing Windows enrollment.| You may 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 have been removed, either you or the user can reset the Cloud PC. |
 | To complete the setup, ask your administrator to resolve the following:- 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 has been set to the default, either you or the user can reset the Cloud PC. |
 

support/windows-365/windows-365-boot-known-issues.md

@@ -156,7 +156,7 @@ Windows 365 Boot is configured by using the [CloudDesktop CSP](/windows/client-m
 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).
 
@@ -170,7 +170,7 @@ Windows 365 Boot is configured through the [Windowslogon CSP](/windows/client-ma
 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).