Merge remote-tracking branch 'upstream/main' into AB#6970-Setting-up-a-Hyper-V-replica-between-Windows-Server-2016-and-Windows-Server-2022

Author: v-tappelgate

Outlook/Client/clienttoc/toc.yml

@@ -273,6 +273,8 @@
           href: ../performance/cannot-open-word-documents-or-excel-spreadsheets.md
         - name: Can't start Outlook in cached mode or create a profile
           href: ../performance/cannot-start-outlook-in-cached-mode-or-create-profile.md
+        - name: Collect performance and network traces
+          href: ../performance/collect-performance-trace.md
         - name: Crashes after installing language packs
           href: ../performance/outlook-2016-crash-event-1000.md
         - name: Error when you copy MSG email message files in Outlook containing multiple attachments or recipients

Outlook/Client/performance/collect-performance-trace.md

@@ -0,0 +1,43 @@
+---
+title: Collect a Performance Trace in New Outlook for Windows
+description: Provides guidance to collect performance and network traces in new Outlook for Windows.
+author: cloud-writer
+ms.author: meerak
+manager: dcscontentpm
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+  - sap:Errors, Crashes, and Performance
+  - Outlook for Windows
+  - CSSTroubleshoot
+ms.reviewer: caithart
+appliesto: 
+  - New Outlook for Windows
+search.appverid: MET150
+ms.date: 08/27/2025
+---
+# Collect a performance trace in new Outlook for Windows
+
+If you contact Microsoft Support to troubleshoot issues that affect new Outlook for Windows, you might be asked to collect a performance trace, a network trace or both. To collect these traces, use the Outlook icon in your system tray, and save the files to your local computer.
+
+The Outlook icon provides the following options to collect a trace.
+
+| Options | Description |
+|--|--|
+| Start Performance Trace | Start monitoring performance indicators, and continue until stopped manually.<br><br>After the trace collection starts, this option changes to **Stop Performance Tracing**. |
+| Record Perf Trace for 1 min | Monitor performance indicators for one minute, and then stop automatically.<br><br>This option might be useful to troubleshoot an unresponsive application to make sure that the trace is saved automatically. |
+| Start Network Trace | Start capturing network logs, and continue until stopped manually.<br><br>After the trace collection starts, this option changes to **Stop Network Tracing**. |
+
+To collect and access a trace, follow these steps:
+
+1. To start a trace, right-click the Outlook icon in the system tray, and then select the appropriate option.
+
+2. After you reproduce the issue, right-click the Outlook icon again, and then select the appropriate option to stop the trace.
+
+3. To access the trace files, open File Explorer, and then navigate to **%localappdata%\Microsoft\Olk\Feedback\Traces**.
+
+   The file name of a trace uses the following format: **WebviewTrace_\<TraceType_n_yyyymmdd_hhmmSSss>.json**
+
+   For example: **WebviewTrace_Performance_1_20250324_215740833.json**
+
+If you're on the phone with Microsoft Support, and you're asked to share the trace files, navigate to **Help** > **Get Diagnostics**, and then select the **Send diagnostics** button. Provide the displayed Support ID so that the Support agent can access the trace information that you collected.

support/azure/.openpublishing.redirection.azure.json

@@ -6373,6 +6373,10 @@
         {
         "source_path": "automation/runbooks/reinstall-oms-agent-linux.md",
         "redirect_url": "/troubleshoot/azure/automation/welcome-automation"
+      },
+        {
+        "source_path": "virtual-machines/windows/run-win-server-2003.md",
+        "redirect_url": "/troubleshoot/azure/virtual-machines/windows/ms-azure-windows-eos"
       }
   ]
 }

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md

@@ -4,7 +4,7 @@ description: Troubleshoot common issues with monitoring sync health and resolvin
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 07/24/2025
+ms.date: 08/25/2025
 ms.author: kendownie
 ms.custom: sap:File Sync, devx-track-azurepowershell
 ms.reviewer: v-weizhu, vritikanaik
@@ -754,8 +754,9 @@ Reset-AzStorageSyncServerCertificate -ResourceGroupName <string> -StorageSyncSer
 
 This error might occur due to the following reasons:
 
