Power Platform Governance and Administration

We have observed in the new UI of D365 application the Business recommended field has been removed from the field property. I would request to not to remove such options as the end users would be interested to utilize this feature.

I understand that MS tried to improve it because for example security reasons but in fact this change means that more people need to get larger access that finally gives larger access also to other areas.

With the recent release of Commanding V2, and the ability to make ribbon buttons within PowerApps the use of PowerFX as Show/Hide rules and some onSelect commands looks very useful.

To ensure these can be widely used components within a Library need to be merged when multiple solutions are deployed which add layers to a single Model Driven Application.

At the moment an Application can only have one Component Library for new commands that use Power FX. So if multiple providers/solutions were to add buttons for an Application then these individual Components should all be added to the library as merge behaviour (Similar to formXML/Sitemap or Option Set currently)

Request to Reference Non-Primary Information from Primary Audit Logs

There are customer records A and A’, with A being the primary. When merging, only the information from A is adopted, and no integration event is recorded in A’s audit history. If the merge itself was an error or if you want to check A’s information, you will need to search for the inactive customer information, which becomes difficult over time. Without a merge log on the primary side, there is a risk of not realizing that an incorrect merge has occurred.

Therefore, We propose that a merge log be recorded on the primary side as well, allowing reference to the non-primary data.

Since Owner role access is the most powerful role in the subscription, in some situations, it is not ideally to assign it to a user.

Hence, we should have other roles to choose from instead of having to choose Owner role access.

In Power automate, we dont have any option to set the trigger condition based on related tables. Currently we have option only to set against the base table.

For existing flows, we have to add a block to check the conditions and if not met, cancelling the flows. With the option set in the trigger itself, a lot of cancelled runs and unneeded api calls can be avoided.

With the Power Platform and registering webhooks with the plugin registration tool we are given not many options for authentication. We are currently using the Authentication of “Webhook Key” as per the plugin registration tool. It does not satisfy the policy when turn on Authentication on the Function App.

This Function Apps need to compliant with CIS Microsoft Azure Foundations Benchmark 1.4.0. Part of that, for function apps is to satisfy the policy as defined in this link https://learn.microsoft.com/en-us/azure/governance/policy/samples/cis-azure-1-4-0#9-appservice, and this policy https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc75248c1-ea1d-4a9c-8fc9-29a6aabd5da8