Power Platform Governance and Administration

In the Power Platform admin center, if you want to remove users who have already been added, you need to delete the user accounts in the Microsoft 365 admin center. Therefore, you cannot delete or hide active users in the Microsoft 365 admin center. There are many scenarios where active users in the Microsoft 365 admin center are not being used in the environment. By implementing a feature to hide users in the Power Platform admin center, it will allow for better visibility of users utilizing the environment, making it clearer who the users of the environment are. I hope for the implementation of this feature.

As of January 17th, 2025, service notifications are sent to active members of the Dynamics 365 Administrator and Power Platform Administrator role. Previously, they were sent to users that were assigned the System Administrator role.

After engaging with MS support, we have been told that there are no other ways to receive these notifications. It also requires that the individual be elevated to the appropriate admin role to receive notifications. As we use PIM for all admin roles, this leaves us with no reliable way to receive these notifications.

We need some way to receive messages regarding service interruptions. Email would be sufficient, but locking it behind admin roles is a poor decision.

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

I recently received a Power Platform Environment expiration email to my company account, which wasn't for my company's tenant.

However, there's no reference to which tenant or organisation it is for, in the email.

Working for a company the provides Dynamics and Power Platform support, to many clients, I have accounts and Environments in many tenants, some of which have my company email as the contact email.

With no way to tell which tenant the email was for, I'm going to have to work through all the tenants I have access to, where the Environment name might match the account I use - In this case it's a Developer Environment so is using my name, so at least I can rule out service and generic admin accounts. But still...

It would be very useful if the Environment expiration email included some form of reference back to the tenant and/or organisation that it's relevant to.

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.

Current limit:

User cannot edit values for the Cross Tenant Server profile, only Location and Port can be changed. This is really inconvenient as values that need to be changed once in a while, like Client Secret, cannot be changed. Users would have to create a new Server Profile and go through the entire process one more time to get mailboxes working. No workarounds available

Suggestion:

Enabling all values of Cross Tenant server profiles to be editable would benefit users greatly

Benefits:

- As mentioned, convenience regarding values that need to be changed regularly

- Saves time on the process of having to re-activate mailboxes

- Provides general ease of access

We are using Deployment Pipelines to manage all our Power App and Workflows from Dev to Test to Prod. We use the Delegated Deployment option using a Service Principal account. This is to make sure all connections are workflows are shared to that account. This helps when you have multiple people working in the Power Platform and someone leaves the company. Their flows and power apps will still work. However, we discovered today that if a Solution includes some "Desktop Flows" and you are promoting it to a new environment, the deployment will fail. You will get an error

"ServicePrincipalShareNotSupportedInApi - Sharing connections with a service principal is not supported by the api."

This happens because under the connections section, we check the option to share connections with service principal account. This is required to ensure workflows will run correctly when deployed. This needs to be allowed with Desktop Flow Machine Group connections too.

My work around right now is to manually export the solution as zip as a managed solution. Then manually import it into the new environment. Once imported, you will be able to deploy updates to the solution with Pipelines once more.

Currently, we only have the option to download the summary of total File capacity consumption. We should also have the choice for the Admin to download the attachments stored in File capacity, which includes images, attachment in emails, etc to monitor the resource in the environment.

In Mid-January Microsoft rolled out something to Copilot Studio that was a bug which affected all agents in our Tenants.

after a few weeks of meetings we were finally informed that this was in fact a bug and they rolled out a fix.

We were reactive to this bug, rather than proactive and believe anything of this nature should be notifying all Admins of the issue, as well as the ETA on a fix.

I have several environments and managing them is easier with the sort option, The problem is that we do not have any option to save the order we want, and the page is not even capable to remember my last sort configuration.

This is a very basic feature and a must have

https://i.ibb.co/DftZrQzq/Screenshot-2025-02-03-003553.png