The practical appeal is straightforward: makers get a baseline of operational visibility without wiring a separate monitoring implementation into each page.
What the roadmap promises—and what is available
Microsoft’s roadmap item 576282 lists September 2026 for preview and December 2026 for general availability, while retaining an In development status. It identifies the web platform, model-driven apps, admins or makers, and weekly release version 2608.5.
Those dates are planning targets, not a declaration that deployment is complete. Microsoft’s roadmap explicitly says release information is estimated and subject to change. Its Learn documentation still labels this telemetry capability as preview.
What Power Apps exports
Microsoft documents four activity categories:
| Activity | Application Insights table | Recorded information |
|---|---|---|
| Completed page loads | pageViews | Page identity, app, host type, load duration, and navigation origin |
| Unhandled errors | exceptions | Page-rendering errors and unhandled promise rejections |
| Supported Data API operations | dependencies | Duration and result for create, update, delete, retrieve, and query operations |
| Navigation from a generative page | pageViews | Source and destination page information |
Completed and supported are important boundaries. This is not a promise to capture every attempted load, handled error, or external request. Microsoft also cautions that preview features are not intended for production use.
The administrator prerequisites matter
“Out of the box” does not mean “without configuration.” Microsoft’s export guide limits the integration to Managed Environments and requires local authentication for the Application Insights integration. Setup needs a tenant-level Power Platform administrator or Dynamics 365 administrator role, plus an environment administrator or Dataverse system administrator role. Appropriate access to the destination Azure resource is also required.
The documented setup sequence is:
- Open the Power Platform admin center.
- Select Manage → Data export → App Insights → New data export.
- Name the export, choose the relevant data type and filters, and select the source environment.
- Select the Azure subscription, resource group, and Application Insights resource.
- Review the configuration and select Create.
Avoid pooling multiple environments into one destination without considering reporting consequences: Microsoft warns that its built-in reports will not work correctly with that arrangement.
Data should start exporting within 24 hours. If nothing appears afterward, Microsoft recommends checking setup permissions and the configured instrumentation key. GCC customers integrating with Application Insights in Azure Government are directed to submit a support request.
How to judge whether it is useful
Microsoft’s broader Power Platform integration stores exported telemetry in Azure Monitor logs. Application Insights provides Performance, Failures, and Logs views for investigating it, with additional event properties carried through customDimensions.
A sensible evaluation is to exercise a published page in a test environment, then inspect the exported records before designing dashboards or alerts. For example, compare a page-load record with the supported data-operation records generated while using that page. Treat this as a validation approach, not an assertion that every event shares identical correlation fields.
The analytical value is separating questions that otherwise become one vague support ticket: “Is the page slow?” and “Are its data operations slow?” Microsoft’s documented performance views support examining operation durations and dependencies, although an individual incident still requires investigation rather than guesswork dressed as a dashboard.
The bottom line: automatic telemetry should reduce instrumentation work, but validate coverage before depending on it. A useful baseline is not the same thing as complete application observability.