-- A new server certificate is generated on the Azure File Sync server, and the old certificate is still cached. This error will be resolved within a few hours once the server cache is refreshed.
-- The server endpoint deletion failed, leaving the endpoint in a partially deleted state. To resolve this issue, retry deleting the server endpoint.
+- The server’s managed identity tenant ID doesn't match the tenant ID of the Storage Sync Service or the storage account.
+- The server was recently re-registered or its managed identity configuration changed, but the update hasn't propagated yet.
+ 
 
 
 <a id="-1906441711"></a><a id="-2134375654"></a><a id="doesnt-have-enough-free-space"></a>**The volume where the server endpoint is located is low on disk space.**  

…-machines/windows/run-win-server-2003.md …machines/windows/ms-azure-windows-eos.mdsupport/azure/virtual-machines/windows/run-win-server-2003.md renamed to support/azure/virtual-machines/windows/ms-azure-windows-eos.md support/azure/virtual-machines/windows/run-win-server-2003.md renamed to support/azure/virtual-machines/windows/ms-azure-windows-eos.md

@@ -1,30 +1,43 @@
 ---
-title: Running Windows Server 2003 on Microsoft Azure
-description: Provides information about Windows Server 2003 support and answers some of the most common questions about running Windows Server 2003 on Microsoft Azure.
-ms.date: 07/21/2020
-ms.reviewer: 
+title: 'Windows Server EOS Timeline: Key Dates and Impact for Azure Virtual Machines'
+description: Provides information about Windows Server 2003 and later versions End of Support (EOS).
+ms.date: 08/26/2025
+ms.reviewer: v-liuamson 
 ms.service: azure-virtual-machines
 ms.collection: windows
 ms.custom: sap:VM Admin - Windows (Guest OS)
 ---
-# Running Windows Server 2003 on Microsoft Azure
+# Windows Server EOS timeline: Key dates and impact for Azure Virtual Machines
 
 **Applies to:** :heavy_check_mark: Windows VMs
 
 _Original KB number:_   4010166
 
-This article provides information about Windows Server 2003 support and answers some of the most common questions about running Windows Server 2003 on Microsoft Azure.  
+This article provides information about Windows Server support and answers some of the most common questions about around End of Support (EOS) for Azure Virtual Machines (VMs) running Windows Server operating systems.
 
-## Microsoft Windows Server 2003 end-of-support
+> [!IMPORTANT]
+> This article applies to Windows Server versions that have reached End of Support (EOS). Microsoft has officially ended support for the following operating systems:
+>
+> - Windows Server 2003
+> - Windows Server 2008/R2
+>
+>Machines running the above listed operating systems will no longer receive Microsoft support and may not receive further security updates. Additionally, many compliance requirements include being on a currently supported operating system.
 
-Microsoft ended extended support for Windows Server 2003 on July 14, 2015. If you are running Windows Server 2003, this may put your applications and business at risk, since there may be no security or software updates. You can still move a Windows Server 2003 VM to Azure, and receive assistance in troubleshooting issues that concern running Windows Server 2003 on Azure. However, this support is limited to issues that don't require OS-level troubleshooting or patch.
+Migrating your applications to Azure instances running a newer version of Windows Server is the recommended approach to ensure that you are effectively leveraging the flexibility and reliability of the Azure cloud. Pre-configured images with different combinations of Windows and SQL Server are available in the Marketplace and enable you to run any compatible solution on our cost-effective, high-performance, reliable cloud computing platform. For more information, see [Windows Server 2012 migration strategy](/windows-server/get-started/upgrade-migrate-roles-features).
 
-Machines running Windows 2003 will no longer receive Microsoft support and may not receive further security updates. Additionally, many compliance requirements include being on a currently supported operating system.
+## Microsoft Windows Server 2008/R2 End of Support (EOS)
 
