Question
A company uses Power Automate extensively.
The company maintains the following three environments:
| Environment name | Dataverse enabled | Purpose |
|------------------|-------------------|---------|
| Environment1 | No | Used for a small task management application. Administrators of the environment must be able to view failed flow run details only. |
| Environment2 | Yes | Stores highly sensitive data that must not leave the geographical boundary. Auditing policies dictate that all activities must be stored for 90 days. Administrators need to receive automatic smart detection alerts. |
| Environment3 | Yes | Central environment for the company, used to store analytical data for all cloud flow runs across the tenant which then surface in a model-driven app. No flows execute in this environment. |
You need to recommend a monitoring solution for each environment. The solution must minimize development effort.
Which tools should you recommend? To answer, move the appropriate tools to the correct environments. You may use each tool once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Explanation
Environment1: Power Platform admin center — The Power Automate analytics in the Power Platform admin center include an Errors report that shows recurring flow errors with counts, the flow, its creator and the last occurrence. Environment admins can view it with no setup, and it does not depend on Dataverse, which this environment lacks; it covers exactly the need to view failed run details only.
Environment2: Application Insights — Cloud flow run, trigger and action telemetry can be exported from a managed, Dataverse-backed environment to an Application Insights resource through Data export in the admin center. You choose the Azure region of the resource, so the data stays inside the required geography, Application Insights retains data for 90 days by default, and it provides smart detection alerts that notify administrators of anomalies automatically.
Environment3: Power Automate Management connector — A central environment that runs no flows of its own needs to collect data about cloud flows in every environment in the tenant and store it in Dataverse for a model-driven app. The Power Automate Management connector (the approach the CoE Starter Kit uses) retrieves flows and their runs across environments and writes them into Dataverse tables, without custom code.
Microsoft Purview is not needed: it audits user and admin activity rather than monitoring flow run health or raising smart detection alerts.
