Power Platform Governance and Administration

With the Power Platform and registering webhooks with the plugin registration tool we are given not many options for authentication. We are currently using the Authentication of “Webhook Key” as per the plugin registration tool. It does not satisfy the policy when turn on Authentication on the Function App.

This Function Apps need to compliant with CIS Microsoft Azure Foundations Benchmark 1.4.0. Part of that, for function apps is to satisfy the policy as defined in this link https://learn.microsoft.com/en-us/azure/governance/policy/samples/cis-azure-1-4-0#9-appservice, and this policy https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fc75248c1-ea1d-4a9c-8fc9-29a6aabd5da8

Current Behavior

When a tenant's Default environment has no user activity for an extended period, the Power Platform automatic cleanup mechanism sends warning notification emails to tenant administrators and eventually deletes the environment. After deletion, a new replacement Default environment is automatically created. This new environment also becomes inactive over time, triggering the same notification cycle again.

For organizations that do not use Power Platform (for example, tenants that only use Power BI), this creates an endless loop of notification emails that cannot be stopped. The official documentation confirms:

"You can't turn off this cleanup mechanism. However, you can review the last activity date for environments in the Power Platform admin center."

Source: Automatic deletion of Power Platform environments (Microsoft Learn)

The only options to prevent the cycle are triggering activity on the environment periodically or acquiring a premium license, neither of which is practical for organizations that do not use Power Platform.

Requested Improvements

This idea contains two requests:

1. Allow administrators to opt out of inactivity notification emails: Tenant administrators should have the option to acknowledge the cleanup process and suppress future notification emails for the Default environment. For example, a one-time "Do not notify me about this environment's inactivity" toggle in the Power Platform Admin Center.
2. Allow administrators to disable automatic re-creation of the Default environment: After a Default environment is deleted due to inactivity, administrators should have the option to prevent the system from automatically creating a new replacement Default environment. This would break the cycle entirely for tenants that do not need the environment.

Business Impact

• Organizations that only use other Microsoft products (e.g., Power BI, Microsoft 365) but do not use Power Platform receive recurring notification emails indefinitely with no way to stop them
• This creates unnecessary confusion and concern for administrators who do not understand why they are receiving deletion warnings for a service they do not use
• The current behavior generates avoidable support cases, consuming both customer and Microsoft support resources
• Providing an opt-out option would improve administrator experience and reduce noise for non-Power Platform tenants

Affected Components

• Power Platform automatic environment cleanup mechanism
• Default environment lifecycle and re-creation logic
• Administrator notification email system
• Power Platform Admin Center settings

As we have known, there are 2 types of copying environment, "Copy everything" and "Copy Customization only". However, there is no function to allow copying data, could have a function to copy data only between environments so we can use data with old customization to test firstly before applying to higher environment?

After updating user from Entra ID group, user need to sign-in to Dataverse to get syncing information, that is designed by the system for group team in Power Platform admin center. However, for some disabled user, they are unable to sign-in the environment again and we have to edit manually. We would like to have a feature that syncing user automatically from Entra ID group to Power Platform team group without any manually action from users or admin.

Currently, we don't have the ability to restrict access to the Power Platform admin center.

By implementing this feature, you can improve the security of your users.

Make "UK English" and installable language into our Dynamics 365 environment.

Now there are several (less well-known) languages (eg Kazakh), which can be install. They are available in the list to be selected and installed. So why not "UK English"?

How do you see which languages are available? When going from Power Platform Admin Centre, selecting an environment, clicking "..." alongside that environment, and selecting "Settings" from the context menu, then going to "Product -> Languages", you get a list of language you can install ito your environment. But "UK English" is missing from this list.

We would like "UK English" to be in that list to be installed.

When our environment was installed, the consultant selected the defauly language of "US English". But we are in the UK, and want it to be changed to "UK English". I've been told that we can't do this retrospectively.

Why does it matter? Every so often the issue pops up. For example, in "Customer Service Hub", if you wish to create an Email Template, the only selectable language is "US English". We want "UK English" to be selectable, so we don't get all those apparent spelling issues.

So please add "English (United Kingdom)" to the list of languages that can be installed.

Many thanks

Michael Bradley

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.