-Migrating your applications to Azure instances running a newer version of Windows Server is the recommended approach to ensure that you are effectively leveraging the flexibility and reliability of the Azure cloud. Pre-configured images with different combinations of Windows and SQL Server are available in the Marketplace and enable you to run any compatible solution on our cost-effective, high-performance, reliable cloud computing platform. For more information, see [Windows Server 2003 migration strategy](https://www.microsoft.com/cloud-platform/windows-server-2003).
+Microsoft ended extended support for Windows Server 2008 and 2008 R2 on January 14, 2020, and Azure Extended Security Updates (ESU) support ended on January 9, 2024. Systems running these versions are no longer eligible for free security updates, non-security patches, or technical support. To maintain security and compliance, Microsoft recommends migrating workloads to newer Windows Server versions on Azure.
+
+## Microsoft Windows Server 2003 End of Support (EOS)
+
+Microsoft ended extended support for Windows Server 2003 on July 14, 2015. If you are running Windows Server 2003, this may put your applications and business at risk, since there may be no security or software updates. You can still move a Windows Server 2003 VM to Azure and receive assistance in troubleshooting issues that concern running Windows Server 2003 on Azure. However, this support is limited to issues that don't require OS-level troubleshooting or patch.
 
 ## Frequently asked questions
 
+> [!NOTE]
+>The information provided in this section is specific to Windows Server 2003.
+
 **When does extended support for Windows Server 2003 end?**
 
 Windows Server 2003 extended support ended on July 14, 2015.

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

@@ -1,3 +1,4 @@
+items:
 - name: Welcome
   href: welcome-virtual-machines-windows.yml
 
@@ -35,8 +36,8 @@
         href: /windows-server/get-started/extended-security-updates?context=/troubleshoot/azure/virtual-machines/windows/context/context
       - name: Upgrade Windows Server 2008/2008 R2
         href: /azure/virtual-machines/windows-in-place-upgrade?context=/troubleshoot/azure/virtual-machines/windows/context/context
-  - name: Windows 2003 Server
-    href: run-win-server-2003.md
+  - name: Windows Server 2003 and later versions End Of Support (EOS)
+    href: ms-azure-windows-eos.md
   - name: 32-bit operating systems
     href: support-32-bit-operating-systems-virtual-machines.md
   - name: Hybrid use benefit images are retired

support/power-platform/power-automate/toc.yml

@@ -288,6 +288,8 @@
       href: solutions/duplicate-binary-objects-in-schema-v2.md
 - name: Support resources
   items:
+    - name: Create an effective Power Automate support request
+      href: /power-automate/support-service-request
     - name: Power Automate support
       href: https://powerautomate.microsoft.com/support/
     - name: Power Automate Community forum

support/power-platform/power-automate/welcome-power-automate.yml

@@ -9,7 +9,7 @@ metadata:
   ms.topic: landing-page # Required
   author: aartig13 #Required; your GitHub user alias, with correct capitalization.
   ms.author: aartigoyle #Required; microsoft alias of author; optional team alias.
-  ms.date: 04/30/2025
+  ms.date: 08/28/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
@@ -85,6 +85,8 @@ landingContent:
     linkLists:
       - linkListType: reference
         links:
+          - text: Create an effective Power Automate support request
+            url: /power-automate/support-service-request
           - text: Power Automate support
             url: https://powerautomate.microsoft.com/support/
           - text: Power Automate Community forum

support/windows-client/toc.yml

@@ -745,8 +745,6 @@ items:
       href: ./setup-upgrade-and-drivers/dynamic-link-library.md
     - name: Error when you access a USB storage device
       href: ./setup-upgrade-and-drivers/error-when-you-access-usb-storage-device.md
-    - name: Error 0x800F0818 - 0x20003 Occurs during Upgrade from Windows 10 to Windows 11
-      href: ./setup-upgrade-and-drivers/error-0x800f0818-during-upgrade-to-windows-11.md
     - name: Event ID 219 when a device is plugged into a Windows system
       href: ./setup-upgrade-and-drivers/event-id-219-when-device-plugged-in-windows-system.md
     - name: Event ID 7000 or 7026 after starting a computer
@@ -807,6 +805,8 @@ items:
       href: ./setup-upgrade-and-drivers/iso-file-on-vlsc.md
     - name: Error 0x80042468 when creating a single partition
       href: ./setup-upgrade-and-drivers/error-when-creating-single-partition.md
+    - name: Error 0x800F0818 - 0x20003 during upgrade from Windows 10 to Windows 11
+      href: ./setup-upgrade-and-drivers/error-0x800f0818-during-upgrade-to-windows-11.md
     - name: Error 87 when a Windows 10 image is applied
       href: ./setup-upgrade-and-drivers/dism-error-87-apply-windows-10-image.md
     - name: Error "A fatal error occurred while trying to sysprep the machine"