Merge remote-tracking branch 'upstream/main' into AB#7765-Failure-in-Windows-Update-on-host-systems-in-a-virtual-machine-cluster

v-tappelgate · v-tappelgate · commit 676e254bfd8f · 2025-12-04T10:04:53.000-08:00
diff --git a/Microsoft365/purview/purview/retention/identify-errors-in-retention-and-retention-label-policies.md b/Microsoft365/purview/purview/retention/identify-errors-in-retention-and-retention-label-policies.md
@@ -8,11 +8,12 @@ ms.reviewer: kyrachurney, lindabr, meerak
 ms.custom: 
   - sap:Retention
   - CI 171536
+  - CI 8323
   - CSSTroubleshoot
 appliesto: 
   - Microsoft Purview
 search.appverid: MET150
-ms.date: 05/05/2025
+ms.date: 12/03/2025
 ---
 
 # Identify errors in Microsoft 365 retention and retention label policies
@@ -79,15 +80,15 @@ Use the following steps to check for errors in policies that target:
 
 1. [Connect to Security & Compliance PowerShell](/powershell/exchange/connect-to-scc-powershell).
 
-2. Get policy information by using the [Get-AppRetentionCompliancePolicy cmdlet](/powershell/module/exchange/get-appretentioncompliancepolicy). Run the following commands:
+1. Get policy information by using the [Get-AppRetentionCompliancePolicy cmdlet](/powershell/module/exchange/get-appretentioncompliancepolicy). Run the following commands:
 
    ```powershell
    Get-AppRetentionCompliancePolicy -Identity "<policy name>" -DistributionDetail | FL DistributionStatus
    Get-AppRetentionCompliancePolicy -Identity "<policy name>" -DistributionDetail | Select -ExpandProperty DistributionResults
    ```
 
-   If there are policy errors, the value returned by the `DistributionResults` property contains more information about the errors.
-
+   If there are policy errors, the value returned by the `DistributionResults` property contains more information about the errors. Check for the value returned by the `DistributionResults` property only when the `DistributionStatus` property returns error messages as its value. You must resolve the errors. However, if the `DistributionStatus` property returns warning messages, you can ignore them. 
+   
 ## Recommended practices
 
 To minimize retention policy errors, follow these practices:
diff --git a/Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md b/Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md
@@ -22,7 +22,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 11/20/2025
+ms.date: 12/03/2025
 ---
 # Known issues with Teams Rooms on Windows
 
