Power Platform Governance and Administration

After setting up an Azure Synapse link, we can view the Sync status of each table through the 'Azure Synapse Link' page.

If there is a failure to sync one of the tables, this is reported on the UI, but as far as I can see is not alerted elsewhere.

Access to this status programmatically, or via exposed logs, would be useful for holistic reporting in tooling external to the Powerapps dataverse.

In the admin center we have to options when copying across environments:

• everything - (application data + customization + schemas)
• Customization and schemas only

There should be a third entry to just copy applicational data if the mappings are compatible.

The task recorder for RSAT [Regression suite automation tool (RSAT) is only enabled in finance and HR. Ref: Task recorder resources - Finance & Operations | Dynamics 365 | Microsoft Docs

It has very good capabilities and saves a lot of effort in testing.

Request to please raise priority of this work in team's backlog to have this capability ready for Customer service modules.

Unable to remove the table from Modern advanced search without removing the table from the Model Driven App. This is a limitation and should be resolved, as we still need to keep the table in the Model Driven App and Navigation as well and just want to remove it from search.

In the modern UI old advanced find view, admin were able to download the fetch xml to use in multiple applications. Please provide a 'system admin' or 'system customizer' only button that allows us to download fetch xml easily from the views we know our users are refering to so that we can apply it in our other applications.

I can't fathom why nested groups are not supported. I need this functionality:

1. D365 groups created in AD, automatically, based on various critera.
2. D365 enviro groups created in AAD to include a few AAD service accounts.
3. D365 enviro groups contain the AD groups as needed.
4. D365 AAD security group assigned as enviro security group to allow users in.

I have to add users MANUALLY to the AAD group, even if they are in nested groups. Once they are in the D365 enviro, I can remove them from AAD and the nested users still work.

This is just crazy, and defeats the entire purpose of groups.

Please fix this ASAP. OR allow multiple security groups in D365 environments.

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.