incorporated peer reviews

Author: SnehaSudhirG

articles/update-manager/cross-subscription-patching.md

@@ -2,7 +2,7 @@
 title: Cross subscription patching in Azure Update Manager
 description: Learn about the overview, benefits, and limitations of cross-subscription patching in Azure Update Manager. Centralize and streamline patch management across multiple Azure subscriptions.
 ms.service: azure-update-manager
-ms.date: 02/01/2025
+ms.date: 02/04/2025
 ms.topic: conceptual
 author: SnehaSudhirG
 ms.author: sudhirsneha
@@ -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 Management offers a straightforward and efficient solution for managing asset patching within a subscription. However, its capabilities extend far beyond that. With proper configuration, users can manage and apply patches across multiple Azure subscriptions from a centralized location. The capability is beneficial for organizations with resources distributed across various subscriptions, ensuring consistent and streamlined patch management.
+Azure Update Management offers a straightforward and efficient solution for managing asset patching within a subscription. However, its capabilities extend far beyond that. With proper configuration, you can manage and apply patches across multiple Azure subscriptions from a centralized location. The capability is beneficial for organizations with resources distributed across various subscriptions, ensuring consistent and streamlined patch management.
 
 ## Key benefits of Cross-subscription patching
 
@@ -25,23 +25,23 @@ Azure Update Management offers a straightforward and efficient solution for mana
 
 - **Azure Resource Manager (Arc)-connected hosts**: Non-Azure hosts connected to Azure through Arc, subject to [Arc prerequisites](https://learn.microsoft.com/azure/azure-arc/servers/prerequisites) and Azure Update Manager [supported regions](support-matrix.md#azure-arc-enabled-servers)
 
-- **Azure VM** - Native virtual machines created in Azure
+- **Azure VM** - Native virtual machines created in Azure.
 
 # [Supported OS type](#tab/sup-os)
 
 - **Windows**: Cross-subscription patching supports various versions of Windows Server and Windows operating systems. Ensure that your Windows devices are up-to-date and compatible with the patching process. For more information, see [support matrix for Arc-connected hosts](support-matrix-updates.md#azure-arc-enabled-servers)and [Azure VM for supported images](support-matrix-updates.md#supported-windows-os-images). 
 
-- **Linux**: Cross-subscription patching also supports multiple Linux distributions, including most mainstream distributions like Ubuntu, CentOS, and Red Hat Enterprise Linux (RHEL) etc. Make sure that your Linux devices meet the necessary requirements for patching. For more information, see[support matrix for Arc-connected hosts](support-matrix-updates.md#azure-arc-enabled-servers) and [Azure VM for supported images](support-matrix-updates.md#supported-linux-os-images). 
+- **Linux**: Cross-subscription patching also supports multiple Linux distributions, including most mainstream distributions like Ubuntu, CentOS, and Red Hat Enterprise Linux (RHEL) etc. Ensure that your Linux devices meet the necessary requirements for patching. For more information, see[support matrix for Arc-connected hosts](support-matrix-updates.md#azure-arc-enabled-servers) and [Azure VM for supported images](support-matrix-updates.md#supported-linux-os-images). 
 
 ---
 
 > [!NOTE]
-> If VMs running unsupported images are included in the schedule, the maintenance configuration (that is, patch job) scheduled fails.
+> If VMs running unsupported images are included in the schedule, the maintenance configuration (i.e., patch job) will fail.
 
 
 ## Limitations
 
-**Rate limits** - For managing a large number of assets through API/SPN (Service Principal Name), be mindful of rate limits and distribute the load among multiple Service Principals to avoid throttling issues.
+**Rate limits** - For managing a large number of assets through API/SPN (Service Principal Name), be mindful of rate limits and distribute the load among multiple Service principals to avoid throttling issues.
 
 
 ## Next steps

articles/update-manager/enable-cross-subscription-patching.md

@@ -4,28 +4,28 @@ description: Learn how to enable cross-subscription patching in Azure Update Man
 ms.service: azure-update-manager
 author: SnehaSudhirG
 ms.author: sudhirsneha
-ms.date: 08/22/2024
+ms.date: 02/04/2025
 ms.topic: how-to
 ---
 
 # Enable cross subscription patching in Azure Update Manager
 
 **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.
 
-This article describes how to enable cross-subscription patching either through Azure CLI or portal.
+This article describes how to enable cross-subscription patching either through Azure CLI or Azure portal.
 
 ## Enable resource providers in subscription
 
-1. Register the necessary resource providers to your subscription either through Azure CLI or manually via the Azure portal
+1. Register the necessary resource providers to your subscription either through Azure CLI or manually via the Azure portal.
 
-    # [Using Azure CLI](#tab/az-cli)
+    # [Azure CLI](#tab/az-cli)
 
-    Open your Azure CLI and enter the following commands:
+    Open your Azure CLI and run the following commands:
 
     az provider register--namespace "Microsoft.Insights"
     az provider register--namespace "Microsoft.Maintenance"
 
-    # [Using Azure portal](#tab/az-portal)
+    # [Azure portal](#tab/az-portal)
 
     1. Sign in to the [Azure portal](https://portal.azure.com) and go to your subscription.
     1. Under **Settings**, select **Resource providers**.
@@ -40,11 +40,11 @@ This article describes how to enable cross-subscription patching either through
         - Scheduled patching contributor
         - Reader
    - These roles can be granted on the Resource Group or Subscription level if you have resources spread among multiple resource groups and want to include them all at once.
-   - If you have a smaller scope and plan to manage it with a dedicated admin or group, these two roles can be granted to a user or a security group (SG). If you're envisioning a larger scope with automation in place, grant these roles to the API and Service Principal Name (SPN) you use.
+   - If you have a smaller scope and plan to manage it with a dedicated admin or group, these two roles can be granted to a user or a security group (SG). If you are envisioning a larger scope with automation in place, ensure to grant these roles to the API and Service Principal Name (SPN) you use.
 
-3. Scheduling
+3. Scheduling using maintenance configurations
 
-   There are two methods for schedule patching.
+  To create maintenance configurations in Azure Update Manager, there are two ways you can set it up
 
    # [Using Azure portal](#tab/az-patch-portal)
       
@@ -58,6 +58,7 @@ This article describes how to enable cross-subscription patching either through
      - For schedule patching on VM or Arc assets, locate the assets by using the *resourceId* and *subscription* that they're attached to.
 
 ---
+
 ## Next steps
 
 * Overview on [cross-subscription patching](cross-subscription-patching.md)