Merge remote-tracking branch 'upstream/main' into AB#8098-new-Zero-Trust-DNS-

Author: v-tappelgate

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

@@ -93,6 +93,12 @@ items:
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Error Code 0x800f0831
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-installation-error.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error code 0x80244007
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80244007.md?context=/troubleshoot/azure/virtual-machines/windows/context/context   
+    - name: Error code 0x80072f8f
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80072f8f.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error code 0x8000ffff
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x8000ffff.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
 
 - name: Uploading a VHD to Azure
   items:
@@ -272,6 +278,28 @@ items:
 
 - name: Instant Metadata Service (IMDS)
   items:
+  - name: In-place system upgrade for Windows Server Azure VMs
+    href: /azure/virtual-machines/windows-in-place-upgrade?context=/troubleshoot/azure/virtual-machines/windows/context/context
+  - name: In-place system upgrade for Windows-based Azure VMs
+    href: in-place-system-upgrade.md
+  - name: Upgrade VM to contain more than 64 vCPUs
+    href: vm-cannot-upgrade-64-vcpu.md
+  - name: Windows Update errors that require in-place upgrades
+    href: windows-update-errors-requiring-in-place-upgrade.md
+  - name: Known errors and issues
+    items:
+    - name: Error code 0x80070002
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070002.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error code 0x8024002E
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-code-0x8024002e.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error code 0x80070490
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070490.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error 0x8007000d after installing Windows updates
+      href: ../../../windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error Code 0x800f0831
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-installation-error-corruption.md
+    - name: Error Code 0x8007045b
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md
   - name: Overview
     href: /azure/virtual-machines/instance-metadata-service?context=/troubleshoot/azure/virtual-machines/windows/context/context
   - name: Certificate Issues

support/azure/virtual-machines/windows/windows-activation-troubleshoot-tools.md

@@ -27,7 +27,7 @@ Validates the activation status of your Windows VM and checks for common issues
   - Detects misconfigurations.
   - Provides actionable guidance.
 
-For more information, see [Windows activation validation](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/WindowsActivationValidation/README.md).
+For more information, see [Windows activation validation](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_Activation_Validation).
 
 ### 2. Azure Instance Metadata Service certificate check
 
@@ -44,7 +44,7 @@ Verifies the integrity and availability of certificates that are required for ac
 For more information, see: 
 
 - [Cause: Azure Instance Metadata Service connection issue](activation-watermark-appears.md#cause-1-azure-instance-metadata-service-connection-issue).
-- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/IMDSCertCheck/README.md).
+- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_IMDSValidation).
 
 ## How to run these tools
 

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

@@ -28,8 +28,8 @@ When an Azure Virtual Machine running Windows Server or Windows Client with **Ac
 **Purpose**  
 There two scripts that can be used to detect if there are 'ghosted nics' inside of the VM. A VM that has one ore more could experience issues.This script detects ghosted (disconnected) network interface cards (NICs) and remove them from the registry.
 
-- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 
 
@@ -41,8 +41,8 @@ There two scripts that can be used to detect if there are 'ghosted nics' inside
 For more information, see: 
 
 - [Troubleshooting: Multiple Mellanox Ethernet Adapters After VM Deallocation (Ghost NICs)](./windows-vm-ghostednic-troubleshooting.md)
-- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 ## How to run the tools
 
@@ -63,7 +63,7 @@ Download the scripts from GitHub, and then run them manually. To access the scri
 - Navigate to your VM in the Azure portal: > **Operations** > **Run Command**.
 - Select the script from the list (see the following screenshot).
 
-**Only the [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning) is available in this method. The other script can be run via the Run Command prepackeged method.**
+**Only the [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection) is available in this method. The other script can be run via the Run Command prepackeged method.**
 
 :::image type="content" source="media/windows-vm-ghostednic-tool/windows-vm-ghostednicvalidationtool-portal-runcmd.png" alt-text="Azure portal view Run Command example." lightbox="media/windows-vm-ghostednic-tool/windows-vm-ghostednicvalidationtool-portal-runcmd.png":::   
 
