Power Platform Governance and Administration

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.

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.

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.

Please provide a dashboard for monitoring the flow of moderated emails that have been escalated to a manager via an Exchange DLP policy. There is currently no way to view these messages that are pending approval if staff are on leave, absent, etc. This feature was present in the legacy governance portal.

Due to security controls in my organization, I am unable to set my Azure Key Vaults to allow all public network access (nor would I want to, if it was allowed). Due to this, I must maintain an extensive allow list of IP addresses that the Power Automate platform uses. This is not a sustainable practice, being that the list is hard to find and subject to change. It would be great if Power Automate could be made a "Trusted Microsoft Service" so I would not have to maintain this allow list of IPs. Alternatively, if Power Automate could work with the Key Vault team to make Key Vault work with service tags, that would also work.

When managing security roles for a specific user having a button to remove all security roles instead of needing to scroll down to uncheck each security role would be nice.

Could you please add English (Australia) to Dynamics 365 to have to continue changing the spelling of words in the environment is time consuming.

We have more than 10k+ Power Platform Environments in our Production Tenant. There is a need to identify environments where Dynamics365 Apps are enabled for various projects , but looks like there is no OOB / automated way to get those details. So, identify a way through which we can get the list of Power Platform Environments where Dynamics365 Apps are enabled

I would like to request more robust error logging when dealing with permission issues in Power Pages. Users are presented with a generic error that they do not have permission to make the change but even with Dev tools and Azure logging there is no way to know the table or permissions that are presenting the error.

This will only lead to immense frustration in the product from end users and administrators.

In our case a simple Append to a related table needed to be added. This would have been present in CE and could have been solved in minutes compared to hours.