Power Platform Governance and Administration

Reporting an issue where a Microsoft partner is unable to view their client's licenses in the PPAC, despite having all necessary GDAP roles assigned. This issue is particularly challenging as the report is still in preview, and there is no dedicated support team to address these failures.

Steps to Reproduce:

1. Log in to the Partner Center using an account with GDAP roles assigned.
2. Navigate to the PPAC license requirement report.
3. Attempt to view the client's licenses.
4. Observe that the report fails to display correctly, showing "No data to display." (screenshot below)

Please enhance the functionality and reliability of the PPAC license requirement report, ensuring it works seamlessly with GDAP permissions. Provide clear documentation on the required configurations and roles for partners to access the report.

Currently, all the Asia-based tenant can create Dataverse environment from other region except for Australia and India. This is hard for some business scenario when the end-user is based in these 2 countries, but the administration and development need to be done from Asia region.

Currently, if we want to export user list for an environment, we have to go inside the environment and export the data from table User. Customer would like to have function to export user list for all environment at once in Power Platform Admin Center. That will help to save time for Administrator in management process

In Power Platform Admin Center, currently we are not able to track the progress of Backup&Restore process. It leads to several inconveniences because we are not able to know when the environment is ready to use.

Our team is certain they were previously able to search by GUID in the global search. We used to be able to search by GUID for multiple different tables/entities.

Integrating Teams chat in a model driven app, doesn't work.

In our company we have also Dynamics 365 Sales and there it works.

It doesn't seem to be a licence issue.

We followed all the Microsoft instructions on:

https://learn.microsoft.com/en-us/dynamics365/sales/teams-integration/enable-teams-chat

So, the question is, where is the problem?

How can we enable and use Teams in our model driven app?

The error we receive is: “No manifest found”.

The current implementation of colouring in model-driven app charts is very limiting.

The excellent XRMtoolbox use to provide great workarounds for branding charts and customising labels etc, but currently most of the features are now not supported after the switch to the unified interface.

We should, at the very least, be able to change the colour of series on charts. Out of the box, layering the default green line over a blue column chart, for example, makes it unreadable. This is super frustrating to users.

We shouldn't have to implement Power BI for simple data charts on model driven app dashboards to just make things readable.

Currently, Dynamics 365 primarily supports logging through Application Insights, which limits flexibility for customers who have invested in other enterprise logging and monitoring solutions. I would like to request native support for integrating the standard .NET ILogger interface with alternative logging providers beyond Application Insights.

This enhancement would allow developers to centralize logs across services within their existing observability infrastructure, improving diagnostics, operational consistency, and maintainability.

All the dates in the admin center are backwards (American) dates. Regardless of browser settings.

All dates should conform to the local settings. There's only a handful of countries that have their date formatted m/d/y.

Ideally, this should be a tenant wide setting, but at least start in the admin center. The 4th of November is not proceeded by the 4th of December.

Microsoft can deploy new fields on Dataverse Tables at any time, and can do it in Production-type environments before Sandbox-type environments. These unexpected changes in data model can generate issues on applications (having their own constraints) that consume Dataverse.

The suggestion is:

• To have visibility in advance on fields deployed by Microsoft in Dataverse
• That Microsoft always deploys new fields in Sandbox-type environments before Production-type environments