Merge branch 'main' into CI-7835

Author: ryanberg-aquent

.openpublishing.redirection.json

@@ -13922,6 +13922,10 @@
     {
       "source_path": "support/power-platform/power-automate/desktop-flows/ui-automation/ui-sap-automation/sap-click-element-dpi.md",
       "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/sap-automation/sap-click-element-dpi"
+    },
+    {
+      "source_path": "support/power-platform/power-automate/desktop-flows/browser-automation/browser-automation-error-after-chromium-update.md",
+      "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/failed-to-assume-control-of-edge-chrome-firefox-error"
     }
   ]
 }

support/azure/azure-monitor/app-insights/availability/availability-monitoring-common-issues-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: Review a list of frequently asked questions (FAQ) about common issues that occur when you use Application Insights availability monitoring.
   ms.topic: faq
   ms.date: 07/09/2025
-  ms.reviewer: v-leedennis, toddfous, v-weizhu
+  ms.reviewer: toddfous
   ms.service: azure-monitor
   ms.custom: sap:Availability Tests
 

support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md

@@ -479,7 +479,7 @@ If you accidentally attached by using an invalid shared access signature URL and
 Storage Explorer comes packaged with all dependencies it needs to run on Windows.
 
 > [!NOTE]
-> Some components need command line access. If it's restricted, Storage Explorer might not work as expected. If you encounter issues, contact your system administrator.
+> Some components need command line access. If restricted, Storage Explorer might not work as expected. If you encounter issues, contact your system administrator.
 
 ## [macOS](#tab/macOS)
 
@@ -840,7 +840,7 @@ docker run \
 
 ## Storage Explorer doesn't run within FSLogix session
 
-If FSLogix manages your user profile, Storage Explorer might be unable to run due to an `EEXIST` error. The error occurs due to a known issue with recent versions of FSLogix. If you encounter the error, you can work around it by following these steps:
+If FSLogix manages your user profile, Storage Explorer might be unable to run due to an `EEXIST` error. The error occurs due to a known issue with certain versions of FSLogix. If you encounter the error, make sure you're using the latest version of FSLogix. If the issue still occurs, you can work around it by following these steps:
 
 1. Open the Group Policy Management Console (gpmc.msc).
 

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

@@ -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/11/2025
+ms.date: 12/05/2025
 ms.reviewer: kendownie, v-surmaini, v-weizhu
 ---
 # Troubleshoot Azure Files identity-based authentication and authorization issues (SMB)
@@ -173,12 +173,67 @@ The cmdlet performs these checks in sequence and provides guidance for failures:
 
 If you just want to run a subselection of the previous checks, you can use the `-Filter` parameter, along with a comma-separated list of checks to run.
 
