Power Platform Governance and Administration

In the PPAC, when going to resources > flows for a large environment, not all flows are displayed. Please fix this so admins can easily reassign flows when needed rather than having to go through powershell.

Reference: TrackingID#2504070040013814

https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-management/manage-orphan-flow-when-owner-leaves-org#assign-new-co-owners-to-an-orphaned-flow

It is not "hard" to find orphaned flows, it is currently not possible.

We strongly believe that the fact that the Finance and Operations Basic User role is only assigned when a user has a fully qualified Finance license is a mistake. As outlined in the Microsoft Learn documentation on Authentication and Authorization (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/power-platform/authentication-and-authorization#security-model), this role is intended to provide access to Virtual Entities-a feature that is not limited to Finance-related functionality alone. Given this, the role should also be assigned to ALL users with a fully qualified FnO license (like project operations license, SCM license). We believe this is simply a design flaw or bug in the automatic role assignment process. Additionally, the same documentation only discusses the assignment of this role, not its revocation, which further adds to our concerns regarding the current behavior.

Customers are often choosing to use Project Operations licenses for their FnO operations, as this license is cheaper then a Finance license, and qualifies as a full FnO license according to the licensing guide of March 2025:

• on page 24: "Project Operations licenses have no roles at the Operations – Activity level, but full users of Project Operations have rights to Operations – Activity roles for other Dynamics 365 products, such as Finance and Supply Chain Management"
• on page 39: In the table of capacity licenses, you can see that the same capacity is foreseen in the Operations database for Commerce, Finance, Project Operations and SCM licenses.

It does not make any sense that rights to use virtual entities would not be applicable to the other fully qualified FnO licenses like project operations or supply chain management.

We would like to have feature that can control deployment time for out of the box solution. The feature should allow us to schedule special time for system solution to avoid slow performance by Microsoft's solution during working hours.

The same logic used for the Microsoft solutions. The possibility to link solutions to each other. For example, by mark the base solution as Main Solution on the new solution.

So if you have a "base" solution and you want to make an extra solution to keep certain things apart, make sure that that extra solution is placed in the layering just above the base solution.

This way you can also deploy faster because you can keep the solutions small.

Customer encountered an issue during the initial sync of tables for the Synapse link. As a workaround, we suggested removing the table from ASL and adding it back again. However, due to the large number of tables, we need an alternative solution to resolve this issue effectively.

Request:

Please assist us in finding a better way to address this problem.

 Idea Recommendation for Managing System Tables in Dataverse  

To enhance transparency and control over system tables in Dataverse, I propose a System Table Management Dashboard with built-in tools and clear visibility for users/customers to manage data, solutions, and privileges effectively.  For example we have a constantly growing WeResource Base Table, whcih we have to ope a support ticket, in order to Microsoft run a script to delete ophaneted customization records

Key Features and Benefits

1. Transparency of Data

  - Data Source Labeling:Every system table should include metadata showing:  

    - Origin of Data: Which solution (managed/unmanaged) introduced it.  

    - Purpose: A short description of its role in the system.  

  - Solution Mapping View: A dashboard that visualizes which tables and components belong to which solution,  1^st and 3^rd party customizations, solution imports and installed applications metadata.  

2. User Privileges and Rights Management 

  - Granular Permissions: Since Microsoft has defined that the relationship between a user and the data, not the application or environment owners determines access, this functionality should extend to managing system tables.  

  - Role-Based Management: Customers and administrators should have access to this functionality based on their assigned roles and rights, enabling them to:  

    - View and manage data associated with system tables.  

    - Execute cleanup tasks (e.g., removing orphaned customizations).  

  - Audit Trails: Log all changes made to system tables, including data modifications, schema updates, and deletions, ensuring secure and accountable management.  

3. Orphaned Customization Cleanup

  - Built-in Cleanup Tool: Replace the existing script-based approach with a user-friendly feature that:  

    - Identifies orphaned customizations (e.g., unused fields, orphaned records, deprecated tables).  

    - Provides a preview of items to delete, along with their impact on solutions or applications.  

    - Allows users to approve deletions directly within the Dataverse UI based on their roles and privileges.  

  - Impact Assessment: Notify users of dependencies before deletions to prevent accidental system issues.  

4. Enhanced Table Documentation

  - Each table should have a "Description Tab", where metadata like:  

    - Creation Date  

    - Last Modified Date  

    - Associated Solutions  

    - Dependency Tree (showing related tables and components)  

    - User-defined annotations  

    can be displayed.  

5. Customization Validation Reports

  - A Validation Tool to:  

    - Identify conflicting customizations across solutions.  

    - Highlight unused components for potential cleanup.  

6. Open Architecture Approach  

  - Ensure that all management tools, including cleanup functionalities, are fully accessible through APIs or Admin Center Tools, so customers can integrate them with their workflows if desired.  

  - Avoid black-box features; instead, provide clear documentation and functionalitoes and transparency on what operations the system performs.  

Implementation Roadmap*

1. Phase 1: Data Transparency on Dashboard

2. Phase 2: Cleanup and Validation  on Dashboard

3. Phase 3: Privilege Management on Dashboard

4. Phase 4: Documentation and APIs and Tools for all Funtionalities  

Expected Outcomes

- Improved Admin/User Confidence: Transparent data and solution management reduce confusion and trust issues.  

- Operational Efficiency: Built-in tools for cleanup and validation save time and reduce risks.  

- System Integrity and Compliance: Role-based access ensures users and administrators operate within defined rights, upholding system integrity and security.  It should be already like that.

By embedding these features into Dataverse and aligning them with Microsoft’s user-role-based access control model, customers and administrators will gain the functionality and transparency needed to manage their environments effectively while staying aligned with modern data governance principles.

Hi team,

Please help create a button so we can export environment name and information in the environment page

Request to Reference Non-Primary Information from Primary Audit Logs

There are customer records A and A’, with A being the primary. When merging, only the information from A is adopted, and no integration event is recorded in A’s audit history. If the merge itself was an error or if you want to check A’s information, you will need to search for the inactive customer information, which becomes difficult over time. Without a merge log on the primary side, there is a risk of not realizing that an incorrect merge has occurred.

Therefore, We propose that a merge log be recorded on the primary side as well, allowing reference to the non-primary data.

Hi team,

We know that the choice field was create differently however we want the choice field able to modify through solution import like the other field.

Per the document here:  Dynamics 365 service description - Power Platform | Microsoft Learn. hyperlink “Product and Feature Availability”

shows the current status of the following feature as "not available"

Embed a model-driven app as a tab app in Teams

This is a significant gap in Teams/Power Apps integration functionality. Both GCC and Commerical users can use Teams Web to embed and connect to Model Driven Power Apps on a channel tab, but the Teams Desktop experience for GCC users is broken.

Please fix this ASAP.