Power Platform Governance and Administration

In the PPAC, when going to resources > flows for a large environment, not all flows are displayed. Please fix this so admins can easily reassign flows when needed rather than having to go through powershell.

Reference: TrackingID#2504070040013814

https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-management/manage-orphan-flow-when-owner-leaves-org#assign-new-co-owners-to-an-orphaned-flow

It is not "hard" to find orphaned flows, it is currently not possible.

Microsoft can deploy new fields on Dataverse Tables at any time, and can do it in Production-type environments before Sandbox-type environments. These unexpected changes in data model can generate issues on applications (having their own constraints) that consume Dataverse.

The suggestion is:

• To have visibility in advance on fields deployed by Microsoft in Dataverse
• That Microsoft always deploys new fields in Sandbox-type environments before Production-type environments

While Power Apps allows table selection and editing, it is inefficient for handling large volumes of records (querying, updating, deleting). Although SSMS can execute SQL on Dataverse tables, it currently does not support updates or deletions.

Dataverse Capacity should have more information about the information of each table. Especially for ActivityPointerBase and AuditBase.

These tables can be retrieved some data by running SQL query or accessing via WebAPI. However, it would be more helpful if the Dataverse capacity report could provide more information about storage with filters by column values of each table.

In Power Platform, you can learn about events that have a significant operational impact through notifications in the message center and known issues. However, it is not possible to check all events through those services. Since some events may affect customers, there is a need for a tool to monitor incidents where functionality is not operating normally. We hope for the implementation of this feature.

In Azure Synapse Link for Dataverse, Tables of Dataverse are being synchronized to CSV files. We face issues when the data model of a Table changes.

Indeed, when a new column is added in a Table, only the new or updated records have the new column in the CSV file. Existing records do not have the new column in the CSV file.

Then, all lines in the CSV file don't have the same number of columns, which is not standard and makes the CSV file not readable by many tools and languages. The only solution to fix the CSV file is to remove the concerned Table from the synchronisation, and add it again.

This is also a bigger issue because Microsoft can deploy new fields on a Table at any time, and can do it in Production-type environments before Sandbox-type environments.

Then, we face unpredictable issues in the CSV files in Azure Synapse Link, that we can solve only after they happened, even in Production.

The idea is the following: when a new column in added in a Table synchronized in Azure Synapse Link: all records in the CSV file should be updated to use the new column, in order to have a standard CSV file accepted by all tools and languages.

Currently, the audit logs provided through the Microsoft Purview Portal for Dynamics 365 CRM only record the fact that a user accessed an entity, but do not capture or expose the specific Entity ID (Record ID) of the record that was viewed.

This is a significant limitation for organisations needing to maintain a strong security posture. In the event of a suspected data breach, it is currently impossible to reconstruct exactly which CRM records were accessed by a user based on standard Purview audit data. This weakens incident response capabilities and limits compliance with data protection regulations such as GDPR, HIPAA, and others, where organisations are expected to provide detailed information on data access.

Proposed Feature:

Enhance CRM audit logging in Purview to include the Entity ID (record GUID) for all access events (Read/View). This data should be available both in the Purview Portal investigation and reporting.

Business Impact:

• Improves ability to monitor and investigate unauthorised access events
• Enables full auditability and traceability of CRM data
• Helps organisations meet regulatory and compliance obligations
• Reduces security risk and strengthens trust in the Dynamics platform

Example Scenario:

If a CRM user views a sensitive customer record (e.g., a lead or a case), the audit log should record not just that the entity type "Lead" or "Case" was accessed, but also the specific Entity ID (e.g., caseid=ABC12345-6789-4DEF-0123-456789ABCDEF).

This would allow organisations to identify precisely which customer's data was viewed, enabling accurate breach reporting and remediation.

Currently, Dynamics 365 primarily supports logging through Application Insights, which limits flexibility for customers who have invested in other enterprise logging and monitoring solutions. I would like to request native support for integrating the standard .NET ILogger interface with alternative logging providers beyond Application Insights.

This enhancement would allow developers to centralize logs across services within their existing observability infrastructure, improving diagnostics, operational consistency, and maintainability.

Currently, there is no centralized dashboard available to track audit log settings and retention periods across environments in Power Platform. This creates a visibility gap for administrators who need to monitor and manage data governance effectively.

We’ve observed the following:

• Audit logs can have their retention period set to "forever", which may lead to excessive Dataverse storage usage if not regularly monitored.
• At present, admins must manually access each environment’s settings to review audit log status and retention configuration.
• There is no consolidated view to track Dataverse audit log usage, retention periods, or potential overuse risks.

We propose a feature enhancement to include a dashboard in the Power Platform Admin Center that provides:

• A summary view of audit log status and retention periods for each environment.
• Alerts or indicators for environments with indefinite retention settings.
• Usage statistics showing how much Dataverse space is consumed by audit logs.
• Add two new actions(get audit settings and update audit settings) in the PowerPlatformforAdmins connector.

This would enable admins to take proactive measures for capacity planning and ensure compliance with internal data retention policies.

Thank you for considering this request.

Power App Grid control to support Business rule logic and lookup prefiltering