Power Platform Governance and Administration

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.

Currently:

Azure Synapse Links with Workspaces featuring private endpoints are not supported.

Benefits:

Allowing support for private endpoints allows more options and freedom for the user

Power Automate Environment Routing - Idea Description

Objective:

To enable environment routing for Power Automate, similar to the existing functionality in PowerApps, Copilot Studio, ensuring a seamless user experience and consistent governance across the Power Platform.

Current Challenge:

• Users are unable to route directly to a dedicated developer environment when accessing Power Automate, unlike the functionality available in PowerApps and Copilot Studio. This inconsistency complicates user experience and governance.
• The lack of environment routing in Power Automate leads to potential governance issue and increased administrative overhead.
• Thomson Reuters want to showcase instructions on how to use Power Platform, Governance and Support provided by Thomson Reuters. This has been possible with Environment routing to developer environment and again we hit a roadblock since this is not possible in Power Automate.

Proposed Solution:

• Implement environment routing in Power Automate to automatically direct users to their designated developer environment upon login.
• Ensure that this routing is consistent with the functionality available in PowerApps, providing a unified experience across the Power Platform.

Benefits:

• Improved User Experience: Users will have a consistent and intuitive experience across PowerApps and Power Automate, reducing the learning curve and potential for errors.
• Enhanced Governance: Automatic routing to the correct environment will help enforce governance policies and ensure that users are working within the appropriate environments.
• Reduced Administrative Overhead: Simplifying the navigation process will reduce the need for manual intervention and support, freeing up administrative resources.

Technical Considerations:

• Integration with Existing Environment Routing: Leverage the existing environment routing mechanisms in PowerApps to ensure consistency and minimize development effort.
• User Training and Documentation: Update user training materials and documentation to reflect the new routing functionality, ensuring a smooth transition for users.

Conclusion:

Implementing environment routing in Power Automate will align it with PowerApps, providing a seamless user experience and enhancing governance across the Power Platform. This feature will reduce administrative overhead and improve overall efficiency.

In addition to its own catalog, Default's catalog is always displayed.

In this case, the Default catalog should also be able to be hidden, as this may reduce visibility.

We hope you will consider us.

I want to be able to check inquiries made more than 2000 items ago in order to review past inquiries.

When you want to restore a PROD type org you always need to mark the org down to Sandbox type and then restore. But when you mark the org from PROD type to sandbox type you cannot see all 28 days' worth of backup the retention shows only for 7 days as now the org is et as Sandbox. What is the threshold time to see all your 28 days' worth of backup data for the originally set PROD org type. PG should make the switch and retention at least 6 to 8 hrs. long and not instantaneous.

Customer sometimes need to go back to 7+ days older backup for this originally marked PROD rog.

Currently, the New Power Platform Admin Center is in preview, and a customer reported experiencing issues with sorting environments by column headers. Specifically, when attempting to sort by the "Database Consumed" column, the environments are not sorted correctly from highest to lowest. This issue seems to affect to most of the columns and under specific conditions of certain customers.

Additionally, when users click on the headers to sort, a down arrow appears on all headers, which creates confusion as it is unclear which column is sorted and in what order. This is not a good user experience and needs improvement.

Steps to reproduce:

1. Log into PPAC
2. Go to Licensing > Dataverse
3. Click on "Manage Billing Plans" button
4. Sort by any column header (i.e. Database consumption)
5. The arrows will display in all the columns and the table is not sorted (see screenshot below)

We suggest improving the sorting functionality to ensure accurate and reliable sorting by all column headers.

Our customer currently want to raise the Feature request to change the "Welcome" salutation from Power Pages home page (make.powerpages.microsoft.com) to other personalized welcome/greetings salutation, also attach with customer's preferred name.

This would greatly enhance customer's personal experience when accessing Microsoft's product.

Current Behavior:

When we try to create an environment without any preinstalled apps by selecting ‘Enabling Dynamics 365 apps’ to Yes and ‘Automatically deploy these apps’ to None it is still getting created with preinstalled apps.

Expected Behavior:

If we select 'None' for the option ‘Automatically deploy these apps’ , then the environment should be created with no apps in it.

Hi Team,

Power platform administration is bit difficult if there is no option to get how many dataverse environments we have and its admins, checking manually also difficult, could you please check on this request.