Merge pull request #292306 from GitHubber17/347131-aa

Bulk - Global effort to fix validation issues

Author: Jill Grant

articles/automation/automation-subscription-limits-faq.md

@@ -14,7 +14,7 @@ Azure Automation will soon revise its service and subscription limits to ensure
 
 ## Revised limits
 
-For more information on the current service and subscription limits, see [Automation limits](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#process-automation).
+For more information on the current service and subscription limits, see [Automation limits](../azure-resource-manager/management/azure-subscription-service-limits.md#process-automation).
 
 The following limits would be changed:
 - Maximum number of active Automation accounts in a subscription in a region. 

articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md

@@ -23,9 +23,9 @@ Using the Azure portal, you can migrate from Change Tracking & Inventory with LA
 - Migrate multiples VMs on LA version solution within a particular Automation Account.
 
 > [!NOTE]
-> File Integrity Monitoring (FIM) using [Microsoft Defender for Endpoint (MDE)](https://learn.microsoft.com/azure/defender-for-cloud/file-integrity-monitoring-enable-defender-endpoint) is now currently available. Follow the guidance to migrate from:
-> - [FIM with Change Tracking and Inventory using AMA](https://learn.microsoft.com/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-ama).
-> - [FIM with Change Tracking and Inventory using MMA](https://learn.microsoft.com/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-mma).
+> File Integrity Monitoring (FIM) using [Microsoft Defender for Endpoint (MDE)](/azure/defender-for-cloud/file-integrity-monitoring-enable-defender-endpoint) is now currently available. Follow the guidance to migrate from:
+> - [FIM with Change Tracking and Inventory using AMA](/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-ama).
+> - [FIM with Change Tracking and Inventory using MMA](/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-mma).
 
 ## Onboarding to Change tracking and inventory using Azure Monitoring Agent
 

articles/automation/change-tracking/overview-monitoring-agent.md

@@ -17,9 +17,9 @@ ms.service: azure-automation
 This article explains on the latest version of change tracking support using Azure Monitoring Agent as a singular agent for data collection. 
 
 > [!NOTE]
-> File Integrity Monitoring (FIM) using [Microsoft Defender for Endpoint (MDE)](https://learn.microsoft.com/azure/defender-for-cloud/file-integrity-monitoring-enable-defender-endpoint) is now currently available. If you have FIM configured with either AMA or LA, follow the guidance to migrate from:
-> - [FIM with Change Tracking and Inventory using AMA](https://learn.microsoft.com/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-ama).
-> - [FIM with Change Tracking and Inventory using MMA](https://learn.microsoft.com/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-mma).
+> File Integrity Monitoring (FIM) using [Microsoft Defender for Endpoint (MDE)](/azure/defender-for-cloud/file-integrity-monitoring-enable-defender-endpoint) is now currently available. If you have FIM configured with either AMA or LA, follow the guidance to migrate from:
+> - [FIM with Change Tracking and Inventory using AMA](/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-ama).
+> - [FIM with Change Tracking and Inventory using MMA](/azure/defender-for-cloud/migrate-file-integrity-monitoring#migrate-from-fim-over-mma).
 
 ## What is Change Tracking & Inventory
 

articles/update-manager/manage-hot-patching-arc-machines.md

@@ -12,7 +12,7 @@ ms.author: sudhirsneha
 
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
 
-Azure Update Manager enables you to install hotpatches (preview) on Windows Server Azure Editions and Arc-enabled machines. For more information, see [Hotpatch for virtual machines](https://learn.microsoft.com/windows-server/get-started/hotpatch). 
+Azure Update Manager enables you to install hotpatches (preview) on Windows Server Azure Editions and Arc-enabled machines. For more information, see [Hotpatch for virtual machines](/windows-server/get-started/hotpatch).
 
 This article explains how to install hotpatches (preview) on compatible Arc-enabled machines. For hotpatches (preview) being non-intrusive on availability, you can create faster schedules and update your services immediately after release, with less planning to maintain reliability of your machines at-scale.  
 

articles/update-manager/migration-overview.md

@@ -20,7 +20,7 @@ Azure Update Manager provides a SaaS solution to manage and govern software upda
 > - On 31 August 2024, both Azure Automation Update Management and the Log Analytics agent it uses [have retired](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). If you are still using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. Follow the guidance in this document to move your machines and schedules from Automation Update Management to Azure Update Manager. For more information, see the [FAQs on retirement](https://aka.ms/aum-migration-faqs).   
 > - If you are still using Azure Automation Update Management Solution, we recommend that you don't remove the the Microsoft Monitoring Agent (MMA) agents from the machines before completing the migration to Azure Update Manager as the migration tools expect the agent to be installed on the machines to be migrated. Additionally, if you remove the MMA agent from the machine before moving to Azure Update Manager, it will break the Automation Update Management patching workflows for that machine.      
 
-Azure Update Manager has no dependency on either the Azure Monitor Agent(AMA) or MMA agents. as it relies on the [Microsoft Azure Windows VM Agent](https://learn.microsoft.com/azure/virtual-machines/extensions/agent-windows) or the [Microsoft Azure Linux VM Agent](https://learn.microsoft.com/azure/virtual-machines/extensions/agent-linux) for Azure VMs and the [Azure connected machine agent](https://learn.microsoft.com/azure/azure-arc/servers/agent-overview) for Arc-enabled servers. When you perform an update operation for the first time on a machine, an extension is pushed to the machine, and it interacts with the agents to assess missing updates and install updates.      
+Azure Update Manager has no dependency on either the Azure Monitor Agent(AMA) or MMA agents. as it relies on the [Microsoft Azure Windows VM Agent](/azure/virtual-machines/extensions/agent-windows) or the [Microsoft Azure Linux VM Agent](/azure/virtual-machines/extensions/agent-linux) for Azure VMs and the [Azure connected machine agent](/azure/azure-arc/servers/agent-overview) for Arc-enabled servers. When you perform an update operation for the first time on a machine, an extension is pushed to the machine, and it interacts with the agents to assess missing updates and install updates.
 
 We provide three methods to move from Automation Update Management to Azure Update Manager which are explained in detail in the links below:   
 - [Portal migration tool](migration-using-portal.md)