Merge pull request #303420 from jobingeorge-microsoft/main

[GA] Resource Health for AVS

Author: ttorble

articles/azure-vmware/architecture-identity.md

@@ -230,7 +230,7 @@ Now that you've covered Azure VMware Solution access and identity concepts, you
 
 - [Details of each privilege](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/defined-privileges.html)
 
-- [How Azure VMware Solution monitors and repairs private clouds](azure-vmware-solution-host-remediation.md#host-monitoring-and-remediation)
+- [How Azure VMware Solution monitors and repairs private clouds](azure-vmware-solution-private-cloud-maintenance-best-practices.md#host-monitoring-and-remediation)
 
 <!-- LINKS - external-->
 [VMware product documentation]: https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/defined-privileges.html

articles/azure-vmware/architecture-private-clouds.md

@@ -146,7 +146,7 @@ Azure VMware Solution continuously monitors the health of both the physical unde
 Now that you learned about Azure VMware Solution private cloud concepts, you might want to read:
 
 - [Azure VMware Solution networking and interconnectivity concepts](architecture-networking.md)
-- [Azure VMware Solution private cloud maintenance best practices](azure-vmware-solution-host-remediation.md)
+- [Azure VMware Solution private cloud maintenance best practices](azure-vmware-solution-private-cloud-maintenance-best-practices.md)
 - [Azure VMware Solution storage concepts](architecture-storage.md)
 - [Enable an Azure VMware Solution resource](deploy-azure-vmware-solution.md#register-the-microsoftavs-resource-provider)
 

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -10,7 +10,7 @@ ms.date: 7/29/2025
 
 # What's new in Azure VMware Solution
 
-Microsoft regularly applies important updates to the Azure VMware Solution for new features and software lifecycle management. You should receive a notification through Azure Service Health that includes the timeline of the maintenance. For more information, see [Host maintenance and lifecycle management](azure-vmware-solution-host-remediation.md#host-maintenance-and-lifecycle-management).
+Microsoft regularly applies important updates to the Azure VMware Solution for new features and software lifecycle management. You should receive a notification through Azure Service Health that includes the timeline of the maintenance. For more information, see [Host maintenance and lifecycle management](azure-vmware-solution-private-cloud-maintenance-best-practices.md#host-maintenance-and-lifecycle-management).
 
 ## July 2025
 

articles/azure-vmware/azure-vmware-solution-host-remediation.md renamed to articles/azure-vmware/azure-vmware-solution-private-cloud-maintenance-best-practices.md

@@ -59,13 +59,13 @@ The following actions are always recommended for ensuring host maintenance opera
 ## Alert Codes and Remediation Table
 |  Error Code         |        Error Details              |  Recommended Action     |
 |--------------------|---------------------------------|---------------------|
-|  EPC_CDROM_EMULATEMODE |  This error is encountered when CD-ROM on the Virtual Machine uses emulate mode, whose ISO image isn't accessible  | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79306) for the removal of any CDROM mounted on customer's workload Virtual Machines in emulate mode or detach ISO. It's recommended to use "Passthrough mode" for mounting any CD-ROM. |
-| EPC_DRSOVERRIDERULE | This error is encountered when there's a Virtual Machine with DRS Override set to "Disabled" mode. | VM shouldn't block vMotion while putting host into maintenance. Set Partially Automated DRS rules for the VM. Refer to [this document](/azure/azure-vmware/create-placement-policy#enable-restrict-vm-movement-for-specific-vms) to know more about VM placement policies. |
-|  EPC_SCSIDEVICE_SHARINGMODE  | This error is encountered when a Virtual Machine is configured to use a device that prevents a maintenance operation: A device that is a SCSI controller which is engaged in bus-sharing   | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79910) for the removal of any SCSI controller engaged in bus-sharing attached to VMs   |
-|  EPC_DATASTORE_INACCESSIBLE  |  This error is encountered when any external Datastore attached to AVS Private Cloud becomes inaccessible  | Follow [this article](/azure/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts?tabs=azure-portal#performance-best-practices) for the removal of any stale Datastore attached to cluster  |
-|  EPC_NWADAPTER_STALE | This error is encountered when connected Network interface on the Virtual Machine uses network adapter which becomes inaccessible | Follow [this KB article](https://knowledge.broadcom.com/external/article/318738/troubleshooting-the-migration-compatibil.html) for the removal of any stale N/W adapters attached to Virtual Machines   |
-| EPC_SERIAL_PORT | This error is encountered when a Virtual Machine’s serial port is connected to a device that can't be accessed on the destination host. | If you're using an image file (ISO, FLP, and so on), ensure that it's accessible from all ESXi servers on the cluster. Store the files on a data store that is shared between all ESXi servers that participate in vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
-| EPC_HARDWARE_DEVICE | This error is encountered when a Virtual Machine’s parallel Port/USB Device is connected to a device can't be accessed on the destination host. | If you're using an image file (ISO, FLP, and so on), ensure that it's accessible from all ESXi servers of the cluster. Store the files on a data store that is shared between all ESXi servers that participate in the vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
+| EPC_CDROM_EMULATEMODE        | This error is encountered when CD-ROM on the Virtual Machine uses emulate mode, whose ISO image isn't accessible  | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79306) for the removal of any CDROM mounted on customer's workload Virtual Machines in emulate mode or detach ISO. It's recommended to use "Passthrough mode" for mounting any CD-ROM. |
+| EPC_DRSOVERRIDERULE          | This error is encountered when there's a Virtual Machine with DRS Override set to "Disabled" mode. | VM shouldn't block vMotion while putting host into maintenance. Set Partially Automated DRS rules for the VM. Refer to [this document](/azure/azure-vmware/create-placement-policy#enable-restrict-vm-movement-for-specific-vms) to know more about VM placement policies. |
+| EPC_SCSIDEVICE_SHARINGMODE   | This error is encountered when a Virtual Machine is configured to use a device that prevents a maintenance operation: A device that is a SCSI controller, which is engaged in bus-sharing   | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79910) for the removal of any SCSI controller engaged in bus-sharing attached to VMs   |
+| EPC_DATASTORE_INACCESSIBLE   | This error is encountered when any external Datastore attached to AVS Private Cloud becomes inaccessible  | Follow [this article](/azure/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts?tabs=azure-portal#performance-best-practices) for the removal of any stale Datastore attached to cluster  |
+| EPC_NWADAPTER_STALE          | This error is encountered when connected Network interface on the Virtual Machine uses network adapter, which becomes inaccessible | Follow [this KB article](https://knowledge.broadcom.com/external/article/318738/troubleshooting-the-migration-compatibil.html) for the removal of any stale N/W adapters attached to Virtual Machines   |
+| EPC_SERIAL_PORT              | This error is encountered when a Virtual Machine’s serial port is connected to a device that can't be accessed on the destination host. | If you're using an image file (ISO, FLP, and so on), ensure that it's accessible from all ESXi servers on the cluster. Store the files on a data store that is shared between all ESXi servers that participate in vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
+| EPC_HARDWARE_DEVICE          | This error is encountered when a Virtual Machine’s parallel Port/USB Device is connected to a device can't be accessed on the destination host. | If you're using an image file (ISO, FLP, and so on), ensure that it's accessible from all ESXi servers of the cluster. Store the files on a data store that is shared between all ESXi servers that participate in the vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
 | EPC_INVALIDVM / EPC_ORPHANVM | This error is encountered when there's an orphaned or Invalid VM in the inventory | Ensure all your Virtual Machines are accessible to the vCenter. Refer to [this KB article](https://knowledge.broadcom.com/external/article/312831/virtual-machines-appear-as-invalid-or-or.html) for more information |
 
 
@@ -77,6 +77,7 @@ The following actions are always recommended for ensuring host maintenance opera
 
 Now that you've covered Azure VMware Solution private cloud maintenance best practices, you might want to learn about:
 
+- [How to configure Resource Health alerts for Azure VMware Solution](configure-azure-monitor-for-resource-health-for-azure-vmware-solution.md)
 - [Azure VMware Solution networking and interconnectivity concepts](architecture-networking.md)
 - [Azure VMware Solution storage concepts](architecture-storage.md)
 - [How to configure Azure Alerts in Azure VMware Solution](configure-alerts-for-azure-vmware-solution.md)

articles/azure-vmware/configure-azure-monitor-for-resource-health-for-azure-vmware-solution.md

@@ -0,0 +1,90 @@
+---
+title: Create an Azure Monitor resource health alert rule for Azure VMware Solution
+description: Learn about configuring Azure Monitor alerts for Resource Health for your Azure VMware Solution private cloud.
+ms.topic: how-to
+ms.service: azure-vmware
+ms.date: 08/05/2025
+---
+
+# Create an Azure Monitor resource health alert rule for Azure VMware Solution
+
+
+This article shows you how to create or edit a resource health alert rule in Azure Monitor for your Azure VMware Solution private cloud. To learn more about alerts, see the [alerts overview](/azure/azure-monitor/alerts/alerts-overview).
+
+Alerts triggered by these alert rules contain a payload that uses the [common alert schema](/azure/azure-monitor/alerts/alerts-common-schema).
+
+## Prerequisites
+
+To create or edit a Resource Health alert rule, you need:
+
+- An Azure subscription with an AVS private cloud deployed
+- Contributor (write) access to that subscription
+- Read permission on any action groups you intend to use
+
+## Create Resource Health alert rule
+
+### Access Resource Health blade
+
+1. In the Azure portal, navigate to your AVS private cloud resource.  
+1. From the left menu, select **Help** → **Resource Health**.
+   :::image type="content" source="media/resource-health/resource-health-left-nav.png" alt-text="Screenshot showing where to find Resource Health for the AVS private cloud.":::
+
+1. Click **Add resource health alert**.
+   :::image type="content" source="media/resource-health/resource-health-create-alert.png" alt-text="Screenshot showing add resource health alert button.":::
+
+### Define the alert condition
+
+* On the **Conditions** pane, select values for each of these fields:
+
+    | Field                        | Description                                                                                                              |
+    |------------------------------|--------------------------------------------------------------------------------------------------------------------------|
+    | **Event status**             | Select **Updated** as the event status                                                                                   |
+    | **Current resource status**  | Select the current resource status. Values are **Available**, **Degraded**, and **Unavailable**.                         |
+    | **Previous resource status** | (Optional) Select the previous resource status. Values are **Available**, **Degraded**, **Unavailable**, and **Unknown**.|
+    | **Reason type**              | Select the causes of the resource health events. Values are **Platform Initiated**, **Unknown**, and **User Initiated**. |
+
+    :::image type="content" source="media/resource-health/resource-health-condition.png" alt-text="Screenshot showing condition tabs while creating alerts using Resource Health for the AVS private cloud.":::
+
+### Configure actions
+
+1. Switch to the **Actions** tab and choose **Use action groups**.  
+1. Pick an existing action group or click **Create action group** to:
+   - Specify the subscription and resource group  
+   - For **Region**, choose **Global**. Resource Health alerts can only be located in the Global region (which is the default).
+
+   - Provide an **Action group name** and **Display name**  
+
+   :::image type="content" source="media/resource-health/resource-health-new-action-group.png" alt-text="Screenshot showing new action group creation wizard with basics tab.":::
+
+   - Under **Notification type**, select channels (Email, SMS, Push, Voice) and add stakeholder contacts
+   :::image type="content" source="media/resource-health/resource-health-action-group-notifications.png" alt-text="Screenshot showing new action group creation wizard with notifications tab." lightbox="media/resource-health/resource-health-action-group-notifications.png":::
+
+   - Under **Review + create**, review the details and click on **Create**
+
+### Review and create
+
+1. On the **Details** tab, fill in:
+   - **Alert rule name**
+   - Subscription and resource group for the rule
+   - Ensure **Enable alert rule upon creation** is checked
+
+   :::image type="content" source="media/resource-health/resource-health-action-group-details.png" alt-text="Screenshot showing new action group creation wizard with details tab.":::
+
+1. Click **Review + create**, then **Create**.
+
+   :::image type="content" source="media/resource-health/resource-health-alert-review-create.png" alt-text="Screenshot showing new alert rule creation wizard with review-create tab.":::
+
+## Manage alert rules
+
+- **View triggered alerts**: search for your alert rule name and select the **History** tab. You can click on any of the triggered alerts to know about it.
+
+   :::image type="content" source="media/resource-health/alert-rule-history.png" alt-text="Screenshot showing an alert rule history." lightbox="media/resource-health/alert-rule-history.png":::
+
+- **Edit an existing rule**: open its **Overview** page and click **Edit**.
+
+## Next steps
+
+- [Manage your alerts](/azure/azure-monitor/alerts/alerts-manage-alert-instances)
+- Learn more about the [ITSM Connector](/azure/azure-monitor/alerts/itsmc-overview)
+
+

articles/azure-vmware/ecosystem-app-monitoring-solutions.md

@@ -74,38 +74,6 @@ Unknown means that Resource Health hasn't received information about the resou
 
 Degraded means that Resource Health detected a loss in performance in either one or more private cloud resources, although it's still available for use. Different resources have their own criteria for when they report that they are degraded.
 
-
-
-#### Pre-configured Alarms enabled in Azure Resource Health
-
-
-|Alert Name|Remediation Mode|
-| -------- | -------- |
-|Physical Disk Health Alarm |System Remediation|
-|System Board Health Alarm|System Remediation|
-| Memory Health Alarm|System Remediation|
-|Storage Health Alarm|System Remediation|
-|Temperature Health Alarm |System Remediation|
-|Host Connection State Alarm|System Remediation|
-|High Availability (HA) host Status |System Remediation|
-| Network Connectivity Lost Alarm|System Remediation|
-|Virtual Storage (vSAN) Host Disk Error Alarm|System Remediation|
-|Voltage Health Alarm |System Remediation|
-|Processor Health Alarm| System Remediation|
-|Fan Health Alarm|System Remediation|
-|High pNIC error rate detected|System Remediation|
-|iDRAC critical alerts if there are hardware faults (CPU/DIMM/PCI bus/Voltage issues)|System Remediation|
-|vSphere HA restarted a virtual machine|System Remediation|
-|Virtual Storage (vSAN) High Disk Utilization|Customer Intervention Required|
-|Replacement Start and Stop Notification|System Remediation|
-|Repair Service notification to customers (Host reboot and Restart of Management services) |System Remediation|
-|Notification to customer when a Virtual Machine is configured to use an external device that prevents a maintenance operation|Customer Intervention Required|
-| Customer notification when CD-ROM is mounted on the Virtual Machine and its ISO image isn't accessible and blocks maintenance operation|Customer Intervention Required|
-|Notification to customer when an external Datastore mounted becomes inaccessible and will block maintenance operations|Customer Intervention Required|
-|Notification to customer when connected network adapter becomes inaccessible and blocks any maintenance operations|Customer Intervention Required|
-|VMware Network (NSX –T) alarms (Customer notification about License expiration)|Customer Intervention Required|
-
-
 ## Next Steps
 
 Now that you have configured an alert rule for your Azure VMware Solution private cloud, you can learn more about: 

articles/azure-vmware/introduction.md

@@ -34,7 +34,7 @@ You can deploy new or scale existing private clouds through the Azure portal or
 
 ## Azure VMware Solution private cloud extension with AV64 node size
 
-The AV64 is an Azure VMware Solution host SKU, which is available to expand the Azure VMware Solution private cloud built with the existing AV36, AV36P, or AV52 SKU. If you want to deploy AV64 directly, refer to [Azure VMWare Solution in an Azure Virtual Network](native-introduction.md). Use the [Microsoft documentation](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-vmware) to check for availability of the AV64 SKU in the region. 
+The AV64 is an Azure VMware Solution host SKU, which is available to expand the Azure VMware Solution private cloud built with the existing AV36, AV36P, or AV52 SKU. If you want to deploy AV64 directly, refer to [Azure VMware Solution in an Azure Virtual Network](native-introduction.md). Use the [Microsoft documentation](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-vmware) to check for availability of the AV64 SKU in the region. 
 
 :::image type="content" source="media/introduction/av64-mixed-sku-topology.png" alt-text="Diagram showing Azure VMware Solution private cloud with AV64 SKU in mixed SKU configuration." border="false" lightbox="media/introduction/av64-mixed-sku-topology.png":::
 
@@ -138,7 +138,7 @@ Azure VMware Solution doesn't store customer data.
 
 ## Host and software lifecycle maintenance
 
-Regular upgrades of the Azure VMware Solution private cloud and VMware software ensure the latest security, stability, and feature sets are running in your private clouds. For more information, see [Host maintenance and lifecycle management](azure-vmware-solution-host-remediation.md#host-maintenance-and-lifecycle-management).
+Regular upgrades of the Azure VMware Solution private cloud and VMware software ensure the latest security, stability, and feature sets are running in your private clouds. For more information, see [Host maintenance and lifecycle management](azure-vmware-solution-private-cloud-maintenance-best-practices.md#host-maintenance-and-lifecycle-management).
 
 ## Monitoring your private cloud