Power Platform Governance and Administration

Currently, if the log usage and file usage of an environment are displayed as zero in the Power Platform Admin Center, users are unable to export the respective usage data themselves.

As a result, users are unable to access the necessary information.

Adding this feature would greatly enhance user convenience.

In Power Platform, you can learn about events that have a significant operational impact through notifications in the message center and known issues. However, it is not possible to check all events through those services. Since some events may affect customers, there is a need for a tool to monitor incidents where functionality is not operating normally. We hope for the implementation of this feature.

Currently, there is a function to check the security score for the entire organization, but there is no function to check the security score for each environment group.

Being able to check the security score for each environment group will allow you to manage each environment more efficiently.

We would like to be able to receive email notifications without having to assign an admin role. Dynamics 365 will be more useful if this feature is implemented.

https://learn.microsoft.com/en-us/power-platform/admin/manage-email-notifications

The option to copy or clone an Power Platform environment with just its Dataverse database incl. all the data, but without all the Power Apps, Flows etc. would be a very helpful feature for data migrations.

Currently only a copy of the whole environment incl. everything or the customizations and schemas only is possible.

You know, there is a simple share button that users can use to give others access to the Copilot Agent. Easy thing and IT loves the simplicity (/sarcasm).

We’ve heard numerous concerns regarding sharing these Copilot Agents. Many organizations haven’t had enough time to understand what they are and how to govern them. So, my colleague took a long journey and went through all the options and did practical testing with several different type of user accounts in our Lab tenant.

We were surprised how many bits and pieces there was and it took several days go through all of them.

• Sharing the Copilot Studio Agent Builder agent in BizChat is simple and straightforward, but the agent's capabilities and sharing controls are limited.
• Sharing Copilot Studio extension for M365 Copilot has more capabilities, and different controls and settings are available.

Our urgent ask for Microsoft is a tool to monitor all different types of agents. We want to see what our users have created, how much they are used, and where the agents are connected.

Credits for this idea goes to my colleague Mikko K!

Current behavior : Search capability in PPAC flow list is limited to searching on the current page and it does not search on all the pages of flows. Users need to click 'Load more' options multiple times to get search result of flow list , making it most unsatisfying experience for users.

Expected behavior: User should be able to search the complete dataset in the first search itself. Searching on each page of flow list is the very time consuming and most unsatisfying experience.

The SharePoint document library is integrated onto main parent table. The quick view form is created on this main parent table. The related Documents subgrid id added onto the quick view form. The quick view form is added onto the related child table's main form.

The list of documents are displayed in Documents subgrid of quick view form on child table's main form, but unable to access/open the documents from the subgrid.

The response received from Microsoft Support team is as follows:

Embedding the document sub grid in a related entity quick view form and configuring the grid to access documents from its parent entity is currently unsupported.

It is nice feature to have it and it is may be useful for many users.

The 'Name of Record' record identifier (activity Id) matches the 'Invitation id'

If the Update action failed, because of Flow design work, it triggers mechanism of the Flow that cause the error. Basically, it will create a new record with the same id follows the upsert process as stated in the following documents.

And when a new record is upserted, due to having the same id as the previous invite record, this record will be detected as having duplicate key matching the ‘invitation id’ mentioned above.

Reference:

https://learn.microsoft.com/en-us/power-automate/dataverse/update

• https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-upsert-insert-update-record?tabs=webapi#understanding-the-upsert-process-for-standard-tables