Merge pull request #204586 from SnehaSudhirG/13July-UMC-brokenlinks

fixed broken links

Author: PRMerger6

articles/update-center/enable-machines.md

@@ -24,7 +24,7 @@ Register the periodic assessment and scheduled patching feature resource provide
 
 ## Prerequisites
 
-- Azure subscription - if you don't have one yet, you can [activate your MSDN subscriber benefits](/pricing/member-offers/msdn-benefits-details/) or sign up for a [free account](/free/?WT.mc_id=A261C142F).
+- Azure subscription - if you don't have one yet, you can [activate your MSDN subscriber benefits](https://azure.microsoft.com/pricing/member-offers/credit-for-visual-studio-subscribers/) or sign up for a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
 - Your account must be a member of the Azure [Owner](/azure/role-based-access-control/built-in-roles#owner) or [Contributor](/azure/role-based-access-control/built-in-roles#contributor) role in the subscription.
 

articles/update-center/overview.md

@@ -26,7 +26,7 @@ Before you enable your machines for update management center (preview), make sur
 > [!IMPORTANT]
 > Update management center (preview) can manage machines that are currently managed by Azure Automation [Update management](/azure/automation/update-management/overview) feature without interrupting your update management process. However, we don't recommend migrating from Automation Update Management since this preview gives you a chance to evaluate and provide feedback on features before it's generally available (GA). 
 >
-> While update management center is in **preview**, the [Supplemental Terms of Use for Microsoft Azure Previews](/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+> While update management center is in **preview**, the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 ## Key benefits
 

articles/update-center/troubleshoot.md

@@ -39,7 +39,7 @@ To review the logs related to all actions performed by the extension, check for
 
 ### Arc-enabled servers
 
-For Arc-enabled servers, review the [troubleshoot VM extensions](/azure-arc/servers/troubleshoot-vm-extensions) article for general troubleshooting steps.
+For Arc-enabled servers, review the [troubleshoot VM extensions](/azure/azure-arc/servers/troubleshoot-vm-extensions) article for general troubleshooting steps.
 
 To review the logs related to all actions performed by the extension, on Windows check for more details in `C:\ProgramData\GuestConfig\extension_Logs\Microsoft.SoftwareUpdateManagement\WindowsOsUpdateExtension`. It includes the following two log files of interest:
 
@@ -66,9 +66,6 @@ For  Windows service pack updates, we check for 20 minutes + 10 minutes for rebo
 
 More details can be found by reviewing the logs in the file path provided in the error message of the deployment run.
 
->[!NOTE]
-> For [Azure Arc-enabled servers](/azure/azure-arc/servers/overview), it can take up to five minutes to trigger a deployment job on the machine. If you have configured 30 minutes as the maximum duration, there is a high chance that the scan for missing updates will not occur. At least 25 minutes is required in the maintenance window to start the operation. 
-
 #### Resolution
 
 Setting a longer time range for maximum duration when triggering an [on-demand update deployment](deploy-updates.md) helps avoid the problem.