Power Platform Governance and Administration

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

In Azure Synapse Link for Dataverse, Tables of Dataverse are being synchronized to CSV files. We face issues when the data model of a Table changes.

Indeed, when a new column is added in a Table, only the new or updated records have the new column in the CSV file. Existing records do not have the new column in the CSV file.

Then, all lines in the CSV file don't have the same number of columns, which is not standard and makes the CSV file not readable by many tools and languages. The only solution to fix the CSV file is to remove the concerned Table from the synchronisation, and add it again.

This is also a bigger issue because Microsoft can deploy new fields on a Table at any time, and can do it in Production-type environments before Sandbox-type environments.

Then, we face unpredictable issues in the CSV files in Azure Synapse Link, that we can solve only after they happened, even in Production.

The idea is the following: when a new column in added in a Table synchronized in Azure Synapse Link: all records in the CSV file should be updated to use the new column, in order to have a standard CSV file accepted by all tools and languages.

Currently, there is no centralized dashboard available to track audit log settings and retention periods across environments in Power Platform. This creates a visibility gap for administrators who need to monitor and manage data governance effectively.

We’ve observed the following:

• Audit logs can have their retention period set to "forever", which may lead to excessive Dataverse storage usage if not regularly monitored.
• At present, admins must manually access each environment’s settings to review audit log status and retention configuration.
• There is no consolidated view to track Dataverse audit log usage, retention periods, or potential overuse risks.

We propose a feature enhancement to include a dashboard in the Power Platform Admin Center that provides:

• A summary view of audit log status and retention periods for each environment.
• Alerts or indicators for environments with indefinite retention settings.
• Usage statistics showing how much Dataverse space is consumed by audit logs.
• Add two new actions(get audit settings and update audit settings) in the PowerPlatformforAdmins connector.

This would enable admins to take proactive measures for capacity planning and ensure compliance with internal data retention policies.

Thank you for considering this request.

A metal briquetting machine compresses scrap metal, chips, and turnings into dense, compact briquettes for easy handling, storage, and recycling. This hydraulic or mechanical system reduces waste volume, lowers transportation costs, and minimizes environmental impact. Ideal for industries like automotive, aerospace, and manufacturing, it processes materials such as aluminum, steel, copper, and brass. The machine improves recycling efficiency, reduces oil contamination, and enhances workplace safety by minimizing loose metal debris. Available in various sizes and capacities, modern briquetting machines feature automation, adjustable pressure, and user-friendly controls. Investing in this equipment boosts sustainability, cuts costs, and optimizes metal waste management.

Please help create that capture user-related metadata such as device type (e.g., desktop, mobile, tablet), access channel, and browser type (e.g., Chrome, Edge, Safari) used within our model-driven application

I would like the ability to Disable or Hide Edit Filters button on Main Grid based on a users Security role or at the Application module level - preferable both to provide the most flexibility around who can edit filters in views.

This is important to me as I am using views to prevent users from seeing sensitive data that they should. not be able to access.

I am already using Owners Teams for a higher level of data segmentation and now find that we are exposed if the user discovers they can Edit the filter and remove one of the rows thereby exposing data that they should not see.