@@ -76,14 +76,14 @@ For more information, see [Run scripts in your Windows VM by using action Run Co
 
 ## Recommended workflow
 
-1. Run **[Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)** to verify activation status and detect common issues.
-2. If ghost-nics are detected, run [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time) to remove them.
+1. Run **[Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)** to verify activation status and detect common issues.
+2. If ghost-nics are detected, run [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal) to remove them.
 
 ### **Additional resources**
 
 - [Troubleshooting: Multiple Mellanox Ethernet Adapters After VM Deallocation (Ghost NICs)](./windows-vm-ghostednic-troubleshooting.md)
-- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 [!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
 

support/azure/virtual-machines/windows/windows-vm-ghostednic-troubleshooting.md

@@ -75,7 +75,7 @@ This behavior is **by design** due to the architecture of Accelerated Networking
 
 ### **1. Detect the Scenario**
 Use **RunCommand** to check for ghosted NICs:  
-[Ghosted NIC Check Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
+[Ghosted NIC Check Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows_GhostedNIC_Detection)
 
 ### **2. Clean Up Ghosted NICs**
 
@@ -84,8 +84,8 @@ Use **RunCommand** to check for ghosted NICs:
 
 **Option B: Force Removal via RunCommand**
 - Use RunCommands to check then remove ghosted NICs:  
-  - [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-  - [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+  - [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+  - [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 
 ### **3. Plan for Design Behavior**

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

@@ -37,7 +37,7 @@ Certificate not found: 'CN=Microsoft Azure XXXX, ...'
 For more information, see: 
 
 - [Cause: Azure Instance Metadata Service connection issue](activation-watermark-appears.md#cause-1-azure-instance-metadata-service-connection-issue).
-- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/IMDSCertCheck/README.md).
+- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_IMDSValidation).
 
 ## How to run the tool
 

support/developer/visualstudio/installation/toc.yml

@@ -58,6 +58,8 @@
     href: ./version-visual-studio-requires-april-2014-update.md
   - name: Wait for setup to finish before trying again
     href: ./another-setup-already-running-wait-finish.md
+  - name: Workarounds for Visual Studio on unsupported operating systems
+    href: ./visual-studio-unsupported-operating-systems.md
   - name: Workarounds for Visual Studio 2022 on unsupported operating systems
     href: ./visual-studio-2022-unsupported-operating-systems.md
   - name: Windows Program Compatibility mode is on

support/developer/visualstudio/installation/visual-studio-unsupported-operating-systems.md

@@ -0,0 +1,76 @@
+---
+title: Workarounds for Visual Studio on Unsupported Operating Systems
+description: This article describes known issues and workarounds for Visual Studio if it's installed on unsupported operating systems.
+ms.date: 11/11/2025
+ms.reviewer: pchapman, jagbal, v-shaywood
+ms.custom: sap:Installation\Setup, maintenance, or uninstall
+---
+# Workarounds and operating system requirements for Visual Studio
+
+_Applies to:_   Visual Studio  
+
+## Summary
+
+Microsoft Visual Studio is supported on only 64-bit editions of [Windows 11](/lifecycle/products/?terms=windows%2011), [Windows 10](/lifecycle/products/?terms=windows%2010), and Windows Server 2019 and later versions that are still within their support lifecycle. We recommend that you don't run Visual Studio on earlier or unsupported versions of Windows and Windows Server. For more information, see [full system requirements](/visualstudio/releases/vs18/vs-system-requirements). To enable organizations to schedule their operating system upgrades, this article provides known issues and potential workarounds when you use Visual Studio on an unsupported operating system.
+
+> [!NOTE]
+> Microsoft can't provide support or fixes for issues that occur if you use Visual Studio on an unsupported operating system. For feedback on supported configurations, see [Developer Community](https://developercommunity.visualstudio.com/).
+
+## Arm-based operating systems
+
+Arm64 Visual Studio is supported on only Windows 11 on Arm. 64-bit Visual Studio isn't supported on ARM operating systems. Therefore, the performance of that setup might not meet your expectations.
+
+The following workloads and components aren't supported by Arm64 Visual Studio running on ARM64 operating systems:
+
+- Azure development (except for the Container development tools that are supported)
+- Data storage and processing (except for the SQL Server Data Tools that are supported)
+- Data science and analytical applications
+- Python development
+- Mobile development with C++
+- Office/SharePoint development
+- Microsoft Blend
+- XAML Designer (runs in an x86 process on ARM64)
+
+## Windows LTSC
+
+The Windows Long-term Servicing channel (LTSC) isn't intended for deployment on most devices in an organization. Use it only for special-purpose devices. Visual Studio isn't intended to run on [the Windows Long-term Servicing Channel (LTSC)](/windows/deployment/update/waas-overview#long-term-servicing-channel). However, building apps that run on Windows LTSC is supported.
+
+## Application Virtualization
+
+Visual Studio doesn't support Application Virtualization (App-V) solutions. For example, Microsoft App-V for Windows or third-party app virtualization technologies isn't supported by Visual Studio.
+
+## Azure Virtual Desktops
+
+Running Visual Studio in a virtual machine (VM) environment requires a full Windows operating system. Visual Studio doesn't support multiple simultaneous users using the software on the same computer, including shared virtual desktop infrastructure computers or a pooled Windows Virtual Desktop host pool.
+
+## Windows containers
+
+Running Visual Studio Community, Professional, Enterprise, or Team Explorer editions in Windows containers isn't supported. The Build Tools edition is supported.
+
+## 32-bit operating systems
+
+Visual Studio doesn't install on 32-bit operating systems.
+
+## Windows 7 and Windows Server 2008 R2
+
+Visual Studio doesn't install on Windows 7 and Windows Server 2008 R2.
+
+## Windows 8 and Windows Server 2012
+
+Visual Studio doesn't install on Windows 8 and Windows Server 2012.
+
+## Windows 8.1 and Windows Server 2012 R2
+
+Visual Studio doesn't install on Windows 8.1 and Windows Server 2012 R2.
+
+## Windows 10, versions 1507 and 1511
+
+Visual Studio doesn't install on Windows 10, versions 1507 or 1511.
+
+## Windows 10, versions 1607 through 1903
+
+.NET 4.8.1 doesn't install and isn't supported on Windows 10, versions 1607 through 1903.
+
+## Windows 10, versions 1909 through 2004
+
+.NET 4.8.1 doesn't install and isn't supported on Windows 10, versions 1909 through 2004.

support/mem/intune/app-management/troubleshoot-google-apps.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot Managed Google Play apps on Intune-managed devices
 description: Troubleshoot common issues with Managed Google Play for Android Enterprise devices enrolled in Microsoft Intune.
-ms.date: 02/11/2025
+ms.date: 11/07/2025
 search.appverid: MET150
 ms.reviewer: kaushika, v-six, esalter
 ms.custom: sap:AppDeployment - Android\ManagedGooglePlay
@@ -36,8 +36,32 @@ This is expected behavior. Only system apps installed in the Work Profile are in
 
 See the blog post [Best practices for updating your Android Enterprise apps](https://techcommunity.microsoft.com/t5/intune-customer-success/best-practices-for-updating-your-android-enterprise-apps/ba-p/3038520) to learn about best practices and options for configuring app updates for your corporate-owned devices. This includes using network preferences, maintenance windows, and high-priority update mode Which bypasses all regular constraints so you can apply and update as fast as possible.
 
-### I want to stay updated on any Google service issues that may cause impact
+## I want to stay updated on any Google service issues that may cause impact
 
 Google releases [service announcements](https://www.androidenterprise.community/t5/service-announcements/tkb-p/Announcements) containing details about issues that may impact Android Enterprise management. Follow the [instructions to subscribe](https://www.androidenterprise.community/t5/news-info/new-community-board-subscribe-to-the-new-service-announcements/ba-p/1044) and receive notifications for new posts.
 
+## Newly approved Managed Google Play apps don't appear in the Play Store
+
+<!-- 33632857 -->
+
+When you approve a Managed Google Play app, it might not appear in the Play Store for users. This behavior occurs when your tenant is in Custom mode.
+
+Custom mode is enabled automatically when you edit collections in the Managed Google Play iFrame. In this mode, newly approved apps remain hidden until you manually add them to a collection.
+
+To resolve the issue, use one of the following options:
+
+- **Add the app to a collection:** In the Managed Google Play iFrame, add the app to an existing or new collection.
+- **Reset the Play Store layout to Basic:**  
+  1. In the Intune admin center, go to **Apps** > **All apps** > **Create Managed Google Play app**.  
+  2. Select **Reset to Basic**.  
+  3. Confirm the action.
+
+> [!IMPORTANT]
+> Resetting to Basic deletes all existing collections. After the reset, all approved apps become visible in the Play Store automatically. Any future changes to collections switch the store back to Custom mode.
+
+Allow a few minutes for the change to propagate. If the reset fails, retry and confirm that you have the correct permissions. If the issue continues, capture the error details and contact Microsoft Support.
+
+For more information, see [Add Managed Google Play apps to Android Enterprise devices with Intune](/mem/intune/apps/apps-add-android-for-work).
+
+
 [!INCLUDE [Third-party disclaimer](../../../includes/third-party-contact-disclaimer.md)]