Merge branch 'main' into Meera-SupportArticles-Working

Author: Cloud-Writer

.openpublishing.redirection.json

@@ -1,5 +1,30 @@
 {
   "redirections": [
+    {
+      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-sql-cluster-ag-fci-issues.md",
+      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-sql-cluster-ag-fci-scenarios",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/azure/virtual-machines/windows/performance-diagnostics.md",
+      "redirect_url": "/azure/azure-monitor/vm/performance-diagnostics?tabs=windows",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/azure/virtual-machines/windows/how-to-use-perfinsights.md",
+      "redirect_url": "/azure/azure-monitor/vm/performance-diagnostics-run?tabs=windows",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/azure/virtual-machines/windows/performance-diagnostics-vm-extension.md",
+      "redirect_url": "/azure/azure-monitor/vm/performance-diagnostics-analyze?tabs=windows",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/azure/virtual-machines/windows/perfinsights-and-scale-set-vm-instances.md",
+      "redirect_url": "/azure/azure-monitor/vm/performance-diagnostics-extension",
+      "redirect_document_id": false
+    },
     {
       "source_path": "support/windows-client/windows-tss/gather-information-using-tss-hyper-v-issues.md",
       "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-hyperv-scenarios",

support/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry.md

@@ -400,6 +400,8 @@ This issue occurs if the admin doesn't install the application or if no tenant u
 
 ### [Node.js](#tab/nodejs)
 
+#### Enable error logs
+
 Turn on internal logs by using the following setup. After you enable the logs, the console shows error logs, including any errors that are related to Microsoft Entra integration. Examples include failing to generate the token with the wrong credentials or if the ingestion endpoint doesn't authenticate by using the provided credentials.
 
 ```javascript

support/azure/virtual-desktop/toc.yml

@@ -35,5 +35,7 @@ items:
   href: ./troubleshoot-session-host-configuration-update.md
 - name: Troubleshoot session host virtual machine configuration
   href: ./troubleshoot-vm-configuration.md
+- name: Troubleshoot ephemeral OS disks
+  href: ./troubleshoot-ephemeral-os-disks.md
 - name: Win key remains held after pressing Ctrl+Win+L in a remote session
   href: win-key-remains-held-after-pressing-ctrl-win-l-in-remote-session.md

support/azure/virtual-desktop/troubleshoot-ephemeral-os-disks.md

@@ -0,0 +1,88 @@
+---
+title: Troubleshoot ephemeral OS disks in Azure Virtual Machines (VMs) and Azure Virtual Desktop (AVD)
+description: Resolve deployment failures, data loss, and feature limitations with ephemeral OS disks for Azure Virtual Machines (VMs) and Azure Virtual Desktop (AVD). Get troubleshooting steps and best practices.
+ms.topic: troubleshooting
+ms.date: 10/23/2025
+ms.reviewer: kaushika
+audience: itpro
+ms.custom: 
+- sap:Azure Virtual Desktop\Remote Desktop Clients\Redirecting resources via the client
+- pcy:wincomm-user-experience
+
+---
+# Troubleshoot ephemeral OS disks in Azure Virtual Machines (VMs) and Azure Virtual Desktop (AVD)
+
+## Summary
+
+Ephemeral OS disks (EOSD) are designed for Azure Virtual Machines (VMs) and Azure Virtual Desktop (AVD) session hosts, offering faster provisioning and reduced storage costs. However, users might encounter deployment failures, unexpected data loss, or functional limitations when the stateless design of EOSD and its dependencies on VM size and local storage aren't fully understood. This article helps identify and resolve these issues.
+
+## Symptoms
+
+- Deployment failures occur because of insufficient local storage for the OS image on specific VM sizes.
+- Loss of OS-level changes after stopping, deallocating, or reimaging a VM.
+- Confusion arises from unsupported EOSD features like snapshots, backups, and encryption.
+- Operational delays and increased support cases for AVD and stateless workloads.
+
+## Troubleshooting Guidance
+
+### VM size incompatibility
+
+**Cause**: Some VM sizes don't have enough local cache or temporary disk space to accommodate the OS image, causing deployment failures.
+
+**Solution**:
+
+- Check that the VM size supports EOSD by verifying the local cache or temporary disk size.
+- Use the Azure CLI command `EphemeralOSDiskSupported` to confirm compatibility.
+- For AVD, ensure the Temp Disk placement is selected during VM creation, as NVMe is not supported in public preview.
+
+### Misunderstanding EOSD persistence
+
+**Cause**: Ephemeral OS disks are designed as stateless disks, which means they don't support persistent features like snapshots, backups, or encryption.
+
+**Solution**: Use managed OS disks for persistent features. If you need features such as backups, snapshots, or encryption, switch to managed OS disks instead of EOSD for your Azure VMs or AVD session hosts.
+
+### Lifecycle mismanagement
+
+**Cause**: Stop and deallocate operations wipe the OS state on EOSD, causing data loss.
+
+**Solution**: Avoid stop and deallocate operations.
+
+- Don't stop or deallocate VMs using EOSD, as this leads to data loss. Instead, design stateless workloads.
+- Persist user profiles externally using FSLogix profile containers or Azure Files.
+
+### Incorrect DiffDiskPlacement configuration
+
+**Cause**: Selecting an unsupported placement option, such as NVMe, can cause deployment issues.
+
+**Solution**: Correct DiffDiskPlacement configuration
+
+- For AVD session hosts, ensure the Temp Disk placement is selected during deployment.
+- Avoid selecting NVMe placement during public preview to prevent deployment issues.
+
+### Regional SKU rollout gaps
+
+**Cause**: Incomplete rollout of supported SKUs or backend bugs cause regional deployment issues.
+
+**Solution**: Address regional SKU rollout gaps
+
+- Monitor Azure announcements for updates on SKU availability.
+- Deploy to another region or select a different SKU if rollout gaps affect your deployment.
+
+### Best practices
+- **Validate VM size and placement:** Before deployment, ensure your VM’s local cache or temporary disk can accommodate the OS image size.
+- **Design stateless workloads:** Persist user profiles and application data externally using FSLogix profile containers or Azure Files.
+- **Avoid stop/deallocate operations:** Use restart or delete/recreate logic for autoscale scenarios to prevent data loss.
+- **Communicate limitations upfront:** Inform teams that EOSD doesn't support snapshots, backups, or Azure Disk Encryption.
+- **Monitor regional availability:** Check supported SKUs and regions using Azure documentation before deployment.
+- **Set up automated configuration:** Use VM extensions or scripts to reapply settings and applications after reimaging.
+- **For AVD environments:**
+    1. Use Temp Disk for ephemeral OS disk placement (NVMe isn't supported in public preview).
+    1. Persist user profiles with FSLogix profile containers.
+    1. Store application packages on Azure Files or Azure NetApp Files.
+    1. Set up autoscale rules to delete and recreate hosts instead of deallocating them.
+
+### More information
+
+For further details, refer to the following resources:
+- [Ephemeral OS disks for AVD session hosts](/azure/virtual-desktop/deploy/session-hosts/ephemeral-os-disks)
+- [Ephemeral OS disks - Frequently Asked Questions](/azure/virtual-machines/ephemeral-os-disks-faq)

support/azure/virtual-machines/linux/convert-mbr-partition-to-gpt.md

@@ -2,9 +2,9 @@
 title: Failed to resize MBR partitions for a data disk larger than 2 TB
 description: Provides a solution to an issue where you can't resize a Master Boot Record (MBR) partition for a data disk larger than 2 TB in an Azure Linux virtual machine.
 ms.service: azure-virtual-machines
-ms.date: 04/29/2024
-ms.reviewer: brfett, v-weizhu
-ms.custom: sap:Assistance with resizing a disk, linux-related-content
+ms.date: 10/22/1025
+ms.reviewer: brfett
+ms.custom: sap:Assistance with disk operations, linux-related-content
 ---
 # Unable to resize MBR partition for a data disk larger than 2 TB in Linux virtual machine
 

support/azure/virtual-machines/linux/create-swap-file-linux-vm.md

@@ -1,13 +1,13 @@
 ---
 title: Create a SWAP file for an Azure Linux VM
 description: Describes how to create a SWAP file for an Azure Linux VM.
-ms.date: 09/15/2025
+ms.date: 10/22/2025
 ms.service: azure-virtual-machines
-ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
+ms.custom: sap:Assistance with disk operations, linux-related-content
 ms.collection: linux
-ms.author: mabicca
-author: mabicca
-ms.reviewer: v-weizhu
+ms.author: jarrettr
+author: JarrettRenshaw
+ms.reviewer: mabicca
 ---
 
 # Create a SWAP partition for an Azure Linux VM
@@ -87,7 +87,7 @@ You can create a SWAP partition by using one of the following options.
 1. Make the script executable:
 
     ```bash
-    chmod +x /var/lib/cloud/scripts/per-boot/swap.sh
+    sudo chmod +x /var/lib/cloud/scripts/per-boot/swap.sh
     ```
 
 1. Stop and start the VM. Stopping and starting the VM is only necessary the first time after you create the SWAP file.

support/azure/virtual-machines/linux/linux-hyperv-issue.md

@@ -67,15 +67,15 @@ Or
     1. Identify the file that disables the hv_netvsc driver and the corresponding line numbers by running the following command:
 
         ```bash
-        grep -nr "hv_netvsc" /etc/modprobe.d/
+        sudo grep -nr "hv_netvsc" /etc/modprobe.d/
         ```
 
     2. Modify the corresponding file and comment out or delete the hv_netvsc entries:
 
           :::image type="content" source="media/linux-hyperv-issue/hv-netvsc-disabled.png" alt-text="Screenshot that shows the possible configuration file contents used to disable network drivers.":::
 
         ```bash
-        vi /etc/modprobe.d/disable.conf
+        sudo vi /etc/modprobe.d/disable.conf
         ```
 
         > [!NOTE]
@@ -88,13 +88,13 @@ Or
     - For RHEL/SLES-based images
 
         ```bash
-        # dracut -f -v
+        sudo dracut -f -v
         ```
 
     - For Ubuntu/Debian-based images
 
         ```bash
-        # mkinitramfs -k -o /boot/initrd.img-$(uname -r)
+        sudo mkinitramfs -k -o /boot/initrd.img-$(uname -r)
         ```
 
 6. Reboot the VM.
@@ -104,19 +104,19 @@ Always take a backup of the original initial RAMdisk image to facilitate the rol
 - For RHEL-based images:
 
     ```bash
-    # cp /boot/initramfs-<kernelVersion>.img /boot/initramfs-<kernelVersion>.img.bak
+    sudo cp /boot/initramfs-<kernelVersion>.img /boot/initramfs-<kernelVersion>.img.bak
     ```
 
 - For SLES-based images:
 
     ```bash
-    # cp /boot/initrd-<kernelVersion> /boot/initrd-<kernelVersion>.bak
+    sudo cp /boot/initrd-<kernelVersion> /boot/initrd-<kernelVersion>.bak
     ```
 
 - For Ubuntu/Debian-based images:
 
     ```bash
-    # cp /boot/initrd.img-<kernelVersion> /boot/initrd.img-<kernelVersion>.bak
+    sudo cp /boot/initrd.img-<kernelVersion> /boot/initrd.img-<kernelVersion>.bak
     ```
 
 ### <a id="reenable-hv_netvsc-offline"></a>Solution 2: Enable Hyper-V network driver offline
@@ -154,7 +154,7 @@ If the issue continues even though the Hyper-V network driver is enabled, use on
 7. Generally, a NIC MAC address would only change if a NIC is deleted or added by the administrator or a NIC is updated in the backend. If network configuration via cloud-init isn't desired, and the `apply_network_config` parameter needs to be set to false, delete the */var/lib/cloud/instance/obj.pkl* file and reboot the system.
 
     ```bash
-    # rm /var/lib/cloud/instance/obj.pkl
+    sudo rm /var/lib/cloud/instance/obj.pkl
     ```
 
 8. Once the changes are applied, restart the system.
@@ -213,7 +213,7 @@ If the VM is inaccessible due to other Hyper-V drivers being disabled, use an of
     1. Run the following command to identify the file that disables the hv_utils, hv_vmbus, hv_storvsc, or hv_netvsc driver and the corresponding line number.
 
         ```bash
-        egrep -nr "hv_utils|hv_vmbus|hv_storvsc|hv_netvsc" /etc/modprobe.d/
+        sudo egrep -nr "hv_utils|hv_vmbus|hv_storvsc|hv_netvsc" /etc/modprobe.d/
         ```
 
     2. Modify the corresponding file and comment out or delete the hv_utils, hv_vmbus, hv_storvsc, or hv_netvsc entries. The entries will most commonly be any of the following (or both):
@@ -223,7 +223,7 @@ If the VM is inaccessible due to other Hyper-V drivers being disabled, use an of
         :::image type="content" source="media/linux-hyperv-issue/hv-disabled-example-2.png" alt-text="Screenshot that shows the possible configuration file contents used to disable kernel modules/drivers.":::
 
         ```bash
-        vi /etc/modprobe.d/disable.conf
+        sudo vi /etc/modprobe.d/disable.conf
         ```
 
     > [!IMPORTANT]
@@ -236,13 +236,13 @@ If the VM is inaccessible due to other Hyper-V drivers being disabled, use an of
     - For RHEL/SLES-based images
 
         ```bash
-        # dracut -f -v
+        sudo dracut -f -v
         ```
 
     - For Ubuntu/Debian-based images
 
         ```bash
-        # mkinitramfs -k -o /boot/initrd.img-$(uname -r)
+        sudo mkinitramfs -k -o /boot/initrd.img-$(uname -r)
         ```
 
 5. Once the changes are applied, use the `az vm repair restore` command to perform an automatic OS disk swap with the original VM and reboot the system.

support/azure/virtual-machines/linux/serial-console-linux.md

@@ -11,9 +11,8 @@ ms.service: azure-virtual-machines
 ms.collection: linux
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 10/16/2025
-ms.author: jarrettr
-ms.reviewer: mbifeld
+ms.date: 09/10/2025
+ms.author: mbifeld
 ---
 
 # Azure Serial Console for Linux
@@ -89,9 +88,8 @@ By default, all subscriptions have serial console access enabled. You can disabl
 
 ### Use Serial Console with custom boot diagnostics storage account firewall enabled
 
-> [!CAUTION]
-> There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions. This issue occurs because Azure Serial Console runs in Microsoft's internal tenant, and firewall rules on the customer-managed storage account might block its access, even with correct permissions.
-> To avoid connectivity issues, [switch to managed boot diagnostics](../windows/boot-diagnostics.md#enable-boot-diagnostics-on-existing-virtual-machine) (recommended) or remove the firewall on the custom boot diagnostics storage account.
+> [!WARNING]
+> There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions when using the [az serial-console](/cli/azure/serial-console) command. To avoid connectivity issues, use Serial Console in the Azure Portal.
 
 > [!IMPORTANT]
 > By the end of 2025, Azure Serial Console will no longer utilize boot diagnostics storage accounts for establishing a connection. No customer action is required for this change. This change doesn't affect serial logs or screenshots.

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

@@ -1,3 +1,4 @@
+items:
 - name: Welcome
   href: welcome-virtual-machines-linux.yml
 
@@ -262,13 +263,13 @@
     href: convert-mbr-partition-to-gpt.md
   - name: VHD is not supported when you create a VM in Azure
     href: ../windows/vhd-not-supported-vm-azure.md?context=/troubleshoot/azure/virtual-machines/linux/context/context
+  - name: Create a SWAP file
+    href: create-swap-file-linux-vm.md
 
 - name: Linux administration
   items:
   - name: Configure multiple NICs
     href: linux-vm-multiple-virtual-network-interfaces-configuration.md
-  - name: Create a SWAP file
-    href: create-swap-file-linux-vm.md
   - name: Maximum RAM memory of Linux VM
     href: max-linux-ram-limited-64-gb.md
   - name: Configure custom DNS servers