Power Platform Governance and Administration

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.

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

 Issue on dataareaID on generaljournalaccountentry entity (ynapse link for dataverse integration with FO

Issue observed while querying the generaljournalaccountentry table in Dataverse)

"Found that there is no field called dataareaID in the generaljournalaccountentry table"

MS Reference:https://portal.microsofticm.com/imp/v5/incidents/details/616139717/summary

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.

An "Unknown Error" was being thrown on a save button with SubmitForm(FormName). The issue was ultimately traced down to a corrupted Data Card on the form, yet the data card didn't show an error. This made debugging very difficult.

The data card should have shown an error

The error shouldn't have just been shown on the save button

Unknow error should be updated with a better error message that would help to identify the issue

Currently Microsoft's cloud carbon calculation methodology is limited to emissions associated with M365 products like Exchange Online, SharePoint, OneDrive etc. It would be great if Power Platform is also included in this methodology.

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.

Hello team,

At the moment, date & time format for exported Dataverse tables on Azure Synapse Link have 3 different formats for the following columns

• SinkCreatedOn & SinkModifiedOn | M/d/yyyy H:mm:ss tt
• CreatedOn | yyyy-MM-dd'T'HH:mm:ss.sssssssXXX
• All other datetime columns | yyyy-MM-dd'T'HH:mm:ss'Z'

This would cause date & time management for them hard to manage. Therefore, I'm creating this Idea in order to request to make all 3 formats to be consistent. Thank you for your help.

Information gathered from: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/export-data-lake-faq#what-date-and-time-formats-can-be-expected-in-exported-dataverse-tables

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.

Within a Power App, I should be able to add power automate workflows that have been saved in a solution. Currently I can only select saved flows if they are an instant flow that starts with a power apps trigger. I should be able to select flows that have any trigger.

Also, in Power Automate when I associate an App to the flow, it should automatically show up under the "Power Automate In your app" section within the app. but it does not.

While we're at it, if the app has a co-owner, it should automatically make them co-owners of the associated workflows / share the same permissions.