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.

Current behavior:

The D365 Sandbox environment backup restore has retention period of 7 days and for production environment it is 28 days.

Ask:

Request to increase the retention period of backup restore of D365 environments.

Sandbox environments from 7 days to 30 days and production environments from 28 days to 60 days.

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.

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.

Currently, Power Platform Advisor provides automated recommendations with predefined severity levels (e.g., High, Medium, Low). However, there is no option for tenant admins to adjust the severity based on contextual relevance or business impact.

For example, recommendations related to license mismatches or app ownership may be marked as "High" by default, even if they pose minimal operational risk in our environment. This can lead to unnecessary escalations or misprioritization of admin efforts. I

There should be a feature in Power Platform Admin Center that allows tenant admins to:

• Override the default severity of recommendations.
• Provide justification or notes for the override.
• Track overridden recommendations separately for audit and governance purposes.

This would empower organizations to tailor the recommendation system to their unique operational context and improve the efficiency of issue triage and resolution.

when a record is deleted, the associated Business Process Flow records are permanently deleted, not sent to the recycle bin.

This behavior has caused significant challenges for our data restoration efforts. We believe this is a defect that should be addressed to support proper restoration functionality.

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.