Merge branch 'main' of https://github.com/MicrosoftDocs/SupportArticles-docs-pr into ci3529

Author: Deland-Han

support/azure/azure-storage/files/security/files-troubleshoot-linux-nfs.md

@@ -3,7 +3,7 @@ title: Troubleshoot NFS file shares - Azure Files
 description: Troubleshoot issues with NFS Azure file shares.
 ms.service: azure-file-storage
 ms.custom: sap:Security, linux-related-content
-ms.date: 10/11/2024
+ms.date: 01/21/2025
 ms.reviewer: kendownie
 ---
 
@@ -24,6 +24,76 @@ This article lists common issues related to NFS Azure file shares and provides p
 | Standard file shares (GPv2), GRS/GZRS | :::image type="icon" source="media/files-troubleshoot-linux-nfs/no-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-linux-nfs/no-icon.png" border="false"::: |
 | Premium file shares (FileStorage), LRS/ZRS | :::image type="icon" source="media/files-troubleshoot-linux-nfs/no-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-linux-nfs/yes-icon.png" border="false":::|
 
+## Use the Always-On Diagnostics tool
+
+You can use the Always-On Diagnostics (AOD) tool to collect logs on NFSv4 and SMB Linux clients. The daemon runs in the background as a system service and can be configured to detect anomalies in a variety of sources such as dmesg logs, debug data, and error and latency metrics. It can capture data from tcpdump, nfsstat, mountstsat, and other sources, along with the system's CPU and memory usage. The tool can be useful for collecting debug information on field issues that can be hard to reproduce.
+
+AOD is currently compatible with systems running SUSE Linux Enterprise Server 15 (SLES15) and Red Hat Enterprise Linux 8 (RHEL8). Follow the appropriate installation steps.
+
+### [RHEL](#tab/RHEL)
+
+Follow these instructions to install the Always-On Diagnostics tool on Red Hat Enterprise Linux 8.
+
+1. Download the repo config package.
+   
+```
+curl -ssl -O https://packages.microsoft.com/config/rhel/8/packages-microsoft-prod.rpm
+```
+
+2. Install the repo config package.
+   
+```
+sudo rpm -i packages-microsoft-prod.rpm
+```
+
+3. Delete the repo config package after installing and updating the package index files.
+
+```
+rm packages-microsoft-prod.rpm
+sudo dnf update
+```
+
+4. Install the package.
+
+```
+sudo dnf install aod
+```
+
+### [SLES](#tab/SLES)
+
+Follow these instructions to install the Always-On Diagnostics tool on SUSE Linux Enterprise Server 15.
+
+1. Add the Microsoft repo. You might need to add the Microsoft repository key to your list of trusted keys.
+
+```
+sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
+sudo zypper addrepo --check --refresh --name 'Microsoft' https://packages.microsoft.com/sles/15/prod microsoft
+```
+
+2. Refresh the repositories.
+
+```
+sudo zypper refresh
+```
+
+3. Check if the repo has been added and the aod package is available for installation.
+
+```
+zypper search aod
+```
+
+4. Install the package.
+
+```
+sudo zypper install aod
+```
+
+### [Ubuntu](#tab/Ubuntu)
+
+The Always-On Diagnostics tool is not yet available for Ubuntu.
+
+---
+
 ## chgrp "filename" failed: Invalid argument (22)
 
 ### Cause 1: idmapping isn't disabled

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

@@ -11,8 +11,6 @@ ms.reviewer: kendownie, v-weizhu
 
 This article lists common issues that can occur when using SMB Azure file shares with Linux clients. It also provides possible causes and resolutions for these problems.
 
