Power Platform Governance and Administration

Currently, when importing a solution that includes duplicate detection rules, the option to overwrite customizations cannot be selected from the Power Apps Maker Portal. Instead, it is necessary to choose “Overwrite Customizations” from the traditional UI.

However, if the option to “Overwrite Customizations” could also be selected in the Power Apps Maker Portal, it would improve customer convenience and lead to increased productivity.

Please allow applications to be published without having to open the application in edit mode.

We recently ran into a problem which took us several weeks to resolve where we imported a managed solution into a powerapps environment. During the import the active managed layer created was not set as the published live layer, and so we had to go into the edit mode of the app to get to the button to publish the application. However by entering the edit mode we are creating a new unmanaged layer, entirely defeating the point of using a managed solution in the first place.

The initial need comes from the request to provide the dynamics app for outlook within the mobile outlook.

Currently it is not possible to scope a conditional access policy for a specific power app from a dynamics CRM instance. Caused by this we could only handle the whole power apps of a tenant in such a rule.

This is from security perspectives a poor approach.

We suggest it should be possible to create a conditional access policy for a specific power app (from a dynamics CRM). So that we can define the security more precisely.

Customer encountered an issue during the initial sync of tables for the Synapse link. As a workaround, we suggested removing the table from ASL and adding it back again. However, due to the large number of tables, we need an alternative solution to resolve this issue effectively.

Request:

Please assist us in finding a better way to address this problem.

Enable dynamic retrieval of IP lists and provide an improved interface for managing them. Currently, all IP addresses that need to be restricted must be entered into a small text box, which is inefficient. Additionnaly, the feature should allow for the inclusion of service tags for better organization and management.

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.

Current Dynamics 365 Excel export timeout has an internally hardcoded timeout of 12 minutes.

Because the 12 minute timeout is the default behavior, it is not possible to change the Excel export timeout value.

Therefore, we need the ability to increase the Dynamics 365 Excel export timeout limit.

With this implementation, the export limit will no longer time out at 12 minutes, allowing companies to work without worrying about the export limit and improving work efficiency.

Currently, we don't have the ability to restrict access to the Power Platform admin center.

By implementing this feature, you can improve the security of your users.

PowerPages is not approved for use at my organization and so we want to hide and disable it for all users.

I put in a support ticket to Microsoft, and the technician told me that by design, the PowerPages icon in the Office 365 app launcher at Office.com cannot be hidden.

There are definitely other organizations that wish to hide the PowerPages icon from the Office.com "All Apps" page.

It would be helpful if notifications are sent to admins when the environment has admin mode enabled, as it's a change that affect all non-admin users. It's also helpful in T2T, G2G migration scenarios where admin mode is automatically enabled after the move.