diff --git a/windows/client-management/mdm/diagnose-provisioning-packages.md b/windows/client-management/mdm/diagnose-provisioning-packages.md
index 82753567f2..c71e35a930 100644
--- a/windows/client-management/mdm/diagnose-provisioning-packages.md
+++ b/windows/client-management/mdm/diagnose-provisioning-packages.md
@@ -15,13 +15,12 @@ ms.collection: highpri
 # Diagnose Provisioning Packages
 
 ## Unable to apply Power Settings
-When applying certain provisioning packages containing power settings ([Configure power settings | Microsoft Learn](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11)) they require elevated permissions which are not applied when applying PPKGs [after the initial setup](/windows/configuration/provisioning-packages/provisioning-apply-package#after-initial-setup). An error of STATUS_PRIVILEGE_NOT_HELD (HRESULT=0xc0000061) is given when applying these packages with the incorrect security context.
+When applying certain provisioning packages containing [power settings](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11) they require elevated permissions which are not applied when applying PPKGs [after the initial setup](/windows/configuration/provisioning-packages/provisioning-apply-package#after-initial-setup). An error of STATUS_PRIVILEGE_NOT_HELD (HRESULT=0xc0000061) is given when applying these packages with the incorrect security context.
 
-Simply placing the PPKG into %WINDIR%/Provisioning/Packages and rebooting the machine will apply the packages with the correct security context (NT Authority\SYSTEM - [LocalSystem Account - Win32 apps | Microsoft Learn](/windows/win32/services/localsystem-account)) as stated in the note in [Configure power settings | Microsoft Learn](/windows-hardware/customize/power-settings/configure-power-settings?view=windows-11)
+Simply placing the PPKG into %WINDIR%/Provisioning/Packages and rebooting the machine will apply the packages with the [correct security context](../windows/win32/services/localsystem-account)) as stated in [Configure power settings](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11)
 
 ## Unable to perform Bulk Enrollment in Azure AD
-Provisioning packages allow enrollment into Azure AD as seen in [(Bulk join a Windows device to Azure AD and Microsoft Endpoint Manager using a provisioning package - Microsoft Community Hub)](https://techcommunity.microsoft.com/t5/intune-customer-success/bulk-join-a-windows-device-to-azure-ad-and-microsoft-endpoint/ba-p/2381400). A few issues can occur:
-
+See [allow enrollment into Azure AD for provisioning packages](https://techcommunity.microsoft.com/t5/intune-customer-success/bulk-join-a-windows-device-to-azure-ad-and-microsoft-endpoint/ba-p/2381400).
 <!--
 
 TODO: @Harrison Chotzen 
@@ -29,7 +28,7 @@ TODO: @Harrison Chotzen
 -->
 
 ## Unable to apply a multivariant provisioning package
-If creating a multivariant package [(Create a provisioning package with multivariant settings (Windows 10/11) - Configure Windows | Microsoft Learn)](/windows/configuration/provisioning-packages/provisioning-multivariant). It may be difficult to diagnose why a certain target did not get applied. There may be conditions improperly authored which, when applied to the target device may not be evaluated as expected.
+If creating a [multivariant package](../windows/configuration/provisioning-packages/provisioning-multivariant). It may be difficult to diagnose why a certain target did not get applied. There may be conditions improperly authored which when applied to the target device may not be evaluated as expected.
 
 <!-- 
 
@@ -40,10 +39,10 @@ I think that now that the information is combined there is overlap and confusion
 Tooling has been included to surface these conditions in the event a certain target did not get applied.
 
 ## Diagnosing general failures in provisioning
-To help diagnose common problems, you can run the mdmdiagnosticstool and capture multivariant condition values, see [Diagnose MDM failures in Windows 10 - Windows Client Management | Microsoft Learn.](/windows/client-management/diagnose-mdm-failures-in-windows-10)
+To help diagnose common problems, you can run the [mdmdiagnosticstool](../windows/client-management/diagnose-mdm-failures-in-windows-10) and capture multivariant condition values.
 
 ## Diagnosing multivariant problems
-When applying multivariant packages it may be difficult to see why a target was not applied. The MdmDiagnosticsTool [(Diagnose MDM failures in Windows 10 - Windows Client Management | Microsoft Learn)](/windows/client-management/diagnose-mdm-failures-in-windows-10) includes the multivariant condition values on the target system. 
+When applying multivariant packages it may be difficult to see why a target was not applied. The [MdmDiagnosticsTool](../windows/client-management/diagnose-mdm-failures-in-windows-10) includes the multivariant condition values on the target system. 
 <!-- 
 
 this also needs to be fixed