Merge pull request #8196 from MicrosoftDocs/main

Auto push to live 2025-02-11 02:00:02

Author: Deland-Han

.openpublishing.redirection.developer.json

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Files identity-based authentication and authorization
 description: Troubleshoot problems using identity-based authentication to connect to SMB Azure file shares and see possible resolutions.
 ms.service: azure-file-storage
 ms.custom: sap:Security, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
-ms.date: 02/10/2025
+ms.date: 02/11/2025
 ms.reviewer: kendownie, v-surmaini, v-weizhu
 ---
 # Troubleshoot Azure Files identity-based authentication and authorization issues (SMB)
@@ -77,23 +77,23 @@ Second, try [mounting Azure file share with storage account key](/azure/storage/
 
 Third, you can run the `Debug-AzStorageAccountAuth` cmdlet to conduct a set of basic checks on your AD configuration with the logged-on AD user. This cmdlet is supported on [AzFilesHybrid v0.1.2+ version](https://github.com/Azure-Samples/azure-files-samples/releases). 
 
-Sign in to Azure PowerShell interactively as an AD user that has owner permission on the target storage account:
+1. Sign in to Azure PowerShell interactively as an AD user that has owner permission on the target storage account:
 
-```azurepowershell-interactive
-Connect-AzAccount
-```
+    ```azurepowershell-interactive
+    Connect-AzAccount
+    ```
 
-Then run the debug cmdlet:
+2. Run the `Debug-AzStorageAccountAuth` cmdlet:
 
-```azurepowershell-interactive
-$ResourceGroupName = "<resource-group-name-here>"
-$StorageAccountName = "<storage-account-name-here>"
+    ```azurepowershell-interactive
+    $ResourceGroupName = "<resource-group-name-here>"
+    $StorageAccountName = "<storage-account-name-here>"
 
-Debug-AzStorageAccountAuth `
-    -StorageAccountName $StorageAccountName `
-    -ResourceGroupName $ResourceGroupName `
-    -Verbose
-```
+    Debug-AzStorageAccountAuth `
+        -StorageAccountName $StorageAccountName `
+        -ResourceGroupName $ResourceGroupName `
+        -Verbose
+    ```
 
 The cmdlet performs these checks in sequence and provides guidance for failures:
 
@@ -149,20 +149,20 @@ First, make sure that you've followed the steps to [enable Microsoft Entra Kerbe
 
 Second, you can run the `Debug-AzStorageAccountAuth` cmdlet to perform a set of basic checks. This cmdlet is supported for storage accounts configured for Microsoft Entra Kerberos authentication, on [AzFilesHybrid v0.3.0+ version](https://github.com/Azure-Samples/azure-files-samples/releases).
 
-Sign in to Azure PowerShell interactively as an AD user that has owner permission on the target storage account:
+1. Sign in to Azure PowerShell interactively as an AD user that has owner permission on the target storage account:
 
-```azurepowershell-interactive
-Connect-AzAccount
-```
+    ```azurepowershell-interactive
+    Connect-AzAccount
+    ```
 
-Then run the debug cmdlet:
+2. Run the `Debug-AzStorageAccountAuth` cmdlet:
 
-```azurepowershell-interactive
-$ResourceGroupName = "<resource-group-name-here>"
-$StorageAccountName = "<storage-account-name-here>"
+    ```azurepowershell-interactive
+    $ResourceGroupName = "<resource-group-name-here>"
+    $StorageAccountName = "<storage-account-name-here>"
 
-Debug-AzStorageAccountAuth -StorageAccountName $StorageAccountName -ResourceGroupName $ResourceGroupName -Verbose
-```
+    Debug-AzStorageAccountAuth -StorageAccountName $StorageAccountName -ResourceGroupName $ResourceGroupName -Verbose
+    ```
 
 The cmdlet performs these checks in sequence and provides guidance for failures:
 

support/azure/azure-storage/files/security/files-troubleshoot-smb-authentication.md

@@ -350,7 +350,7 @@
   - name: Unlock the encrypted disk for offline repair
     href: unlock-encrypted-linux-disk-offline-repair.md
   - name: How to display encryption settings with Resource Explorer
-    href: /azure/virtual-machines/linux/how-to-display-encryption-settings-with-azure-resource-explorer.md
+    href: how-to-display-encryption-settings-with-azure-resource-explorer.md
   - name: FAQ
     href: /azure/virtual-machines/linux/disk-encryption-faq?context=/troubleshoot/azure/virtual-machines/linux/context/context
 

support/azure/virtual-machines/linux/toc.yml

@@ -5,8 +5,8 @@ services: virtual-machines
 ms.service: azure-virtual-machines
 ms.workload: infrastructure-services
 ms.topic: how-to
-ms.date: 11/17/2023
-ms.reviewer: tagangwa, macla, v-weizhu
+ms.date: 02/11/2025
+ms.reviewer: tagangwa, macla, sinhamanisha, v-weizhu
 ms.custom: sap:VM restarted or stopped unexpectedly
 ---
 # How to check Root Cause Analysis of unexpected Azure virtual machine reboots
@@ -17,6 +17,8 @@ Azure provides methods to access detailed Root Cause Analysis (RCA) of unexpecte
 
 ## Method 1: Check resource health
 
+Azure Resource Health monitors the health of Azure resources and provides insights for troubleshooting. In cloud environments where direct access to servers or infrastructure is impossible, Resource Health is important to reduce 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:
+
 1. Navigate to the impacted VM in the Azure portal.
 2. Go to the **Help** section and then select **Resource health**.
 3. Check the health events for the unexpected VM reboot to get RCA information.