Merge pull request #10621 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-28 18:00 UTC

Author: learn-build-service-prod[bot]

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

@@ -8,7 +8,7 @@ tags: azure-resource-manager
 ms.service: azure-virtual-machines
 ms.tgt_pltfrm: vm
 ms.workload: infrastructure-services
-ms.date: 10/16/2025
+ms.date: 01/27/2026
 ms.author: jarrettr
 ms.reviewer: mbifeld
 ms.custom: sap:Cannot connect to my VM
@@ -46,6 +46,7 @@ Serial Console is available for virtual machines and virtual machine scale sets
 - China East 3
 - China North 2
 - China North 3
+- Denmark East
 - East Asia
 - East US 2 EUAP
 - East US 2

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

@@ -44,25 +44,13 @@ Set-ExecutionPolicy Bypass -Force
 (Invoke-WebRequest -Uri https://aka.ms/vmassist -OutFile vmassist.ps1) | .\vmassist.ps1
 ```
 
-Alternatively, you can specify the full URL instead of the aka.ms short link:
-
-```powershell
-(Invoke-WebRequest -Uri https://raw.githubusercontent.com//azure/azure-support-scripts/master/vmassist/windows/vmassist.ps1 -OutFile vmassist.ps1) | .\vmassist.ps1
-```
-
 ### Option 2: Manually download and run
 
 Download:
 
 ```powershell
 [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
-Invoke-WebRequest -Uri https://raw.githubusercontent.com//azure/azure-support-scripts/master/vmassist/windows/vmassist.ps1 -OutFile vmassist.ps1
-```
-
-Alternatively, you can specify the full URL instead of the aka.ms short link:
-
-```powershell
-Invoke-WebRequest -Uri https://raw.githubusercontent.com//azure/azure-support-scripts/master/vmassist/windows/vmassist.ps1 -OutFile vmassist.ps1
+Invoke-WebRequest -Uri https://aka.ms/vmassist -OutFile vmassist.ps1
 ```
 
 Run the script:
@@ -72,16 +60,6 @@ Set-ExecutionPolicy Bypass -Force
 .\vmassist.ps1
 ```
 
-### Option 3: Download from browser
-
- 1. Download the ```vmassist.ps1``` file [from a web browser](https://github.com//azure/azure-support-scripts/blob/master/vmassist/windows/vmassist.ps1).
- 1. In an elevated PowerShell window, make sure that you're in the same directory that you downloaded the script to, and then run the following code to run the script:
-
- ```powershell
-Set-ExecutionPolicy Bypass -Force
-.\vmassist.ps1
- ```
-
 ## Analyzing output
 
 The script runs a series of checks to analyze the health of the VM Guest Agent and look for various known configurations that could cause issues. Each check either passes or fails in the PowerShell window. 

support/docfx.json

@@ -72,6 +72,7 @@
         "dynamics-365/field-service/**.*": "MSDocsHeader-Dynamics365-Field-Service",
         "dynamics-365/sales/**.*": "MSDocsHeader-Dynamics365Sales",
         "mem/**.*": "MSDocsHeader-Intune",
+        "microsoft-edge/**.*": "MSDocsHeader-MSEdge",
         "power-platform/**.*": "MSDocsHeader-PowerPlatform",
         "power-platform/power-apps/**.*": "MSDocsHeader-MSPowerApps",
         "power-platform/power-automate/**.*": "MSDocsHeader-MSPowerAutomate",
@@ -157,7 +158,8 @@
         "dynamics-365/**/*.md": "aartig13",
         "dynamics/**/*.md": "aartig13",
         "power-platform/**/*.md": "aartig13",
-        "sales-copilot/**/*.md": "aartig13"
+        "sales-copilot/**/*.md": "aartig13",
+        "microsoft-edge/**/*.md": "aartig13"
       },
       "ms.collection": {
         "power-platform/ai-builder/**/*.md": "CEnSKM-ai-copilot",
@@ -186,7 +188,8 @@
         "dynamics-365/**/*.md": "aartigoyle",
         "dynamics/**/*.md": "aartigoyle",
         "power-platform/**/*.md": "aartigoyle",
-        "sales-copilot/**/*.md": "aartigoyle"
+        "sales-copilot/**/*.md": "aartigoyle",
+        "microsoft-edge/**/*.md": "aartigoyle"
       },
       "ms.reviewer": {
         "dynamics-365/supply-chain/costing/*.md": "yanansong",
@@ -249,6 +252,7 @@
         "microsoft-identity-manager/*.md": "microsoft-identity-manager",
         "dynamics/gp/*.md": "dynamics-gp",
         "mem/configmgr/**/*.md": "configuration-manager",
+        "microsoft-edge/**.*": "microsoft-edge",
         "system-center/**/*.md": "system-center",
         "windows/win32/**/*.md": "windows-dev-apps",
         "windows-hardware/drivers/**/*.md": "windows-hardware-driver-quality",
@@ -278,6 +282,7 @@
         "windows-365/**/*.md": "Windows 365",
         "mem/intune/**/*.md": "Intune",
         "mem/configmgr/**/*.md": "Configuration Manager",
+        "microsoft-edge/**.*": "Microsoft Edge",
         "system-center/dpm/**/*.md": "Data Protection Manager",
         "system-center/scom/**/*.md": "Operations Manager",
         "system-center/orchestrator/**/*.md": "Orchestrator",
@@ -343,6 +348,10 @@
           "ASP.NET",
           "ASP.NET Core"
         ],
+        "microsoft-edge/**.*": [
+          "Microsoft Edge", 
+          "Microsoft Edge Developer"
+        ],
         "sql/**/*.md": [
           "Troubleshoot",
           "sql"

support/entra/entra-id/app-integration/android-app-authentication-fails-after-published-to-google-play-store.md

@@ -9,6 +9,8 @@ ms.custom: sap:Developing or Registering apps with Microsoft identity platform
 
 # Authentication fails after an Android app is published to the Google Play Store
 
+## Summary
+
 This article provides a solution to an authentication failure that occurs during signing in after users install an Android app published to the Google Play Store.
 
 ## Symptoms

support/entra/entra-id/app-integration/app-doesnt-appear.md

@@ -11,7 +11,9 @@ content_well_notification: AI-contribution
 ai-usage: ai-assisted
 ms.custom: sap:Enterprise Applications
 ---
-# Application does not appear after clicking the add button
+# Application doesn't appear after clicking the add button
+
+## Summary
 
 The process of adding an application to Microsoft Entra ID may sometimes fail due to transient issues, networking problems, or a known issue. If you encounter an error when clicking the Add button, you’ll see a Notification in an Error state, which indicates that there was an error when creating the application. To learn more about the error or share it with a support engineer, you can follow the steps in [How to see the details of a portal notification](./send-notification-details.md).
 

support/entra/entra-id/app-integration/app-takes-long-time-appear.md

@@ -13,6 +13,8 @@ ms.custom: sap:Enterprise Applications
 ---
 # Application takes a long time to appear after clicking the "add" button
 
+## Summary
+
 If you experience a delay in the appearance of your application after clicking the "add" button, it is possible that it may take 1-2 minutes (and sometimes longer) for the application to appear in your directory. While this is not the expected performance, you can monitor the progress of the application addition by clicking on the Notifications icon (the bell) in the upper right corner of the Azure portal and looking for an In Progress or Completed notification labeled **Adding application**.
 
 If your application is not added or you encounter an error when clicking the Add button, you will see a Notification in an Error state. To obtain more information about the error and learn more or share with a support engineer, you can follow the steps in [How to see the details of a portal notification](./send-notification-details.md).

support/entra/entra-id/app-integration/application-delegated-permission-access-tokens-identity-platform.md

@@ -8,6 +8,8 @@ ms.custom: sap:App registrations
 ---
 # Application and delegated permissions for access tokens in the Microsoft identity platform
 
+## Summary
+
 This article introduces the differences between application and delegated permissions for access tokens in the Microsoft identity platform to help diagnose issues when applications call web APIs.
 
 ## Overview

support/entra/entra-id/app-integration/application-using-tls-1dot0-1dot1-authentication-fail.md

@@ -8,6 +8,8 @@ ms.custom: sap:Developing or Registering apps with Microsoft identity platform
 ---
 # Microsoft Entra applications using TLS 1.0/1.1 fail to authenticate
 
+## Summary
+
 This article provides solutions to authentication errors that occur with Microsoft Entra-integrated applications targeting versions earlier than Microsoft .NET Framework 4.7.
 
 ## Symptoms

support/entra/entra-id/app-integration/asp-dot-net-application-infinite-sign-in-loop.md

@@ -9,6 +9,8 @@ ms.custom: sap:Developing or Registering apps with Microsoft identity platform
 
 # Infinite sign-in loop between ASP.NET application and Microsoft Entra ID
 
+## Summary
+
 This article provides solutions to an issue where an ASP.NET application experiences an infinite redirect loop during signing in with Microsoft Entra ID.
 
 ## Symptoms

support/entra/entra-id/app-integration/asp-dot-net-open-web-interface-for-dot-net-core-authentication-sign-in-failures.md

@@ -8,6 +8,8 @@ ms.custom: sap:Developing or Registering apps with Microsoft identity platform
 ---
 # Troubleshoot ASP.NET OWIN and ASP.NET Core authentication sign-in failures with Microsoft Entra ID
 
+## Summary
+
 When you develop an ASP.NET Open Web Interface for .NET (OWIN) or ASP.NET Core Authentication web application and integrate it with Microsoft Entra ID, you encounter some issues during the sign-in process without any error messages or hint about what the problem might be. This article doesn't focus on direct solutions to sign-in failures but aims to help you expose hidden error messages that can guide you toward resolving the issue.
 
 > [!NOTE]