Power Platform Governance and Administration

Currently GUID is displaying under "Top Workflows by Failures" section. Instead, it should display the system job name.

Currently, if there are any in-progress solution imports, we get an error and cannot start another import. Instead, Users should have the option to import the solutions anytime without any failures and the solutions should be imported sequentially and asynchronously.

This will avoid failures in ADO pipeline automated deployments. Also, we don't have to set a maximum duration for solution import as even with the same solution, the import time varies in the same instance or different environments.

Currently, the admin should access each environment individually and apply the Version upgrade for each app. Admin should have option to synch and upgrade a D365 App to a single version across all environments in the tenant.

When using business rules, you can set Owning Business Unit based on a rule. However, it uses the GUID value, so when promoting to Test Or Production, the GUID is different, meaning the rule wont work. I imagine this is the same with any other lookup. Would it be possible to build in functionality to select name versus the GUID value for the lookup. Alternatively, you could provide the option to lookup an Alternate Key value instead of the built-in functionality. That way, we can make a business rule to set a field based on alternate key instead of primary key field. Advantage here is that alternate key is unique by design, so it should work across environments.

Thanks,

Matthew

The ability to restrict the viewing and creation of data and billing policies that can be created from the Power Platform admin center is not currently implemented.

Implementing this feature allows users to operate efficiently.

Currently, users require the System Admin role in order to modify elements of the Synapse Link to DataVerse (such as adding new tables to the export list for D365 F&O). This gives far reaching privileges well beyond the scope of Synapse Link to DataVerse. It would be beneficial from an IT governance stance if an additional role/privilege was added with specific permissions around managing this without giving wider access/permissions.

We have several environments that we would like to enable "Managed" but need to be able to imperially understand the effect on users currently access apps and artifacts in the environment before changing the setting. Currently, different users are licensed differently - some with per user premium licensing, others as part of E5, D365 addons, and others with standalone licenses - per app/per flow, etc.

The question is: Would switching the "Managed" setting to enabled which requires premium licensing, cause a loss of production access for any users? We need a tool to assess in real time the implications of changing that setting for individual envrionments.

Normally, only admins can go to Power Platform admin center to access all flows in an environment. However, there are scenarios which users need to handle all the flows. It is not feasible for system admin to share all flows and monitor new flows if there are too many flows in the environment.

Hence, there should be a security role which allows assigned user to have full access to flows in an environment without having to share the flows.

Hi!

Currently, the Team approvals are set in the Default environment. This causes issues with our users when they have to find the approvals. Please allow for users to be able to see the Team approval app in the source environment used and/or set the default to be their source environment.

Thanks!

Feasibility to add From from Email Activity in All My Activities View