Power Platform Governance and Administration

When working in development in the Dataverse I find that I'm working with/on a table consistency and every time I have to go back to the Tables list and find the table again (unless I open it in a separate tab and REMEMBER to not go off that page but to use "open in a new tab").

Why not add one more tab to the current list of Recommended, Custom, All, called Recent and show a list of tables recently worked on?

Is there an easy way to copy/move these audit logs and files to Azure Blob storage instead of deleting them or purchasing add-on storage capacity?

Currently Import is either on for all tables or off for all tables for a security role. There are many reasons why you would not want to have end users importing data into tables that they have permissions to create/read/write/delete - chiefly to keep the end users from creating problems with inappropriate data (i.e account where there are many that have the same name but may be in different states or countries or have different account numbers and the end user isn't skilled at altering their import to utilize different lookups, etc.). Our only recourse today is to turn off import for all but administrators however there are some tables that would be ok for the end user to import to (i.e. contact, lead) but without the granularity in the security we can't.

Use record-based security to control access to records (Developer Guide for Dynamics 365 Customer Engagement) | Microsoft Docs

Based on the current design, when the user was assigned share access for this record, he can remove and modify other user's privileges on this record.

For example,

user A and Team A assigned all access for a record. Later user A can modify and evenly remove Team A all access.

We need to limit this right, which when a user was assigned share access, he can only modify himself or he has shared the user.

We have export to datalake which can export tables and entities.

This service is transitioning into Synapse Link for Dynamics.

The fact that it will be entity driven is worrying:

1/ we don’t have (fast) entities for every table in finops (not even for standard ERP tables)

2/ existing entities contain far more tables than the ones needed in datalake (best example customerv3)

cfr. also https://experience.dynamics.com/ideas/idea/?ideaid=5444118e-6c79-ec11-b820-0003ff45920b

A workaround would be to fake entities mapping all fields in the table at runtime… (platform wise)

While adding existing entities to a solution we may need to add bulk of entities (i.e. 30 entities) including alll the assets related to each entity, that means that we have to mark the checkbox "Add All Assets" 30 times for the 30 entities.

It would be great if there's a checkbox to include all assets for all of the selected entities.

Please add AsyncOperation as an input for the PowerPlatformPublishCustomizations task similar to the PowerPlatformImportSolution task. Currently, a timeout error is returned if a response from Dynamics is not received within the time limit after executing the PowerPlatformPublishCustomizations task. This makes it look like the task has failed, but it is just the response that failed within the allowed time.

Please update activity tracking so that is does not stop when I go to another browser window. Right now the time tracker only works when I'm in Dynamics, but often, I need to go outside of dynamics (into excel or building a presentation) while I'm working on customer deliverables. It's really frustrating to work on something for 3 hours, to only have Dynamics track the 5 minutes I spent finding the ticket and posting my work.

We need the ability to switch Azure Active Directories from the Microsoft Power Platform admin center. This will allow our clients to invite our current user accounts into their directory, and not create separate logins in their directory. This type of functionality already exists in the Azure and Partner portals.

It would be great whether business rules could handle the following scenarios:

• The ability to check on fields from parent table while defining a condition
• The ability to set field value with a value from parent table