@@ -39,6 +39,8 @@ ms.date: 11/20/2025
 |Unable to join some Webex meetings|When you select the **Join** button to join a Cisco Webex meeting from a Teams Rooms on Windows device, you're not connected to the meeting and see the home screen on the device instead.|No workaround is available at this time. Cisco is investigating the issue.|
 |Automatic remediation in Pro Management portal keeps failing.|The built-in remediation in the Microsoft Teams Rooms Pro Management portal to disable the USB peripheral power draining option under Windows USB settings keeps failing with the error message:<br/><br/>`Auto Remediation was unable to resolve this issue.`|To resolve the issue, implement a manual fix as described in [USB Peripheral Power Drain signal is unhealthy](./usb-peripheral-power-drain-status-unhealthy.md).|
 |Lenovo Teams Rooms devices display BitLocker recovery screen.|When you try to update Windows from 23H2 to 24H2 on a Lenovo Teams Rooms for Windows device that has BitLocker enabled, the update might fail and you see a BitLocker recovery screen instead.|The Windows update to 24H2 on Lenovo devices is [blocked](https://support.microsoft.com/topic/kb5070632-some-devices-are-temporarily-unable-to-upgrade-to-windows-11-version-24h2-or-25h2-c3dd7515-21e6-46ce-9a9d-64a8882ef5ca) due to this issue. <br/><br/>You can safely upgrade the versions of the Teams Rooms app to 5.3.205.0 and 5.4.210.0 on the affected devices that will remain on Windows version 23H2. <br/><br/>If one of these versions of the Teams Rooms app is already installed and the device displays the BitLocker recovery screen, enter the BitLocker recovery key to restore functionality.|
+|Video participants missing from Front row.|The Front row view doesn't show all the video participants, and they're missing from the overflow area as well.<br/><br/>The Front row view displays a maximum of five attendees on a single screen, and up to nine attendees on a dual screen. When the maximum number of attendees are already shown on the screen, the extra attendees are represented in the overflow view area. However, when two or more participants turn on their cameras, the remaining video streams might not fit in the Front-of-Room display, and they are not accounted for in the overflow area as well. This issue causes those video participants to appear as "missing" from the meeting.|Use a different meeting view than the Front row view.|
+|All video streams turn off on Front row during a meeting.|When you use the Front row view on a Teams Rooms on Windows device, all video streams including the meeting room's video and incoming content turn off in the Front-of-Room display. This issue occurs intermittently when a remote participant turns off their video while content is being shared.|Leave and rejoin the Teams meeting from the Teams Rooms device.|
 
 ## Hardware issues
 
diff --git a/support/azure/app-service/create-delete-resources-faq.yml b/support/azure/app-service/create-delete-resources-faq.yml
@@ -3,11 +3,11 @@ metadata:
   title: FAQ about creating or deleting web apps in Azure App Service
   description: Common questions and answers about creating or deleting Resources in Azure App Service
   services: active-directory
-  author: auolivei
-  ms.reviewer: amehrot, rimarr, jarrettr, v-ryanberg
+  author: JarrettRenshaw
+  ms.reviewer: amehrot, rimarr, jarrettr
   ms.topic: faq
-  ms.date: 06/21/2022
-  ms.author: auolivei
+  ms.date: 11/24/2025
+  ms.author: jarrettr
   ms.service: azure-app-service
   ms.custom: sap:Configuration and Management
 title: Frequently asked questions about creating or deleting resources in Azure App Service
diff --git a/support/azure/partner-solutions/dynatrace/free-trial-errors.md b/support/azure/partner-solutions/dynatrace/free-trial-errors.md
@@ -0,0 +1,45 @@
+---
+title: Dynatrace Free Trial Limitations on Azure
+description: Understand the limitations of Dynatrace free trial resources on Azure.
+author: agrimayadav
+ms.author: jarrettr 
+ms.reviewer: v-ryanberg
+manager: dcscontentpm
+ms.service: partner-services 
+ms.topic: troubleshooting-problem-resolution
+ms.date: 09/23/2025
+ai-usage: ai-assisted
+# customer intent: As an Azure administrator or user, I want to understand the limitations of using a Dynatrace free trial on Azure so that I can work around them and/or prepare for resource deletions.
+
+---
+
+# Free trial limitations
+
+This article helps you understand limitations that you might encounter when creating or managing Dynatrace free trial resources on Azure, including resource creation limits and resource deletion after trial expiration.
+ 
+## Symptoms
+
+- You get an error when attempting to create another Dynatrace free trial resource.
+- The Dynatrace free trial resource is missing or deleted after the trial period ends.
+
+## Cause
+
+- You can only create one Dynatrace resource during the trial period.
+- With the free trial plan, your Dynatrace resource on Azure will be deleted automatically after the trial expires unless you request an extension.
+
+## Solution 1: Unable to create another free trial resource
+
+Only one environment or resource can be created during the trial period. If you need additional environments, upgrade to a paid Dynatrace plan or wait until the trial expires and start a new trial (if eligible).
+
+## Solution 2: Prepare for automatic free trial resource deletion
+
+Be aware that free trial resources are deleted automatically after the trial period ends. If you require more time, [contact Dynatrace sales](mailto:sales@dynatrace.com) to request a trial extension or discuss upgrade options.
+
+## Resources
+
+- [Dynatrace free trial documentation](https://www.dynatrace.com/trial/resources/)
+- [Contact Dynatrace sales](mailto:sales@dynatrace.com)
+
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/partner-solutions/dynatrace/metrics-checkbox-disabled.md b/support/azure/partner-solutions/dynatrace/metrics-checkbox-disabled.md
@@ -0,0 +1,49 @@
+---
+title: Metrics Collection Checkbox for Dynatrace Is Unavailable  
+description: Resolve the issue in which the metrics collection checkbox is unavailable because the user lacks Owner permissions on the subscription.
+author: agrimayadav
+ms.author: jarrettr
+ms.reviewer: v-ryanberg
+manager: dcscontentpm
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution
+ms.date: 09/22/2025
+ai-usage: ai-assisted
+
+# customer intent: As an Azure administrator or user, I want to enable the Metrics checkbox so that I can enable metrics collection for Dynatrace.
+
+---
+
+# Metrics collection checkbox is unavailable 
+
+This article helps you resolve the issue where the **Enable metrics collection** checkbox is unavailable in your Dynatrace integration because the signed-in account doesn't have [Owner role permissions](/azure/role-based-access-control/built-in-roles#owner) on the Azure subscription.
+
+## Prerequisites
+
+- Access to the [Azure portal](https://portal.azure.com/) and the subscription that contains the resource.
+
+## Symptoms
+
+- The **Enable metrics collection** checkbox is unavailable (grayed out) in the Dynatrace integration UI.
+- Attempting to enable metrics collection results in an error or no action.
+
+## Cause
+
+Enabling metrics collection requires Owner role permissions at the subscription scope. Users with Contributor or Reader role permissions can't enable metrics collection from the integration UI and the checkbox is unavailable.
+
+## Solution: Request Owner role permission
+
+1. In the Azure portal, go to the subscription that contains the resource.
+2. Select **Access control (IAM)**.
+3. Select **View my access** to see your current role at the subscription scope.
+
+If you don't have Owner role permissions, contact the subscription Owner or admin and request Owner role permissions or ask them to enable metrics collection for you. After the Owner or admin assigns the role, wait 5–15 minutes for role-based access control (RBAC) propagation and then retry enabling metrics collection in the Dynatrace integration.
+
+## Resource
+
+- [Azure role-based access control (RBAC)](/azure/role-based-access-control/)
+- [Assign Azure roles using the Azure CLI](/azure/role-based-access-control/role-assignments-cli)
+
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/partner-solutions/index.yml b/support/azure/partner-solutions/index.yml
@@ -49,6 +49,16 @@ landingContent:
           - text: Single sign-on doesn't work for the Confluent SaaS portal
             url: confluent/single-sign-on-does-not-work.md   
 
+# Card
+  - title: Dynatrace 
+    linkLists:
+      - linkListType: how-to-guide
+        links:
+          - text: Free trial limitations
+            url: dynatrace/free-trial-errors.md
+          - text: Metrics collection checkbox is unavailable 
+            url: dynatrace/metrics-checkbox-disabled.md
+
 # Card
   - title: Astro 
     linkLists:
diff --git a/support/azure/partner-solutions/toc.yml b/support/azure/partner-solutions/toc.yml
@@ -55,10 +55,14 @@ items:
       href: diagnostic-settings-manual-update.md
     - name: Diagnostic settings not created
       href: diagnostic-settings.md
+    - name: Free trial limitations
+      href: dynatrace/free-trial-errors.md
     - name: Log forwarding persists
       href: log-forwarding-persists.md
     - name: Log limitations
       href: log-limitations.md
+    - name: Metrics checkbox is unavailable
+      href: dynatrace/metrics-checkbox-disabled.md
 - name: Elastic
   items:
     - name: Diagnostic settings manual update
diff --git a/support/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling.md b/support/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling.md
@@ -134,7 +134,7 @@ To fix the issue, use one of the following methods:
 - If MFA is **Enabled** or **Enforced**:
     - Set MFA to **Disabled**. For more information, see [Turn off legacy per-user MFA](/microsoft-365/admin/security-and-compliance/set-up-multi-factor-authentication#turn-off-legacy-per-user-mfa).
     - Bypass MFA by using [Trusted IPs](/azure/active-directory/authentication/howto-mfa-mfasettings#trusted-ips).
-- If Microsoft Entra Conditional Access policies are used, exclude the Microsoft Intune app from the policies that require MFA to allow device sync by using the user credentials.
+- If Microsoft Entra Conditional Access policies are used, exclude the Microsoft Intune app (AppID 0000000a-0000-0000-c000-000000000000) from the policies that require MFA to allow device sync by using the user credentials.
 
 <a name='a-hybrid-azure-ad-joined-windows-10-device-fails-to-enroll-in-intune-with-error-0x800706d9-or-0x80180023'></a>
 
diff --git a/support/power-platform/power-automate/desktop-flows/ui-automation/wrong-ui-element-clicked-populated.md b/support/power-platform/power-automate/desktop-flows/ui-automation/wrong-ui-element-clicked-populated.md
@@ -0,0 +1,46 @@
+---
+title: Troubleshoot Incorrect UI Element Clicked or Populated in Desktop Flow
+description: Resolve issues in Power Automate of desktop targeting the wrong UI element during automation. Learn how to ensure accurate clicks and text population.
+ms.reviewer: iomimtso, nimoutzo, v-shaywood
+ms.date: 11/26/2025
+ms.custom: sap:Desktop flows\UI or browser automation
+---
+# Wrong UI element is clicked or populated in desktop flow
+
+This article resolves an issue in which Power Automate for desktop interacts with the wrong UI element instead of the element that you captured during flow design. This issue occurs even though the [Test Selector](/power-automate/desktop-flows/test-selectors) tool detects the right element.
+
+## Symptoms
+
+When you run a desktop flow that includes UI automation actions such as [Click UI element in window](/power-automate/desktop-flows/actions-reference/uiautomation#click) or [Populate text field in window](/power-automate/desktop-flows/actions-reference/uiautomation#populatetextfield), the flow interacts with a different UI element than the one that you originally captured.
+
+You might observe the following symptoms:
+
+- The action runs without errors but targets an unexpected element.
+- The wrong element receives the click or text input during runtime.
+- The [Test Selector](/power-automate/desktop-flows/test-selectors) tool successfully identifies the correct element during design time.
+
+## Cause
+
+This issue occurs because the target application handles focus, enable, or disable events in an unexpected way. Some applications dynamically change element focus or states. This functionality can cause UI automation actions to interact with the wrong element.
+
+## Solution
+
+To resolve this issue, use a combination of UI automation and mouse and keyboard actions to ensure proper element targeting. Use one of the following methods based on whether you have to click or populate text.
+
+### Click an element by using hover and mouse click
+
+Instead of using the [Click UI element in window](/power-automate/desktop-flows/actions-reference/uiautomation#click) action, follow these steps:
+
+1. Add a [Hover mouse over UI element in window](/power-automate/desktop-flows/actions-reference/uiautomation#hoveronelement) action, and select the target UI element.
+1. Add a [Send mouse click](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#sendmouseclick) action, placed immediately after the hover action, to click the element.
+
+To prevent focus-related issues, this approach makes sure that the element receives focus through the hover action before the click is sent.
+
+### Populate a text field by using focus and send keys
+
+Instead of using the [Populate text field in window](/power-automate/desktop-flows/actions-reference/uiautomation#populatetextfield) action, follow these steps:
+
+1. Add a [Focus text field in window](/power-automate/desktop-flows/actions-reference/uiautomation#focustextfield) action, and select the target text field.
+1. Add a [Send keys](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#sendkeys) action to input the desired text.
+
+To make sure that text is entered in the intended field, this approach explicitly sets the focus to the correct text field before the keystrokes are sent.
diff --git a/support/power-platform/power-automate/toc.yml b/support/power-platform/power-automate/toc.yml
@@ -113,6 +113,8 @@ items:
             href: desktop-flows/ui-automation/element-picker-cant-see-elements.md
           - name: UIPI issues with UI and web automation actions
             href: desktop-flows/ui-automation/uipi-issues.md
+          - name: Wrong UI element is clicked or populated in desktop flow
+            href: desktop-flows/ui-automation/wrong-ui-element-clicked-populated.md
       - name: '"Could not read the application certificate" error when creating a connection'
         href: desktop-flows/application-certificate-error.md
       - name: Agent-related errors when running attended or unattended desktop flows
diff --git a/support/windows-client/installing-updates-features-roles/error-0x8007000e-0x800705aa-insufficient-virtual-memory.md b/support/windows-client/installing-updates-features-roles/error-0x8007000e-0x800705aa-insufficient-virtual-memory.md
