Power Platform Governance and Administration

Hello Team,

We were planning to get the notification alerts when the power platform environment changes from managed to unmanaged and vise versa as well.

We could be able to set this alert on all the environments as well as to a specific environment as well as per our requirement.

However, there is no such way available now. i would like to post my idea here, thus it can get noted. Thus in the future, we can have this alert added.

Thanks,

Minal

We need to clarify the region restriction in Azure policy applied to resource group since we're encountering a discrepancy in the parameters in the Azure policy when creating a Billing policy in Power Platform Admin Center.

The environment we're trying to add is located in [Australia Southeast], and the resource group is under policy which allows creation of resources in [Australia East] and [Australia Southeast]. Technically, this should pass because the location meets the requirements of the policy.

However, the Azure policy return the error missing region [Australia]. And only when user add [Australia] to the policy, it will allow the creation of Biling policy for the environment which is located in [Australia Southeast].

This doesn't make sense this this mean it will allow all region in Australia and is not restricted to Australia East and Southeast. There is no documentation mentioned this part, so this doesn't make sense to the end users.

We will need a documentation or explanation for this type of scenario to avoid confusion in the future.

When you delete any records from PPAC (e.g., deleting security role) and it is failed, only following error message is displayed.

"Unable to delete xxx. Please try again."

This message does not provide enough required information of root cause. In my case, actually it was due to dependency, but it was not easy to know it by error message.

Please consider making error message more detail and valid.

Following the release of the 2022 Wave 2 when responding to emails only the "Reply All" button is readily available. One has to click on a drop down menu to use the "Reply" option. We have 100s of D365 Teams integrated with shared event inboxes that we use to respond to customers all around the world in multiple languages. When using the "Reply All" button this causes several issues for us. One, it causes ticket loops since we currently have Automatic Reply enabled on our Modern ARCs. Two, it creates unnecessary emails send back to ourselves when not needed and increasing unnecessary storage. I would like to propose the return of the "Reply" button. At least in our case the "Reply" button is used more often than the "Reply All" and also it eliminates the extra steps needed to use the "Reply" option. Thanks kindly.

We would like to edit the relationship between Opportunity and Quote to avoid ownership cascading between the two entities

Mostly We use Contains instead of Equals options in Filter By in Girds/SubGrids across the D365 CRM. It will be user friendly to make Contains as default option for Filter By component or give ability to configure this default option through Settings.

On a table like Case table, the first cursor location cannot be changed on default function when creating records.

Using "setFocus" by JavaScript can make this happen, but this takes a lot of procedure.

It would be convenient if the first cursor location could be changed on default function.

Within a long-term entitlement, customers must specify the support time available each month.

However, the current feature does not have the ability to divide the available support time on a monthly basis during entitlement period.

When this feature is implemented, it will be very convenient for customers.

Create an entitlement

https://docs.microsoft.com/en-us/dynamics365/customer-service/create-entitlement-define-support-terms-customer#create-an-entitlement

We are in the process of moving from our Data Export Service environment to the Azure Synapse Link and Data Lake. One feature in the Data Export service was heavily used by our reporting was the GlobalOptionSetMetadata table and OptionSetMetadata table.

Azure Synapse Link's Manage Tables does not see these tables in CRM.

It would be very helpful if we could have access to these tables.