Merge pull request #10298 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit 321f5d6bf249 · 2025-12-04T18:03:23.000Z
Auto Publish – main to live - 2025-12-04 18:00 UTC
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/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
