Merge pull request #8262 from MicrosoftDocs/main

Sync to live

Author: genlin

support/azure/virtual-machines/linux/linux-virtual-machine-cannot-start-fstab-errors.md

@@ -1,6 +1,6 @@
 ---
-title: Troubleshoot Linux VM boot issues due to fstab errors | Microsoft Learn
-description: Explains why Linux VM cannot start and how to solve the problem.
+title: Troubleshoot Linux VM boot issues due to fstab errors
+description: Explains why Linux VM can't start and how to solve the problem.
 services: virtual-machines
 documentationcenter: ''
 author: saimsh-msft
@@ -13,29 +13,32 @@ ms.topic: troubleshooting
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: azurecli
-ms.date: 04/15/2024
+ms.date: 02/19/2025
 ms.author: saimsh
 ---
+
 # Troubleshoot Linux VM boot issues due to fstab errors
 
 **Applies to:** :heavy_check_mark: Linux VMs
 
 [!INCLUDE [CentOS End Of Life](../../../includes/centos-end-of-life-note.md)]
 
-The Linux filesystem table, fstab is a configuration table which is designed to configure rules where specific file systems are detected and mounted in an orderly manner during the system boot process. 
-This article discusses multiple conditions where a wrong fstab configuration can lead to boot issue and provides troubleshooting guidance.
+The Linux filesystem table, fstab, is a configuration table that is designed to configure rules where specific file systems are detected and mounted in an orderly manner during the system boot process. 
+
+This article discusses multiple conditions where a wrong fstab configuration can lead to boot issues and provides troubleshooting guidance.
+
+Here are some common reasons that can lead to virtual machine (VM) boot issues due to fstab misconfiguration:
 
-Few common reasons that can lead to Virtual Machine Boot issues due to fstab misconfiguration are listed below:
 * Traditional filesystem name is used instead of the Universally Unique Identifier (UUID) of the filesystem.
 * An incorrect UUID is used. 
-* An entry exists for an unattached device without ```nofail``` option within fstab configuration.
-* Incorrect entry within fstab configuration.
+* An entry exists for an unattached device without the `nofail` option within the fstab configuration.
+* Incorrect entry within the fstab configuration.
 
 ## Identify fstab issues
 
-Check the current boot state of the VM in the serial log within the [Boot diagnostics] (/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) blade in the Azure portal. The VM will be in an Emergency Mode. You see log entries that resemble the following example leading to the Emergency Mode state:
+Check the current boot state of the VM in the serial log within the [Boot diagnostics](/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) blade in the Azure portal. The VM will be in an Emergency Mode. You see log entries that resemble the following example leading to the Emergency Mode state:
 
