Merge remote-tracking branch 'upstream/main' into AB#8339-Troubleshooting-Windows-Multipath-IO-MPIO-and-Disk-Storage-Issues

Author: v-tappelgate

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/dynamics/gp/this-document-has-been-posted.md

@@ -55,16 +55,16 @@ To resolve this problem, use an SQL query tool to discover why the document is d
 5. Run the following script against the company database:
 
     ```sql
-    Select PSTGSTUS, BCHSOURC, VOIDSTTS,TRXSORCE, DEX_ROW_ID * from SOP10100 where SOPNUMBE = 'Enter your SOP Document number with issue'
+    Select PSTGSTUS, BCHSOURC, VOIDSTTS,TRXSORCE, DEX_ROW_ID, * from SOP10100 where SOPNUMBE = 'Enter your SOP Document number with issue'
     ```
 
 6. > [!NOTE]
    > The Dex_Row_ID value.
 7. Check values in the following columns for the SOP Document. If any of these values are incorrect, the document may appear as posted.
 
-    PSTGSTUS (For an unposted document, it should read "0.")  
-    BCHSOURC (For an unposted document, it should read "Sales Entry.")  
-    VOIDSTTS (For an unposted document, it should read "0.")  
+    PSTGSTUS (For an unposted document, it should read "0".)  
+    BCHSOURC (For an unposted document, it should read "Sales Entry".)  
+    VOIDSTTS (For an unposted document, it should read "0".)  
     TRXSORCE (For an unposted document, it should be blank.)
 8. Run the following scripts against the company database to correct any of the four values from step 6:
 

support/mem/configmgr/cloud-services/public-ip-creation-error.md

@@ -75,9 +75,7 @@ Current Configuration Manager releases don't specify Availability Zone when crea
 
 ## Resolution
 
-At this point, there's no confirmed impact from this behavior, so we recommend that you ignore these errors.
-
-Microsoft plans to resolve this problem in a future release of Microsoft Configuration Manager.
+Microsoft has released a hotfix to address this issue: [Cloud management gateway deployment maintenance update for Configuration Manager 2409, 2503](/intune/configmgr/hotfix/2503/35958849). [Configuration Manager 2509](/intune/configmgr/hotfix/2509/35877153) includes this hotfix.
 
 ## More information
 

support/mem/configmgr/setup-migrate-backup-recovery/understand-troubleshoot-updates-servicing.md

@@ -86,7 +86,7 @@ For reference, the following table lists well-known update package GUIDs. The li
 | Configuration Manager 2403 HFRU | A02D38C5-021E-4144-8249-E7CDE48DA83F|
 | Configuration Manager 2409 | 3B7D84FA-ECCC-4EA0-B8AB-ABBDA1E88E0E |
 | Configuration Manager 2409 HFRU | 345A6BE1-3D07-43ED-B6E5-FAC0889DA04C |
-| Configuration Manager 2503 | 8576527E-DDE9-4146-8ED9-DB91091C38EF|
+| Configuration Manager 2503 | AA928926-5C76-4DE0-B51F-0FE4D365DFE2 |
 | Configuration Manager 2503 HFRU | 6B0783D9-B8A2-4848-82F6-8EFE956F4988|
 
 ### Identify the installation stage of the update

support/power-platform/power-automate/desktop-flows/browser-automation/failed-to-assume-control-of-edge-chrome-firefox-error.md

@@ -0,0 +1,25 @@
+---
+title: Workarounds for SAP GuiTree Capture Issues in Power Automate for desktop
+description: Learn how to resolve issues with capturing SAP GuiTree objects in Power Automate for desktop. Explore UI automation and SAP GUI scripting as workarounds.
+ms.reviewer: iomimtso, ststavri, v-shaywood
+ms.custom: sap:Desktop flows\SAP automation
+ms.date: 11/18/2025
+---
+
+# Can't capture SAP GuiTree objects
+
+Currently, Power Automate for desktop doesn't support capturing SAP GuiTree objects. Support for capturing SAP GuiTree objects is planned for a future release. Until this feature is available, you can use one of the workarounds in this article if your desktop flow must interact with these controls.
+
+## Symptoms
+
+Power Automate for desktop doesn't capture SAP GuiTree objects when you use SAP automation actions.
+
+## Workaround 1: Use UI automation
+
+Use [UI automation actions](/power-automate/desktop-flows/actions-reference/uiautomation) to interact with the controls. Capture the controls by using the UI element picker. Then, use UI automation actions in your desktop flow.
+
+## Workaround 2: Use SAP GUI scripting
+
+Use SAP GUI scripting to automate controls that the SAP automation actions don't capture. For the configuration steps, see [Configure SAP GUI scripting](/power-automate/guidance/rpa-sap-playbook/vbscript-based-sap-gui-automation-overview).
+
+[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]

