created new article prerequisites and addressed warnings

SnehaSudhirG · SnehaSudhirG · commit 868e1fea16a8 · 2024-07-17T08:38:24.000+05:30
diff --git a/articles/update-manager/overview.md b/articles/update-manager/overview.md
@@ -12,9 +12,10 @@ ms.topic: overview
 # About Azure Update Manager
 
 > [!Important]
-> On 31 August 2024, both Azure Automation Update Management and the Log Analytics agent it uses will be retired. Therefor, if you are using the Azure Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. Follow the [guidance](guidance-migration-automation-update-management-azure-update-manager.md) to move your machines and schedules from Automation Update Management to Azure Update Manager.
+> On 31 August 2024, both Azure Automation Update Management and the Log Analytics agent it uses [will be retired](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Therefore, if you are using the Azure Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. Follow the [guidance](guidance-migration-automation-update-management-azure-update-manager.md#migration-scripts) to move your machines and schedules from Automation Update Management to Azure Update Manager.
+
+For more information, see the [FAQs on retirement](update-manager-faq.md#impact-of-log-analytics-agent-retirement). You can [sign up](https://developer.microsoft.com/reactor/?search=Azure+Update+Manager&page=1) for monthly live sessions on migration including Q&A sessions.
 
-For more information, see the [FAQs on retirement](update-manager-faq.md). You can sign up for monthly live sessions on migration including Q&A sessions.
 
 Update Manager is a unified service to help manage and govern updates for all your machines. You can monitor Windows and Linux update compliance across your machines in Azure and on-premises/on other cloud platforms (connected by [Azure Arc](https://learn.microsoft.com/azure/azure-arc/)) from a single pane of management. You can also use Update Manager to make real-time updates or schedule them within a defined maintenance window. 
 
@@ -26,7 +27,7 @@ You can use Update Manager in Azure to:
     - [Customer-defined maintenance schedules](https://aka.ms/umc-scheduled-patching) for both Azure and Arc-connected machines.
     - [Automatic virtual machine (VM) guest patching](../virtual-machines/automatic-vm-guest-patching.md) and [hot patching](https://learn.microsoft.com/azure/automanage/automanage-hotpatch) for Azure VMs.
 - Build custom reporting dashboards for reporting update status and [configure alerts](https://aka.ms/aum-alerts) on certain conditions.
-- Oversee update compliance for your entire fleet of machines in Azure and on-premises/in other cloud environments (connected by [Azure Arc](../azure-arc/includes/azure-arc.md)) through a single pane. The different types of machines that can be managed are:
+- Oversee update compliance for your entire fleet of machines in Azure and on-premises/in other cloud environments connected by [Azure Arc](../azure-arc/includes/azure-arc.md) through a single pane. The different types of machines that can be managed are:
     - [Hybrid machines](https://learn.microsoft.com/azure/azure-arc/servers/)
     - [VMWare machines](https://learn.microsoft.com/azure/azure-arc/vmware-vsphere/)
     - [SCVMM machines](https://learn.microsoft.com/azure/azure-arc/system-center-virtual-machine-manager/)
@@ -56,6 +57,7 @@ Update Manager offers many new features and provides enhanced and native functio
 
 ## Next steps
 
+- [Prerequisites of Update Manager](prerequisites.md)
 - [View updates for a single machine](view-updates.md).
 - [Deploy updates now (on-demand) for a single machine](deploy-updates.md).
 - [Enable periodic assessment at scale using policy](https://aka.ms/aum-policy-support).
diff --git a/articles/update-manager/prerequisites.md b/articles/update-manager/prerequisites.md
@@ -0,0 +1,51 @@
+---
+title: Prerequisites for Azure Update Manager
+description: This article explains the prerequisites for Azure Update Manager, VM extensions and network planning.
+ms.service: azure-update-manager
+ms.custom: linux-related-content
+author: SnehaSudhirG
+ms.author: sudhirsneha
+ms.date: 07/14/2024
+ms.topic: overview
+---
+
+# Prerequisites for Azure Update Manager
+
+## Prerequisites
+
+Azure Update Manager is an out of the box, zero onboarding service. Following are the  only a few things that you must consider before starting to use the service. 
+
+### Arc-enabled servers
+Arc-enabled servers must be connected to Azure Arc to use Azure Update Manager. For more information, see [how to enable Arc on non-Azure machines](https://aka.ms/onboard-to-arc-aum-migration).
+
+### Support matrix
+Refer [support matrix](support-matrix.md) to find out about updates and the update sources, VM images and Azure regions that are supported for Azure Update Manager.
+
+### Roles and permissions
+
+To manage machines from Azure Update Manager, see roles and permissions.
+
+### VM extensions
+
+Azure VM extensions and Azure Arc-enabled VM extensions are required to run on the Azure and Arc-enabled machine respectively for Azure Update Manager to work. But separate installation is not required as the extensions are automatically pushed on the VM the first time you trigger any Update Manager operation on the VM. For more information, see the [VM extensions] that are pushed on the machines
+
+### Network planning
+
+To prepare your network to support Update Manager, you might need to configure some infrastructure components. For more information, see the [network requirements for Arc-enabled servers](../azure-arc/servers/includes/network-requirements.md).
+
+For Windows machines, you must allow traffic to any endpoints required by the Windows Update agent. You can find an updated list of required endpoints in [issues related to HTTP Proxy](https://learn.microsoft.com/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting?toc=%2Fwindows%2Fdeployment%2Ftoc.json&bc=%2Fwindows%2Fdeployment%2Fbreadcrumb%2Ftoc.json#issues-related-to-httpproxy). If you have a local [WSUS](https://learn.microsoft.com/windows-server/administration/windows-server-update-services/plan/plan-your-wsus-deployment) deployment, you must allow traffic to the server specified in your [WSUS key](https://learn.microsoft.com/en-us/windows/deployment/update/waas-wu-settings#configuring-automatic-updates-by-editing-the-registry)
+
+For Red Hat Linux machines, see [IPs for the RHUI content delivery servers](../virtual-machines/workloads/redhat/redhat-rhui.md#the-ips-for-the-rhui-content-delivery-servers)for required endpoints. For other Linux distributions, see your provider documentation.
+
+### Configure Windows Update client
+
+Azure Update Manager relies on the [Windows Update client](https://learn.microsoft.com/windows/deployment/update/windows-update-overview) to download and install Windows updates. There are specific settings that are used by the Windows Update client when connecting to Windows Server Update Services (WSUS) or Windows Update. For more information, see [configure Windows Update client](configure-wu-agent.md).
+
+## Next steps
+
+- [View updates for a single machine](view-updates.md).
+- [Deploy updates now (on-demand) for a single machine](deploy-updates.md).
+- [Enable periodic assessment at scale using policy](https://aka.ms/aum-policy-support).
+- [Schedule recurring updates](scheduled-patching.md)
+- [Manage update settings via the portal](manage-update-settings.md).
+- [Manage multiple machines by using Update Manager](manage-multiple-machines.md).
diff --git a/articles/update-manager/prerequsites.md b/articles/update-manager/prerequsites.md
diff --git a/articles/update-manager/scheduled-patching.md b/articles/update-manager/scheduled-patching.md
@@ -23,11 +23,11 @@ Update Manager uses a maintenance control schedule instead of creating its own s
 
 ## Prerequisites for scheduled patching
 
-1. See [Prerequisites for Update Manager](./overview.md#prerequisites).
+1. See [Prerequisites for Update Manager](prerequisites.md).
 1. Patch orchestration of the Azure machines should be set to **Customer Managed Schedules**. For more information, see [Enable schedule patching on existing VMs](prerequsite-for-schedule-patching.md#enable-schedule-patching-on-azure-vms). For Azure Arc-enabled machines, it isn't a requirement.
 
 	> [!NOTE]
-	> If you set the patch mode to **Azure orchestrated** (`AutomaticByPlatform`) but do not enable the **BypassPlatformSafetyChecksOnUserSchedule** flag and do not attach a maintenance configuration to an Azure machine, it's treated as an [automatic guest patching](../virtual-machines/automatic-vm-guest-patching.md)-enabled machine. The Azure platform automatically installs updates according to its own schedule. [Learn more](./overview.md#prerequisites).
+	> If you set the patch mode to **Azure orchestrated** (`AutomaticByPlatform`) but do not enable the **BypassPlatformSafetyChecksOnUserSchedule** flag and do not attach a maintenance configuration to an Azure machine, it's treated as an [automatic guest patching](../virtual-machines/automatic-vm-guest-patching.md)-enabled machine. The Azure platform automatically installs updates according to its own schedule. [Learn more](prerequisites.md).
 
 ## Schedule patching in an availability set
 
diff --git a/articles/update-manager/toc.yml b/articles/update-manager/toc.yml
@@ -5,6 +5,10 @@ items:
   items:
   - name: About Azure Update Manager
     href: overview.md
+- name: Getting started
+  items:
+  - name: Prerequisites
+    href: prerequisites.md
   - name: Support matrix
     href: support-matrix.md
   - name: What's New 
diff --git a/articles/update-manager/troubleshoot.md b/articles/update-manager/troubleshoot.md
@@ -165,7 +165,7 @@ If you see an `HRESULT` error code, double-click the exception displayed in red
 |Exception  |Resolution or action  |
 |---------|---------|
 |`Exception from HRESULT: 0x……C`     | Search the relevant error code in the [Windows Update error code list](https://support.microsoft.com/help/938205/windows-update-error-code-list) to find more information about the cause of the exception.        |
-|`0x8024402C`</br>`0x8024401C`</br>`0x8024402F`      | Indicates network connectivity problems. Make sure your machine has network connectivity to Update Management. For a list of required ports and addresses, see the [Network planning](overview.md#network-planning) section.        |
+|`0x8024402C`</br>`0x8024401C`</br>`0x8024402F`      | Indicates network connectivity problems. Make sure your machine has network connectivity to Update Management. For a list of required ports and addresses, see the [Network planning](prerequisites.md#network-planning) section.        |
 |`0x8024001E`| The update operation didn't finish because the service or system was shutting down.|
 |`0x8024002E`| Windows Update service is disabled.|
 |`0x8024402C`     | If you're using a WSUS server, make sure the registry values for `WUServer` and `WUStatusServer` under the `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate` registry key specify the correct WSUS server.        |
