Skip to content

Commit 7add5d5

Browse files
authored
editorial changes
1 parent 0535b37 commit 7add5d5

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/azure/virtual-machines/windows/unexpected-vm-reboot-root-cause-analysis.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: virtual-machines
55
ms.service: azure-virtual-machines
66
ms.workload: infrastructure-services
77
ms.topic: how-to
8-
ms.date: 11/17/2023
8+
ms.date: 02/07/2025
99
ms.reviewer: tagangwa, macla, v-weizhu
1010
ms.custom: sap:VM restarted or stopped unexpectedly
1111
---
@@ -17,7 +17,7 @@ Azure provides methods to access detailed Root Cause Analysis (RCA) of unexpecte
1717

1818
## Method 1: Check resource health
1919

20-
Azure Resource Health is a vital service designed to monitor the health of individual Azure resources and provide actionable insights for troubleshooting issues. In cloud environments, where direct access to servers or infrastructure is not feasible, Resource Health plays a crucial role in minimizing troubleshooting efforts. Its primary goal is to help you quickly determine whether the root cause of a problem lies within your application or stems from an event within the Azure platform, thereby streamlining issue resolution and reducing downtime. You can use below steps to use resource health for understanifn the cause of unexpected VM reboot scenario.
20+
Azure Resource Health monitors the health of Azure resources and provides insights for troubleshooting. In cloud environments where direct access to server or infrastructure is impossible, Resource Health is important for reducing troubleshooting efforts. Its main purpose is to help quickly identify if the root cause of a problem is within your application or due to an event within the Azure platform, thus making issue resolution more efficient and minimizing downtime. To understand the cause of an unexpected VM reboot scenario using Resource Health, follow these steps:
2121

2222
1. Navigate to the impacted VM in the Azure portal.
2323
2. Go to the **Help** section and then select **Resource health**.

0 commit comments

Comments
 (0)