-```
+```output
 [K[[1;31m TIME [0m] Timed out waiting for device dev-incorrect.device.
 [[1;33mDEPEND[0m] Dependency failed for /data.
 [[1;33mDEPEND[0m] Dependency failed for Local File Systems.
@@ -44,91 +47,86 @@ Welcome to emergency mode! After logging in, type "journalctl -xb" to viewsystem
 Give root password for maintenance
 (or type Control-D to continue)
 ```
+
  >[!Note]
- > "/data" is an example of mount point used. Dependency failure for filesystem mount point will differ based on the  names used.
+ > `/data` is an example of mount point used. Dependency failure for filesystem mount point will differ based on the names used.
 
 ## Resolution
-There are 2 ways to resolve the issue:
+
+There are two ways to resolve the issue:
+
 * Repair the VM online
-    * [Use the Serial Console](#use-the-serial-console)
-* Repair the vm offline
+    * [Use the serial console](#use-the-serial-console)
+* Repair the VM offline
     * [Use Azure Linux Auto Repair (ALAR)](#use-azure-linux-auto-repair-alar)
-    * [Use Manual Method](#use-manual-method)
+    * [Use the manual method](#use-the-manual-method)
+
+### Repair the VM online
 
-### Repair the VM Online
 #### Use the serial console
-1. Connect to [the serial console](./serial-console-linux.md) of the VM from Azure portal.
-2. Manual access to single user mode is required to reconfigure fstab. The steps can vary based on the type of Linux OS in use and access to the root account. Follow [single user mode](serial-console-grub-single-user-mode.md) documentation to access single user mode for each supported Linux partner images.
+
+1. Connect to [the serial console](./serial-console-linux.md) of the VM from the Azure portal.
+2. Manual access to single-user mode is required to reconfigure fstab. The steps can vary based on the type of Linux OS used and access to the root account. Follow the [single-user mode](serial-console-grub-single-user-mode.md) documentation to access single-user mode for each supported Linux partner image.
 
 ##### Fstab troubleshooting steps
-1. Once the vm has booted into single user mode. Use your favorite text editor to open the fstab file.
 
-   ```
+1. Once the VM has booted into single-user mode. Use your favorite text editor to open the fstab file.
+
+   ```bash
    vi /etc/fstab
    ```
-2. Review the listed filesystems in `/etc/fstab`. Each line in the fstab file indicates a filesystem that is mounted when the VM starts. For more information about the syntax of the fstab file, run the `man fstab` command. To troubleshoot a boot failure, review the entry for the filesystem that failed to mount. It is a good practice to review each line to ensure that it is correct in both structure and content.  Few points to consider to correctly administer an fstab file are as follows:
 
-   * Fields on each line are separated by tabs or spaces. Blank lines are ignored. Lines that have a number sign (#) as the first character are comments. Commented lines can remain in the fstab file, but they won't be processed. We recommend that you comment fstab lines that you are unsure about instead of removing the lines.
-   * Mount the data disks on Azure VMs by using the UUID of the file system partition.To determine the UUID of the file system, run the `blkid` command. For more information about the syntax, run the `man blkid` command. Example of UUID entry in fstab file:
+2. Review the listed filesystems in `/etc/fstab`. Each line in the fstab file indicates a filesystem that is mounted when the VM starts. For more information about the syntax of the fstab file, run the `man fstab` command. To troubleshoot a boot failure, review the entry for the filesystem that failed to mount. It's a good practice to review each line to ensure that it's correct in both structure and content. A few points to consider to correctly administer a fstab file are as follows:
+
+   * Fields on each line are separated by tabs or spaces. Blank lines are ignored. Lines that have a number sign (#) as the first character are comments. Commented lines can remain in the fstab file, but they won't be processed. We recommend that you comment fstab lines that you're unsure about instead of removing the lines.
+   * Mount the data disks on Azure VMs by using the UUID of the file system partition. To determine the UUID of the file system, run the `blkid` command. For more information about the syntax, run the `man blkid` command. Example of the UUID entry in the fstab file:
 
       ```bash
       UUID=<UUID number here>  /data      xfs    defaults,nofail 0  0
       ```
+
    * Use the `nofail` option in the filesystem entries (data disks) to enable startup to continue even after errors occur in partitions for the corresponding entries. The `nofail` option helps make sure that the VM starts even if the file system is corrupted or if it doesn't exist at startup.
 
 5. Save the changes to the fstab file.
 
 6. Use `mount -a` as a best practice after making changes to the fstab entries. This will rerun the fstab configuration and notify the users of any existing syntax or entry errors.
 
-6. Once, the syntax and entries are verified, reboot the vm using the below command.
+6. Once the syntax and entries are verified, reboot the VM using the following command:
 
-   ```
+   ```bash
    reboot -f
    ```
 7. If the entries comment or fix was successful, the system should reach a bash prompt in the portal. Check whether you can connect to the VM.
-> [!Note]
-   > You can also use "ctrl+x" command which would also reboot the vm.
+
+   > [!Note]
+   > You can also use the `ctrl+x` command that will also reboot the VM.
 
 ### Repair the VM offline
 
-If the VM serial console access is not available, an alternative solution is to repair the vm offline. There are two ways to take an offline approach: 
+If the VM serial console access isn't available, an alternative solution is to repair the VM offline. There are two ways to take an offline approach: 
 
 #### Use Azure Linux Auto Repair (ALAR)
 
-Azure Linux Auto Repair (ALAR) scripts is a part of VM repair extension described in [Repair a Linux VM by using the Azure Virtual Machine repair commands](./repair-linux-vm-using-azure-virtual-machine-repair-commands.md). ALAR covers automation of multiple repair scenarios including `/etc/fstab` issues.
-
-The ALAR scripts use the repair extension `run` command and its `--run-id` option. The script-id for the automated recovery is: **linux-alar2**. Implement the following steps to automate fstab errors via offline ALAR approach:
+Azure Linux Auto Repair (ALAR) scripts are part of the VM repair extension described in [Use Azure Linux Auto Repair (ALAR) to fix a Linux VM](./repair-linux-vm-using-alar.md). ALAR covers the automation of multiple repair scenarios, including `/etc/fstab` issues.
 
-```azurecli-interactive
-az vm repair create --verbose -g centos7 -n cent7 --repair-username rescue --repair-password 'password!234' --copy-disk-name  repairdiskcopy
- ```
+The ALAR scripts use the repair extension `repair-button` to fix fstab issues by specifying `--button-command fstab`. This parameter triggers the automated recovery. Implement the following steps to automate fstab errors via the offline ALAR approach:
 
 ```azurecli-interactive
-az vm repair run --verbose -g centos7 -n cent7 --run-id linux-alar2 --parameters fstab --run-on-repair
- ```
-
-```azurecli-interactive
-az vm repair restore --verbose -g centos7 -n cent7
- ``` 
-
-> [!Note] 
-   >The resource group name "centos7, vm name "cent7", and --copy-disk-name "repairdiskcopy" are examples and the values need to change accordingly.
+az vm repair repair-button --button-command fstab --verbose rgtest --name vmtest
+```
 
-   >The fstab repair script will take a backup of the original file and strip off any lines in the /etc/fstab file which are not needed to boot a system. After successful start of the OS, edit the fstab again and correct any errors which didn’t allow a reboot of the system before. 
+> [!NOTE]
+> - Replace the resource group name `rgtest` and VM name `vmtest` accordingly.
+> - The repair VM script, in conjunction with the ALAR script, will temporarily create a resource group, a repair VM, and a copy of the affected VM's OS disk. It backs up the original **/etc/fstab** file and modifies it by removing or commenting out data file system entries that aren't required to boot the system.
+> - After the OS starts successfully, review and edit the **/etc/fstab** file to fix any errors that might have prevented a proper reboot. Finally, the `repair-button` script will automatically delete the resource group containing the repair VM.
 
-Alternatively, once a repair vm is created, the changes can also be implemented by manually logging into the repair vm, mounting the attached copy of OS disk and making changes to its fstab file. Follow the steps here: 
- * Create a repair VM using the `az vm repair create` command.
- * In order to mount and chroot to the filesystems of the attached OS disk in a rescue VM, follow the detailed [chroot instructions](./chroot-environment-linux.md).
- * Next, follow the same [fstab troubleshooting steps](#fstab-troubleshooting-steps) as above.
- * Once the changes are applied, `az vm repair restore` command can be used to perform automatic OS disk swap with the original VM. 
+#### Use the manual method
 
-#### Use Manual Method
+If both the serial console and ALAR approaches aren't possible or fail, the repair has to be performed manually. Follow the steps here to manually attach the OS disk to a recovery VM and swap the OS disk back to the original VM:
 
-If both serial console and ALAR approach is not possible or fails , the repair has to be performed manually. Follow the steps here to manually attach the OS disk to a recovery VM and swap the OS disk back to the original VM:
 * [Attach the OS disk to a recovery VM using the Azure portal](./troubleshoot-recovery-disks-portal-linux.md)
-* [Attach the OS disk to a recovery VM using Azure CLI](./troubleshoot-recovery-disks-linux.md)
-
-Once the OS disk is successfully attached to the recovery VM, follow the detailed [chroot instructions](./chroot-environment-linux.md) to mount and chroot to the filesystems of the attached OS disk. Then, implement [fstab troubleshooting steps](#fstab-troubleshooting-steps) to make appropriate changes to the fstab file of the problematic OS disk.
+* [Attach the OS disk to a recovery VM using the Azure CLI](./troubleshoot-recovery-disks-linux.md)
 
+Once the OS disk is successfully attached to the recovery VM, follow the detailed [chroot instructions](./chroot-environment-linux.md) to mount and chroot to the filesystems of the attached OS disk. Then, implement the [fstab troubleshooting steps](#fstab-troubleshooting-steps) to make appropriate changes to the fstab file of the problematic OS disk.
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/virtual-machines/linux/linux-vm-no-boot-incorrect-hugepages-configuration.md

@@ -250,7 +250,7 @@ To fix the issue, follow these steps:
     
     - [Repair the Linux VM using the Azure VM repair commands](repair-linux-vm-using-azure-virtual-machine-repair-commands.md).
     
-    - (Offline method) [Create a Rescue VM to fix VM boot issues manually](linux-virtual-machine-cannot-start-fstab-errors.md#use-manual-method).
+    - (Offline method) [Create a Rescue VM to fix VM boot issues manually](linux-virtual-machine-cannot-start-fstab-errors.md#use-the-manual-method).
 
 2. If you use the Azure VM repair commands or the offline method in step 1, follow the chroot process introduced in [Chroot environment in a Linux rescue VM](chroot-environment-linux.md).
 

support/entra/entra-id/app-integration/troubleshoot-wif10201-no-validkey-securitytoken-mvc.md

@@ -1,23 +1,23 @@
 ---
 title: ASP.NET MVC Application Error WIF10201 No Valid Key Mapping Found for SecurityToken
-description: This article provides guidance for troubleshooting the error, "WIF10201- No valid key mapping found for securityToken."
+description: This article provides guidance for troubleshooting the error, WIF10201- No valid key mapping found for securityToken.
 author: genlin
 ms.author: bachoang
 ms.service: entra-id
-ms.topic: troubleshooting-general
+ms.topic: troubleshooting-problem-resolution 
 ms.date: 02/05/2025
 ms.custom: sap:Issues Signing In to Applications
 ---
 
-# "WIF10201: No valid key mapping found for securityToken" error in ASP.NET application
+# WIF10201: No valid key mapping found for securityToken error in ASP.NET application
 
 This article provides guidance for troubleshooting an authentication issue that occurs in an ASP.NET MVC application that uses both [WS-Federation](https://github.com/Azure-Samples/active-directory-dotnet-webapp-wsfederation) OWIN middleware and [Windows Identity Foundation](../../../windows-server/user-profiles-and-logon/windows-identity-foundation.md) (WIF) to authenticate to Microsoft Entra ID.
 
 ## Symptoms
 
 The ASP.NET MVC application that was previously working generates the following error message although no changes were made to the application:
 
-```
+```output
 Error Details:
 Server Error in '/' Application.
 WIF10201: No valid key mapping found for securityToken: 'System.IdentityModel.Tokens.X509SecurityToken' and issuer: 'https://sts.windows.net/<Directory ID>/'.
@@ -29,7 +29,7 @@ Exception Details: System.IdentityModel.Tokens.SecurityTokenValidationException:
 
 ## Cause
 
-To validate the signature of the token that's returned by the Entra ID after a successful sign-in, WIF uses the certificate thumbprints that are in the Web.config file, as shown in the following example:
+To validate the signature of the token that's returned by the Entra ID after a successful sign-in, WIF uses the certificate thumbprints that are in the **Web.config** file, as shown in the following example:
 
 ```web.config
 <issuerNameRegistry type="System.IdentityModel.Tokens.ValidatingIssuerNameRegistry, 
@@ -49,8 +49,8 @@ System.IdentityModel.Tokens.ValidatingIssuerNameRegistry">
 
 The "WIF10201" error occurs if none of these certificate thumbprints match the one that's used by Entra ID to sign the token.
 
-The Entra ID uses a [signing key rollover mechanism](/entra/identity-platform/signing-key-rollover) to update the certificate that's used to sign authentication tokens periodically. This key rollover causes the initial certificate thumbprints that are configured in the Web.config file to become invalid.
+The Entra ID uses a [signing key rollover mechanism](/entra/identity-platform/signing-key-rollover) to update the certificate that's used to sign authentication tokens periodically. This key rollover causes the initial certificate thumbprints that are configured in the **Web.config** file to become invalid.
 
 ## Solution
 
-You can either manually update the certificate thumbprints that are in the Web.config file or automate the process through code. For more information, see [Best practices for keys metadata caching and validation](/entra/identity-platform/signing-key-rollover#best-practices-for-keys-metadata-caching-and-validation).
+You can either manually update the certificate thumbprints that are in the **Web.config** file or automate the process through code. For more information, see [Best practices for keys metadata caching and validation](/entra/identity-platform/signing-key-rollover#best-practices-for-keys-metadata-caching-and-validation).

support/power-platform/dataverse/auditing/setup-auditlog-troubleshooting.md

@@ -3,18 +3,15 @@ title: Troubleshooting sync problems in audit logs
 description: Provides common causes for sync issues to help troubleshooting.
 author: pete-msft
 ms.component: pa-admin
-ms.topic: conceptual
-ms.date: 10/03/2024
-ms.subservice: guidance-toolkit
+ms.date: 02/20/2025
 ms.author: petrip
-ms.reviewer: sericks
+ms.reviewer: paulliew
+ms.custom: sap:Microsoft Dataverse\Auditing
 search.audienceType: 
   - admin
 contributors:
 - Grant-Archibald-MS
-  
 ---
-
 # Troubleshooting sync problems in audit logs
 
 ## API permissions

support/power-platform/dataverse/data-integration/data-integrator-error-management.md

@@ -1,13 +1,12 @@
 ---
 title: "Error management and troubleshooting for data integration projects"
 description: "Troubleshoot issues and manage errors when executing data integration projects using the Data Integrator service."
-ms.topic: conceptual
 ms.component: pa-admin
-ms.date: 11/19/2021
+ms.date: 02/20/2025
 author: NHelgren
-ms.subservice: admin
 ms.author: nhelgren
-ms.reviewer: sericks
+ms.reviewer: nhelgren
+ms.custom: sap:Microsoft Dataverse\Microsoft Dataverse miscellaneous
 search.audienceType: 
   - admin
 ---

support/power-platform/dataverse/email-exchange-synchronization/troubleshooting-monitoring-server-side-synchronization.md

@@ -2,12 +2,11 @@
 title: Troubleshooting and monitoring server-side synchronization
 description: Troubleshooting and monitoring server-side synchronization
 ms.component: pa-admin
-ms.topic: conceptual
-ms.date: 01/16/2025
+ms.date: 02/20/2025
 author: rahulmital 
-ms.subservice: admin
 ms.author: rahulmital 
-ms.reviewer: sericks
+ms.reviewer: rahulmital
+ms.custom: sap:Microsoft Dataverse\Email and Exchange Synchronization
 search.audienceType: 
   - admin
 ---

support/power-platform/dataverse/environment-app-access/troubleshoot-missing-environments.md

@@ -2,12 +2,11 @@
 title: Troubleshoot missing environments
 description: "Learn how to update a record's owner, an Owning Business Unit, or both an Owner and Owning Business Unit because the record changes ownership."
 ms.component: pa-admin
-ms.topic: conceptual
-ms.date: 12/03/2024
-ms.subservice: admin
+ms.date: 02/20/2025
+ms.custom: sap:Microsoft Dataverse\Environment and app access issues
 author: davidme-ms
 ms.author: davidme 
-ms.reviewer: sericks
+ms.reviewer: iyanni
 search.audienceType: 
   - admin
 contributors: