Power Platform Governance and Administration

Power Pages does not allow a site to be created with en-GB as a site language.

Please add.

One year ago I created a support ticket, that for columns of type date/time with timezone adjustment configured to be time zone indipendent a wrong time is displayed in the grid view.

On forms the correct time is shown, while in the grid view the user offset of the personal settings is added to the time, which shouldn't happen if "timezone independent" is chosen.

After some analysis this has been identified as bug, but the ETA was unknown at that time.

Now more than a year passed and we created another ticket for this issue, to ask if an ETA is known. We've been told by support, that many other people has raised this bug as well, but it is not enough that this bug is being prioritized by the product group and that we should raise an idea for that.

With the upgraded look and feel of the Timeline in Wave 2 2022, the Reply All and Forward icons were moved into a drop down. This is now an extra click for users. For us in particular, we always use the Reply All button because we can't see who all was on the original email without opening the email record, and for us we do a lot of quick replies.

When a Synapse link configuration is done in a DEV environment, the synapse link configuration and table mapping can be transferred across environments (TEST, PROD)

Transport Azure Synapse Link for Dataverse configuration - Power Apps | Microsoft Docs

This process is manual. It would be great to have a way to deploy the synapse link through an automated deployment with DevOps.

In addition, the related storage account can be different on each environment, so I would be great if we could have a way to Deploy via DevOps an Azure link and its configurations, and change the related storage account for the target environment, in an automated way.

We have export to datalake which can export tables and entities.

This service is transitioning into Synapse Link for Dynamics.

The fact that it will be entity driven is worrying:

1/ we don’t have (fast) entities for every table in finops (not even for standard ERP tables)

2/ existing entities contain far more tables than the ones needed in datalake (best example customerv3)

cfr. also https://experience.dynamics.com/ideas/idea/?ideaid=5444118e-6c79-ec11-b820-0003ff45920b

A workaround would be to fake entities mapping all fields in the table at runtime… (platform wise)

Business need: Export of charts from the dashboards to PDF or XLSX file. Now users don't have this possibility and only workaround of this missing feature is creating screenshots.

PPAC reports are used in our organisation for audits, financial planning, compliance etc. It is essential for us to get transparency on the data we get from PPAC so that we get clear indicators which can guide our strategic decisions.

Requesting for below improvements for PPAC license reports:

• Support at least 12‑month historical license usage data: Power Platform Admin Center (PPAC) license usage reports currently have limitations that impact enterprise reporting and governance. The maximum historical view is limited (e.g., 180 days), while our requirement is at least 12 months of data.
• Similar experience for Power Apps and Power Automate licensing usage reports:

1. Currently Power Apps license can only be downloaded month on month, and Power Automate license can only be downloaded with filters like 30 days, 60 days, 90 days, 180 days. However, it would be useful if there are similar experience for both license types. For example: Why not combine both types together for both licenses? Keep data for at least a year to download and user can download either month on month data or consolidated data for license usage.
2. There is another difference between Power Apps and Power Automate report. Power Apps report provides consolidated report for all licenses, whereas Power Automate provides option to download each and every license usage separately. The best UX would be to combine both of them and to allow users whether to download only for a single license or multiple or all the licenses.

• Clearly explain counting methodology and discrepancies: There are multiple columns with confusing names and subcategories - like License Classification, ServicePlanName and SKUName. We are confused on which one to consider when calculating usage for a particular license. It would be great if there was a clear documentation on what should be considered on which scenarios. Also add details for each of the subcategories of each columns so that the report has transparency on what data it shows.
• Blank environment names: There are certain rows which return Blank environment names. Wondering why it happens and if that has any specific reason, can we have a documentation on why that happens?

These enhancements would reduce manual effort, improve trust in PPAC as a single source of truth, and strengthen enterprise license governance.

Currently, there are no settings to change the datetime format in Power Platform admin center.

It is currently default as mm/dd/yyyy.