support/power-platform/power-automate/desktop-flows/sap-automation/cannot-capture-guitree-objects.md

@@ -0,0 +1,35 @@
+---
+title: Handle Authentication Popup When Starting SAP
+description: Learn how to handle SAP authentication popups in Power Automate for desktop for smooth SAP automation.
+ms.reviewer: iomimtso, ststavri, nimoutzo, v-shaywood
+ms.custom: sap:Desktop flows\SAP automation
+ms.date: 11/19/2025
+---
+# Authentication popup appears when starting SAP
+
+This article helps you resolve an issue in which an authentication popup appears when you use the **Launch SAP** action in Microsoft Power Automate for desktop.
+
+## Symptoms
+
+When you run the [Launch SAP](/power-automate/desktop-flows/actions-reference/sap#saplogin) action by using your logon credentials, an authentication popup window appears unexpectedly. This issue causes the action to fail and prevents other SAP actions from running.
+
+## Workaround
+
+To handle the authentication popup, use [UI automation actions](/power-automate/desktop-flows/actions-reference/uiautomation) instead of the **Launch SAP** action. Follow these steps:
+
+1. Use the **Run application** action to start the SAP GUI application.
+1. Use UI automation actions to interact with the authentication popup:
+   1. Use the **Populate text field in window** action to enter credentials.
+   1. Use the **Click UI element in window** action to submit the credentials.
+1. After you handle the popup, use the **Attach** action to attach the SAP GUI application to the active SAP instance.
+1. After the SAP instance is attached, you can run any other SAP actions.
+
+ :::image type="content" source="media/handle-authentication-popup-launch-sap/authentication-popup-appears-when-launching-sap.png" alt-text="Power Automate for desktop workflow with Run application, UI automation actions to handle authentication popup, and Attach to running SAP actions.":::
+
+## More information
+
+- [UI automation actions](/power-automate/desktop-flows/actions-reference/uiautomation)
+- [SAP automation actions](/power-automate/desktop-flows/actions-reference/sap)
+- [Introduction to SAP GUI–based RPA in Power Automate Desktop](/power-automate/guidance/rpa-sap-playbook/introduction)
+
+[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]

support/power-platform/power-automate/desktop-flows/sap-automation/handle-authentication-popup-launch-sap.md

@@ -1,22 +1,34 @@
 ---
-title: Troubleshoot UI Element Visibility Issues in Power Automate for Desktop
-description: Troubleshoot Power Automate for desktop when it can't interact with specific UI elements. Explore solutions like OCR, image actions, and more.
-ms.date: 11/05/2025
+title: Troubleshoot UI Automation and Element Detection in Power Automate for Desktop
+description: Troubleshoot UI automation issues in Power Automate for desktop. Learn how to fix problems with the element picker or recorder not detecting UI elements.
+ms.date: 12/02/2025
 ms.custom: sap:Desktop flows\UI or browser automation
 ms.reviewer: iomimtso, nimoutzo, v-shaywood
+ms.author: iomimtso
 ---
 
-# UI element picker or recorder can't view UI elements in desktop applications
+# UI automation fails and element picker or recorder can't see UI elements
 
-This article provides troubleshooting guidance for an issue where Power Automate for desktop can't view or interact with specific UI elements in a desktop application.
+This article provides troubleshooting guidance for issues where Power Automate for desktop can't view or interact with specific UI elements in a desktop application.
 
 ## Symptoms
 
-When using Power Automate for desktop, the element picker tool can't detect or "see" certain UI elements within desktop applications. This issue prevents you from selecting elements for automation tasks.
+When you try to use UI automation in Power Automate for desktop, you might experience the following issues:
 
-## Cause
+- _During design time_: The element picker or recorder doesn't show any UI elements when you try to capture elements for automation.
+- _During runtime_: UI automation actions fail to execute correctly in both attended and unattended desktop flow runs.
 
-Some desktop applications use custom UI frameworks or rendering methods that aren't compatible with the standard accessibility APIs that Power Automate for desktop relies on. This incompatibility can make certain elements invisible to the element picker.
+## Cause 1: Interfering background processes
+
+Some background processes interfere with UI automation functionality in Power Automate for desktop. Specifically, the **Microsoft Accessory Center** or **DesktopBridge** processes prevent UI automation from working correctly.
+
+### Solution: Terminate interfering processes
+
+To resolve this issue, terminate the interfering processes and disable them from running in the future.
+
+## Cause 2: Incompatible UI frameworks
+
+Some desktop applications use custom UI frameworks or rendering methods that aren't compatible with the standard accessibility APIs that Power Automate for desktop relies on. This incompatibility makes certain elements invisible to the element picker.
 
 > [!IMPORTANT]
 > For coordinate-based solutions (Solutions [3](#solution-3-use-the-recorder-with-coordinates) and [4](#solution-4-use-move-mouse-and-send-mouse-click-actions)) to work reliably:
@@ -25,7 +37,7 @@ Some desktop applications use custom UI frameworks or rendering methods that are
 > - Changes to the application's user interface structure might affect the effectiveness of these workarounds.
 > - Test your flows thoroughly when deploying to different machines or environments.
 
-## Solution 1: Use Move mouse to image action
+### Solution 1: Use Move mouse to image action
 
 1. Add a **Move mouse to image** action to your flow.
 1. Capture an image of the UI element you want to interact with.
@@ -34,7 +46,7 @@ Some desktop applications use custom UI frameworks or rendering methods that are
 
 This action moves the mouse to the first occurrence of the specified image and sends a left click.
 
-## Solution 2: Use Move mouse to text on screen (OCR) action
+### Solution 2: Use Move mouse to text on screen (OCR) action
 
 1. Add a **Move mouse to text on screen (OCR)** action to your flow.
 1. Specify the text that appears on or near the UI element you want to interact with.
@@ -43,7 +55,7 @@ This action moves the mouse to the first occurrence of the specified image and s
 
 This action uses Optical Character Recognition (OCR) to locate text on the screen or foreground window and sends a mouse click to that location.
 
-## Solution 3: Use the recorder with coordinates
+### Solution 3: Use the recorder with coordinates
 
 1. Open Power Automate for desktop and create a new flow.
 1. Select **Recorder** from the toolbar.
@@ -52,7 +64,7 @@ This action uses Optical Character Recognition (OCR) to locate text on the scree
 
 The recorder creates a **Click UI element in window** action with coordinate-based input parameters populated by using the respective values from your click action.
 
-## Solution 4: Use Move mouse and Send mouse click actions
+### Solution 4: Use Move mouse and Send mouse click actions
 
 1. Add a **Move mouse** action to your flow.
 1. Configure the action to move the mouse to the specific coordinates of the target element.

support/power-platform/power-automate/desktop-flows/sap-automation/media/handle-authentication-popup-launch-sap/authentication-popup-appears-when-launching-sap.png

@@ -0,0 +1,33 @@
+---
+title: Troubleshoot CyberArk Connection Failures for RDP Automation
+description: Troubleshoot CyberArk connection failures for RDP automation in Power Automate. Find solutions to ensure seamless remote desktop connections.
+ms.reviewer: iomimtso, iopanag, v-shaywood
+ms.custom: sap:Desktop flows\UI or browser automation
+ms.date: 11/20/2025
+---
+# RDP automation fails to connect to a machine through CyberArk
+
+This article helps you resolve an issue in which you can't connect to a machine through CyberArk when you use Remote Desktop Protocol (RDP) automation in Microsoft Power Automate for desktop.
+
+## Symptoms
+
+When you execute an RDP automation and it attempts to connect to a machine through CyberArk, the Power Automate agent for virtual desktops doesn't establish communication with Power Automate for desktop, and you receive the following error message:
+
+> A device attached to the system is not functioning.
+
+:::image type="content" source="media/cyberark-connection-not-supported/rdp-connection-failed.png" alt-text="The error message that you receive when you try to connect through CyberArk.":::
+
+However, when you connect directly to the machine by using RDP without CyberArk, the connection works as expected, and Power Automate for desktop successfully communicates with the agent.
+
+## Cause
+
+CyberArk creates a nested remote connection path. This condition interferes with the agent-to-desktop communication that's required for UI and browser automation. Power Automate for desktop doesn't support nested remote connections.
+
+## Solution
+
+To resolve this issue:
+
+- Use a direct RDP connection to the target machine instead of connecting through CyberArk.
+- Make sure that the Power Automate agent for virtual desktops is running and correctly registered on the machine.
+
+[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]