Power Platform Governance and Administration

When a PowerApps managed application is installed from appsource in a customer's tenant, the solution remains uneditable and protected.

But when in dataverse (in the customer's tenant where the managed solution has been installed), an unmanaged solution is created and the managed application installed from appsource is included in this solution, then the managed solution becomes editable and all the code is accessible.

At this point, the solution can be exported and duplicated, losing the intellectual property protection.

From the point of view of an ISV developer, it is necessary that the managed application always remains protected, not being editable or exportable.

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.

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

To improve the readability of highlighted text, it would be beneficial to add a highlight field option to the Personalization settings. This would allow agents to choose or remove colors, ensuring the text remains readable by customizing the color in the personalization settings. Currently, this option is only available at the Organization level by modifying the OptionSet.

Upon verification, we confirmed that connections from Outlook are counted as active users in the Power Platform's Management Center analysis reports.

(Verification Summary)

The verification shows that if you have applications such as Copilot for Sales or Dynamics 365 App for Outlook installed in Outlook, you will appear as an active user only when accessing from Outlook.

(Proposal)

In its current state, it counts connections from Outlook as well, making it impossible to accurately determine Dynamics utilization.

We believe that by counting only connections purely from Dyanmics, it would be possible to see the utilization of Dynamics only, which would be useful for client management.

• virtual entities only work with the highlighted options on the connection:
• Azure AD integrated
• SQL server authentication
• windows authentication
• service principale
• The windows ones are for On Premises , so that leaves us with AD integrated and SQL Server Authentication.

so we can conclude that using the clientID/secret doesn't work with Virtual entities for cloud environments.

the connection can be created but cannot be choosen when creating the entity.And on changing from the inside it doesn't connect and returns null data.

would like to be able to select the created ClientID/Secret connection when creating virtual entities.

Recently we experienced an issue when we were trying to create virtual entities for audit history using SQL views instead of Tables.

As informed from MS Support team , this is not a supported solution so we forced to change our approach and use SQL Tables.

In spite of the final solution we would propose to have the ability to use also SQL views in creating virtual entities.

thank you!

We would like to have the ability to limit, change or update the contacts/users that receive notifications on Dataverse for Teams deletion actions. Some end users/Team owners receive these notifications, that may have used an app to test its functionality and may not be aware of Dataverse or what it is used for.

So, having the ability to change/modify the notifications that are sent out or limit them to Admins only would make it easier to manage user expectations or concerns regarding these notification emails.

After setting up an Azure Synapse link, we can view the Sync status of each table through the 'Azure Synapse Link' page.

If there is a failure to sync one of the tables, this is reported on the UI, but as far as I can see is not alerted elsewhere.

Access to this status programmatically, or via exposed logs, would be useful for holistic reporting in tooling external to the Powerapps dataverse.

In the admin center we have to options when copying across environments:

• everything - (application data + customization + schemas)
• Customization and schemas only

There should be a third entry to just copy applicational data if the mappings are compatible.