+## Mount to Azure Files fails when using Entra Kerberos due to unsupported Kerberos encryption types
+
+When mounting an Azure file share using Entra Kerberos authentication, the mount operation fails. Log collection might show that the Kerberos service ticket can't be decrypted.
+You might also find that the following registry key is configured: `HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\SupportedEncryptionTypes`
+
+### Cause
+
+If the `SupportedEncryptionTypes` registry key is configured with a value that does **not include AES**, Windows will only allow the encryption types specified in the bitmask. For example, the value `0x7` indicates that the client supports only the following Kerberos encryption types:
+
+- DES_CBC_CRC  
+- DES_CBC_MD5  
+- RC4_HMAC  
+
+Because Entra Kerberos always encrypts service tickets with **AES-256 (AES256-CTS-HMAC-SHA1-96)**, mounts will fail if AES isn't included in the supported encryption types for the account or machine.
+
+> [!NOTE]  
+> AES encryption is enabled by default on modern Windows operating systems. If the `SupportedEncryptionTypes` registry key isn't configured, Windows will automatically negotiate AES when available.
+
+### Solution
+
+To successfully mount Azure file shares using Entra Kerberos, AES-256 must be included in the supported encryption types.
+
+Use one of the following options:
+
+#### Option 1: Remove the registry key (recommended if not intentionally configured)
+
+If the encryption types weren't deliberately restricted:
+
+1. Delete the registry key: `HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\SupportedEncryptionTypes`
+1. Reboot the computer.
+
+After rebooting, retry mounting the file share.
+
+> [!TIP]  
+> Removing the key restores Windows default behavior, allowing Active Directory to automatically negotiate AES for Kerberos tickets.
+
+#### Option 2: Explicitly enable AES-256 using Group Policy
+
+If your organization requires explicitly configured Kerberos encryption types:
+
+1. Press **Win + R**, type `gpedit.msc`, and select **Enter**.
+1. Navigate to:  **Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options**
+1. Open **Network Security: Configure encryption types allowed for Kerberos**.
+1. Enable the following encryption types:
+   - **AES256_HMAC_SHA1**  
+   - **AES128_HMAC_SHA1** (optional)  
+1. Apply the change and reboot the computer.
+
+After rebooting, retry mounting the file share.
+
+> [!IMPORTANT]  
+> Entra Kerberos requires **AES256_HMAC_SHA1** to successfully mount Azure file shares. RC4 or DES-only configurations will fail.
+> To understand more about registry keys, see [Decrypting the Selection of Supported Kerberos Encryption Types](https://techcommunity.microsoft.com/blog/coreinfrastructureandsecurityblog/decrypting-the-selection-of-supported-kerberos-encryption-types/1628797).
+
 ## Unable to configure directory/file level permissions (Windows ACLs) with Windows File Explorer
 
 ### Symptom
 
-You might experience one of the symptoms described below when trying to configure Windows ACLs with File Explorer on a mounted file share:
-- After you click on **Edit permission** under the Security tab, the Permission wizard doesn't load. 
+You might experience one of the symptoms described below when trying to configure Windows ACLs with Windows File Explorer on a mounted file share:
+
+- After you click on **Edit permission** under the **Security** tab, the Permission wizard doesn't load. 
 - When you try to select a new user or group, the domain location doesn't display the right AD DS domain. 
 - You're using multiple AD forests and get the following error message: "The Active Directory domain controllers required to find the selected objects in the following domains are not available. Ensure the Active Directory domain controllers are available, and try to select the objects again."
 

support/azure/information-protection/troubleshoot-aip-issues.md

@@ -2,7 +2,7 @@
 title: How to troubleshoot Azure Information Protection policy issues
 description: Discusses how to troubleshoot Azure Information Protection policy issues.
 ms.date: 04/07/2022
-ms.service: information-protection
+ms.service: azure-information-protection
 ms.author: jarrettr
 author: JarrettRenshaw
 ms.reviewer: 

support/azure/information-protection/welcome-information-protection.yml

@@ -7,7 +7,7 @@ metadata:
   title: Troubleshoot common issues with Azure Information Protection
   description: Documentation for troubleshooting common issues with Azure Information Protection. # Required; article description that is displayed in search results. < 160 chars.
   services: azure
-  ms.service: information-protection #Required; service per approved list. service slug assigned to your service by ACOM.
+  ms.service: azure-information-protection
   ms.topic: landing-page # Required
   author: JarrettRenshaw  #Required; your GitHub user alias, with correct capitalization.
   ms.author: jarrettr #Required; microsoft alias of author; optional team alias.

support/azure/virtual-machines/linux/linux-azure-guest-agent-tools-vmassist.md

@@ -4,10 +4,10 @@ description: Provides script-based tool to help diagnose and resolve Azure Guest
 author: JarrettRenshaw
 ms.author: jarrettr
 manager: dcscontentpm
-ms.date: 10/24/2025
+ms.date: 12/04/2025
 ms.reviewer: v-jsitser, scotro, v-ryanberg
 ms.service: azure-virtual-machines
-ms.custom: sap:zzzz
+ms.custom: sap:VM Extensions not operating correctly
 ---
 #  Troubleshooting Tool for Linux Guest Agent - VM assist
 
@@ -59,11 +59,12 @@ If no issues are discovered during the base checks by using bash, the Python scr
 
 ## How to run the tool
 
-The VM assist scripting is run initially from the documentation. Subsequently, you can run the bash script directly: `vmassist.sh` as root or by using `sudo`.
+Go to the following GitHub location and follow the instructions there to [download, install, and run the tool](https://github.com/Azure/azure-support-scripts/blob/master/vmassist/linux/README.md). Subsequently, you can run the bash script directly: `vmassist.sh` as root or by using `sudo`.
 
 If you open a support request, please include both of these files to aid the support agent who assists you.
 
 ## Known issues
+
 - Don't try to run VM assist on appliances. Appliances don't run on general purpose operating systems, and the guest agent might not run at all.
 - Distributions outside PAYG versions of RedHat or SUSE, or any Ubuntu or Mariner or Azure Linux, might display false positive warnings about repository names. This situation requires a more careful reading because even official repositories might not match strict pattern matching. This condition is true because we don't build cases for all distributions.
 - Ubuntu 24.04 has a different architecture of the SSH service. It might flag the service even if the service is operating well.

support/azure/virtual-machines/windows/serial-console-overview.md

@@ -32,13 +32,16 @@ Serial Console is available for virtual machines and virtual machine scale sets
 - Australia Central 2
 - Australia East
 - Australia Southeast
+- Austria East
+- Belgium Central
 - Brazil South
 - Brazil Southeast
 - Canada Central
 - Canada East
 - Central India
 - Central US
 - Central US EUAP
+- Chile Central
 - China East 2
 - China East 3
 - China North 2
@@ -50,12 +53,15 @@ Serial Console is available for virtual machines and virtual machine scale sets
 - France South
 - Germany North
 - Germany West Central
+- Indonesia Central
 - Israel Central
+- Israel Northwest
 - Italy North
 - Japan East
 - Japan West
 - Korea Central
 - Korea South
+- Malaysia West
 - Mexico Central
 - New Zealand North
 - North Central US

support/azure/virtual-machines/windows/windows-vm-wureset-tool.md

@@ -9,13 +9,13 @@ ms.date: 11/18/2025
 ms.custom: sap:Cannot create a VM, H1Hack27Feb2017
 ms.reviewer: macla, scotro, glimoli, jarrettr, azurevmcptcic
 ---
-# Azure Virtual Machine (VM) Windows servicing stack reset tool
+# Azure Virtual Machine (VM) Windows Update Reset Tool
 
 **Applies to:** :heavy_check_mark: Windows VMs
 
 ## Overview
 
-This article covers steps to run a PowerShell script that resets the Windows servicing stack for a VM running in Azure. Running the tool can fix most problems that prevent Windows Updates from installing successfully. 
+This article covers steps to run a PowerShell script that resets the Windows Update servicing stack for a VM running in Azure. Running the tool can fix most problems that prevent Windows Updates from installing successfully. 
 
 > [!NOTE]
 > This article is intended for use with support agents and IT professionals. If you're a home user and looking for more information about fixing Windows update errors, see [Fix Windows Update errors](https://support.microsoft.com/help/10164).
@@ -31,7 +31,7 @@ This article covers steps to run a PowerShell script that resets the Windows ser
 - Restarts services.
 - Generates a summary of actions performed.
 
-For more information, see [Resetting Windows Update servicing stack script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_WUA_Update_Reset?).
+For more information, see [Azure VM Windows WUA Update Reset Tool](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_WUA_Update_Reset?).
 
 
 :::image type="content" source="media/windows-vm-wureset-tool/windows-vm-wureset-tool.png" alt-text="Azure portal view Run Command example." lightbox="media/windows-vm-wureset-tool/windows-vm-wureset-tool.png":::   
@@ -50,12 +50,12 @@ For more information, see [Run scripts in your Windows VM by using action run co
 
 ## Recommended workflow
 
-1. Run `Windows_Update_Reset` to reset the servicing stack.
+1. Run `Windows_Update_Reset` to reset the Windows Update servicing stack.
 2. Try to install the Windows Update that previously failed.
 
 ## Additional resources
 
-- [Resetting Window Update servicing stack script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_Update_Reset).
+- [Azure VM Windows WUA Update Reset Tool](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_Update_Reset).
 
 
 [!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]