Power Platform Governance and Administration

When I decide to link my Dataverse tables to Fabric, I cannot choose which tables will be transferred. It would be great if I could choose only specific tables.

Format time of Modern Date picker is different with Time Setting in Modern Driven App. Date picker field from custom page should be followed CRM Setting.

Example, if we are living in Australia, where we are using dd/mm/yyyy time format, we can change in CRM setting to dd/mm/yyyy, but Date picker from custom page should show as dd/mm/yyyy, not mm/dd/yyyy as US time format.

The idea is specifically related to article:

https://learn.microsoft.com/en-us/power-platform/alm/form-alm

(1) It would be great to prevent the unhealthy scenario mentioned in the article. i.e., "it is not a healthy ALM practice to create multiple managed solutions from the development environment where the base solution (Solution A) is in an unmanaged state". A preventive mechanism should be in place to prevent a form to be added to an unmanaged solution if it is already included in another unmanaged solution within the same environment.

(2) The steps described in "Creating a new form and maintaining it using multiple managed solutions" is not a pragmatic solution, as it requires a separate environment to be setup/available just to make sure a change involves removing a field from a form will work in target environment.

A more robust solution without involving another environment would have been more practical.

Currently Dataverse and Model-driven app audit data for the tenant's Default environment is not available via the M365 Security and Compliance center (data accessed via these instructions - Microsoft Dataverse and model-driven apps activity logging - Power Platform | Microsoft Docs). This is a gap particularly in that there are activities that default to this environment and users generally have more ability to perform actions in this environment. It also leads to inconsistencies in being able to locate audit records and requires our audit and compliance team to have additional access into this via PPAC. We would like to see this information be included along with the data gathered from additional environments.

Based on the documentation here: https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tools#create-service-principal-and-client-secret-using-powershell, the support engineer and myself conclude that the service principal created has full admin rights on the tenant.

[quote] "This PowerShell script helps creating and configuring the service principal to be used with the Microsoft Power Platform Build Tools tasks. It first registers an Application object and corresponding Service Principal Name (SPN) in AAD.

This application is then added as an administrator user to the Microsoft Power Platform tenant itself."

Since our company is both and ISV partner and a customer, the internal IT department will not provide such as service user. That user (for development/testing purposes) will also be able to administrate (and delete!) environments we're using for production purposes.

Hi team,

Please help create a button so we can export environment name and information in the environment page

I would like to be able to specify a default Document Location when multiple Document Locations exist for a record.

Security requirements require that Document Locations be separated, but if the default Document Location cannot be specified, it is meaningless and may lead to user error.

Currently, it is not possible to extract what operations are generating requests in the Power Platform Request Report.

If we can extract what operations are generating supply, we can avoid generating unnecessary requests.