Power Platform Governance and Administration

Currently, there is a known limitation in how virtual entities interact with Dataverse. The RetrieveTotalRecordCount function, which is used for native Dataverse entities, does not apply to virtual entities, leading to the total record count being set to -1 in the API response, which results in the display of 5000+.

Therefore, I would suggest that this function will support for virtual entities also so that the total number of records in subgrid view of virtual tables will reflect correctly.

Currently, Power Platform Admin Center does not offer an out-of-the-box capability to generate detailed API usage reports for non-licensed (non-interactive) users within a specific time window (e.g., a particular 24-hour period).

This limitation makes it difficult for administrators to:

• Troubleshoot throttling issues that may occur in short bursts
• Monitor or audit integrations using non-licensed accounts
• Align API usage to organizational compliance or SLA windows

We propose the introduction of a built-in report or API that would allow tenant admins to filter non-licensed user activity by user ID and time range (e.g., last 24 hours, past week).

This enhancement would significantly improve observability, governance, and operational readiness for large-scale or enterprise-grade environments.

There are two different reports that can be downloaded from PPAC regarding the Copilot Studio Message consumption. A tenant report and a environment report. The environment report contains a more detailed consumption per agent. I would like to have this data available in the tenant report as well. We have 1000+ environments and it is impossible to get a decent overview of the consumption per agent for each environment.

Dear Microsoft Team,

We would like to kindly request the implementation of a feature within the Dataverse platform that notifies users when a Power Automate flow fails to trigger, despite changes occurring in the underlying data.

Recently, we encountered an issue where certain flows did not trigger even though new records were created or updates were made in Dataverse. This lack of triggering resulted in delays and challenges in our automated processes, as we were not immediately aware that the flows had not executed as expected.

A built-in mechanism to alert users when a flow does not trigger—despite relevant data changes—would greatly enhance visibility and allow for quicker troubleshooting, thereby improving overall reliability and operational efficiency.

How can a user know that the flow is not triggered by the Microsoft backend due to failed callback registrations?

We appreciate your consideration of this request and look forward to any updates regarding its feasibility.

Thanks

Currently there is a supported way to update connector endpoint filters via powershell as documened in the following.

https://learn.microsoft.com/en-us/power-platform/admin/connector-endpoint-filtering#powershell-support-for-endpoint-filtering

Please consider creating a power automate connector that will allow admins to create power automate flows that can edit connector endpoint filters.

In Power Apps, security roles are a foundational part of how users interact with data, views, and forms. However, the current app development experience treats security roles as a separate, post-design configuration — which often leads to confusion, misaligned access, and unintended exposure of system views and forms.

I propose that security role planning be integrated as a mandatory step during app development, especially in model-driven apps. This could include:

• A guided step in the App Designer to define or assign security roles based on user personas
• Warnings or prompts when views/forms are included in the app but not properly secured
• A preview mode to test the app as a user with a specific role
• Better visibility into which roles can access which components of the app

This would help makers design apps that are secure, user-specific, and aligned with business requirements — without needing to troubleshoot access issues after deployment.

Why This Matters:

• Prevents users from seeing unintended system views/forms
• Reduces post-deployment issues and support tickets
• Encourages better alignment between app design and security
• Makes the platform more intuitive for citizen developers

Thank you for considering this improvement — it would make a big difference in building secure, role-aware apps from the start.

When searching for app and Flows in the resources section of the Environments, the list does not display all flows or apps in the view, I had to spend over 20 minutes clicking 'Load More' numerous times.

The search functionality only indexes flows that have already been loaded into view, similarly, sorting by “Modified” only applies to the currently displayed set of flows, rather than the full list. This behaviour is a considerable waste of time and effort, especially as I need to do this every time I'm looking for an app or flow.

Many I suggest loading at least the most recently modified apps and flows and possibly a 'Load All' option.