-You can use [AzFileDiagnostics](https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFileDiagnostics/Linux) to automate symptom detection and ensure that the Linux client has the correct prerequisites. It helps set up your environment to get optimal performance. You can also find this information in the [Azure file shares troubleshooter](https://support.microsoft.com/help/4022301/troubleshooter-for-azure-files-shares).
-
 > [!IMPORTANT]
 > This article only applies to SMB shares. For details on NFS shares, see [Troubleshoot NFS Azure file shares](/azure/storage/files/files-troubleshoot-linux-nfs).
 
@@ -24,6 +22,80 @@ You can use [AzFileDiagnostics](https://github.com/Azure-Samples/azure-files-sam
 | Standard file shares (GPv2), GRS/GZRS | :::image type="icon" source="media/files-troubleshoot-smb-authentication/yes-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-smb-authentication/no-icon.png" border="false"::: |
 | Premium file shares (FileStorage), LRS/ZRS | :::image type="icon" source="media/files-troubleshoot-smb-authentication/yes-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-smb-authentication/no-icon.png" border="false"::: |
 
+## Run diagnostics
+
+Diagnostics tools can be helpful for ensuring that clients have the correct prerequisites and for collecting debug information on field issues that can be hard to reproduce.
+
+### Use AzFileDiagnostics
+
+You can use [AzFileDiagnostics](https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFileDiagnostics/Linux) to automate symptom detection and ensure that the Linux client has the correct prerequisites. It helps set up your environment to get optimal performance.
+
+### Use the Always-On Diagnostics tool
+
+You can also use the Always-On Diagnostics (AOD) tool to collect logs on SMB and NFSv4 Linux clients. The daemon runs in the background as a system service and can be configured to detect anomalies in a variety of sources such as dmesg logs, debug data, and error and latency metrics. It can capture data from tcpdump, nfsstat, mountstsat, and other sources, along with the system's CPU and memory usage.
+
+AOD is currently compatible with systems running SUSE Linux Enterprise Server 15 (SLES15) and Red Hat Enterprise Linux 8 (RHEL8). Follow the appropriate installation steps.
+
+#### [SLES](#tab/SLES)
+
+Follow these instructions to install the Always-On Diagnostics tool on SUSE Linux Enterprise Server 15.
+
+1. Add the Microsoft repo. You might need to add the Microsoft repository key to your list of trusted keys.
+
+```
+sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
+sudo zypper addrepo --check --refresh --name 'Microsoft' https://packages.microsoft.com/sles/15/prod microsoft
+```
+
+2. Refresh the repositories.
+
+```
+sudo zypper refresh
+```
+
+3. Check if the repo has been added and the aod package is available for installation.
+
+```
+zypper search aod
+```
+
+4. Install the package.
+
+```
+sudo zypper install aod
+```
+
+#### [RHEL](#tab/RHEL)
+
+Follow these instructions to install the Always-On Diagnostics tool on Red Hat Enterprise Linux 8.
+
+1. Download the repo config package.
+   
+```
+curl -ssl -O https://packages.microsoft.com/config/rhel/8/packages-microsoft-prod.rpm
+```
+
+2. Install the repo config package.
+   
+```
+sudo rpm -i packages-microsoft-prod.rpm
+```
+
+3. Delete the repo config package after installing and updating the package index files.
+
+```
+rm packages-microsoft-prod.rpm
+sudo dnf update
+```
+
+4. Install the package.
+
+```
+sudo dnf install aod
+```
+
+---
+
 ## <a id="timestampslost"></a>Time stamps were lost when copying files
 
 On Linux/Unix platforms, the `cp -p` command fails if different users own file 1 and file 2.

support/azure/index.yml

@@ -115,10 +115,10 @@ productDirectory:
     - url: site-recovery/welcome-site-recovery.yml
       text: Troubleshooting articles for Site Recovery
   - title: Azure Virtual Desktop
-    imageSrc: "https://learn.microsoft.com/static/ui/media/product/azure/virtual-desktop.svg"
+    imageSrc: "https://static.docs.com/ui/media/product/azure/virtual-desktop.svg"
     links:
     - url: virtual-desktop/welcome-virtual-desktop.yml
-      text: Troubleshoot common Azure Virtual Desktop issues
+      text: Troubleshooting articles for Azure Virtual Desktop
   - title: Virtual Machines
     imageSrc: "https://static.docs.com/ui/media/product/azure/virtual-machine.svg"
     links:

support/azure/virtual-desktop/includes/include-troubleshoot-azure-ad-joined-connections-all.md

@@ -1,27 +1,29 @@
 ---
-
 ms.reviewer: daknappe
 ms.topic: include
-ms.date: 11/21/2022
+ms.date: 01/21/2025
 ---
-
 ### Your account is configured to prevent you from using this device
 
-If you come across an error saying **Your account is configured to prevent you from using this device. For more information, contact your system administrator**, ensure the user account was given the [Virtual Machine User Login role](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#azure-role-not-assigned) on the VMs. 
+If you come across an error saying:
+
+> Your account is configured to prevent you from using this device. For more information, contact your system administrator.
+
+Ensure the user account was given the [Virtual Machine User Login role](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#azure-role-not-assigned) on the virtual machines (VMs).
 
 ### The user name or password is incorrect
 
 If you can't sign in and keep receiving an error message that says your credentials are incorrect, first make sure you're using the right credentials. If you keep seeing error messages, check to make sure you've fulfilled the following requirements:
 
-- Have you assigned the **Virtual Machine User Login** role-based access control (RBAC) permission to the virtual machine (VM) or resource group for each user?
-- Does your Conditional Access policy exclude multifactor authentication requirements for the **Azure Windows VM sign-in** cloud application?
+- Have you assigned the Virtual Machine User Login role-based access control (RBAC) permission to the VM or resource group for each user?
+- Does your Conditional Access policy exclude multifactor authentication requirements for the Azure Windows VM sign-in cloud application?
 
-If you've answered no to either of those questions, you'll need to reconfigure your multifactor authentication. To reconfigure your multifactor authentication, follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa?tabs=avd#azure-ad-joined-session-host-vms#azure-ad-joined-session-host-vms).
+If you've answered no to either of those questions, you'll need to reconfigure your multifactor authentication. To reconfigure your multifactor authentication, follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa#azure-ad-joined-session-host-vms).
 
-> [!IMPORTANT] 
+> [!IMPORTANT]
 > VM sign-ins don't support per-user enabled or enforced Microsoft Entra multifactor authentication. If you try to sign in with multifactor authentication on a VM, you won't be able to sign in and will receive an error message.
 
-If you have [integrated Microsoft Entra logs with Azure Monitor logs](/entra/identity/monitoring-health/howto-integrate-activity-logs-with-azure-monitor-logs) to access your Microsoft Entra sign-in logs through Log Analytics, you can see if you've enabled multifactor authentication and which Conditional Access policy is triggering the event. The events shown are non-interactive user login events for the VM, which means the IP address will appear to come from the external IP address from which your VM accesses Microsoft Entra ID. 
+If you have [integrated Microsoft Entra logs with Azure Monitor logs](/entra/identity/monitoring-health/howto-integrate-activity-logs-with-azure-monitor-logs) to access your Microsoft Entra sign-in logs through Log Analytics, you can see if you've enabled multifactor authentication and which Conditional Access policy is triggering the event. The events shown are non-interactive user login events for the VM, which means the IP address will appear to come from the external IP address from which your VM accesses Microsoft Entra ID.
 
 You can access your sign-in logs by running the following Kusto query:
 

support/azure/virtual-desktop/includes/include-troubleshoot-azure-ad-joined-connections-android-chrome-os.md

@@ -1,10 +1,12 @@
 ---
-
 ms.reviewer: daknappe
 ms.topic: include
-ms.date: 11/21/2022
+ms.date: 01/21/2025
 ---
-
 ### Error code 2607 - We couldn't connect to the remote PC because your credentials did not work
 
-If you come across an error saying **We couldn't connect to the remote PC because your credentials did not work. The remote machine is AADJ joined.** with error code 2607 when using the Android client, ensure that you [enabled connections from other clients](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#connect-using-the-other-clients).
+If you come across the following error with error code 2607 when using the Android client:
+
+> We couldn't connect to the remote PC because your credentials did not work. The remote machine is AADJ joined.
+
+Ensure that you [enabled connections from other clients](/azure/virtual-desktop/deploy-azure-ad-joined-vm#connect-using-the-other-clients).

support/azure/virtual-desktop/includes/include-troubleshoot-azure-ad-joined-connections-web.md

@@ -1,14 +1,20 @@
 ---
-
 ms.reviewer: daknappe
 ms.topic: include
-ms.date: 11/21/2022
+ms.date: 01/21/2025
 ---
-
 ### Sign in failed. Please check your username and password and try again
 
-If you come across an error saying **Oops, we couldn't connect to *NAME*. Sign in failed. Please check your username and password and try again.** when using the web client, ensure that you [enabled connections from other clients](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#connect-using-the-other-clients).
+If you come across the following error when using the web client:
+
+> Oops, we couldn't connect to *NAME*. Sign in failed. Please check your username and password and try again.
+
+Ensure that you [enabled connections from other clients](/azure/virtual-desktop/deploy-azure-ad-joined-vm#connect-using-the-other-clients).
 
 ### We couldn't connect to the remote PC because of a security error
 
-If you come across an error saying **Oops, we couldn't connect to *NAME*. We couldn't connect to the remote PC because of a security error. If this keeps happening, ask your admin or tech support for help.**, you have Conditional Access policies restricting access. Follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa?tabs=avd#azure-ad-joined-session-host-vms#azure-ad-joined-session-host-vms) to enforce Microsoft Entra multifactor authentication for your Microsoft Entra joined VMs.
+If you come across an error:
+
+> Oops, we couldn't connect to *NAME*. We couldn't connect to the remote PC because of a security error. If this keeps happening, ask your admin or tech support for help.
+
+You have Conditional Access policies restricting access. Follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa#azure-ad-joined-session-host-vms) to enforce Microsoft Entra multifactor authentication for your Microsoft Entra joined VMs.

support/azure/virtual-desktop/includes/include-troubleshoot-azure-ad-joined-connections-windows.md

@@ -1,22 +1,28 @@
 ---
-
 ms.reviewer: daknappe
 ms.topic: include
-ms.date: 11/21/2022
+ms.date: 01/21/2025
 ---
-
 ### The logon attempt failed
 
-If you come across an error saying **The logon attempt failed** on the Windows Security credential prompt, verify the following:
+If you come across an error saying "The logon attempt failed" on the Windows Security credential prompt, verify the following:
 
 - You're using a device that is Microsoft Entra joined or Microsoft Entra hybrid joined to the same Microsoft Entra tenant as the session host.
 - The [PKU2U protocol is enabled](/windows/security/threat-protection/security-policy-settings/network-security-allow-pku2u-authentication-requests-to-this-computer-to-use-online-identities) on both the local PC and the session host.
-- [Per-user multifactor authentication is disabled](/azure/virtual-desktop/set-up-mfa?tabs=avd#azure-ad-joined-session-host-vms#azure-ad-joined-session-host-vms) for the user account as it's not supported for Microsoft Entra joined VMs.
+- [Per-user multifactor authentication is disabled](/azure/virtual-desktop/set-up-mfa#azure-ad-joined-session-host-vms) for the user account as it's not supported for Microsoft Entra joined VMs.
 
 ### The sign-in method you're trying to use isn't allowed
 
-If you come across an error saying **The sign-in method you're trying to use isn't allowed. Try a different sign-in method or contact your system administrator**, you have Conditional Access policies restricting access. Follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa?tabs=avd#azure-ad-joined-session-host-vms#azure-ad-joined-session-host-vms) to enforce Microsoft Entra multifactor authentication for your Microsoft Entra joined VMs.
+If you come across an error:
+
+> The sign-in method you're trying to use isn't allowed. Try a different sign-in method or contact your system administrator.
+
+You have Conditional Access policies restricting access. Follow the instructions in [Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access](/azure/virtual-desktop/set-up-mfa#azure-ad-joined-session-host-vms) to enforce Microsoft Entra multifactor authentication for your Microsoft Entra joined VMs.
+
+### A specified logon session does not exist. It may already have been terminated
+
+If you come across an error:
 
-### A specified logon session does not exist. It may already have been terminated.
+> An authentication error occurred. A specified logon session does not exist. It may already have been terminated.
 
-If you come across an error that says, **An authentication error occurred. A specified logon session does not exist. It may already have been terminated**, verify that you properly created and configured the Kerberos server object when [configuring single sign-on](/azure/virtual-desktop/configure-single-sign-on).
+Verify that you properly created and configured the Kerberos server object when [configuring single sign-on](/azure/virtual-desktop/configure-single-sign-on).