Power Platform Governance and Administration

Currently, "Child Items Parent Id" property pulldown "Bind to a value on a field" in Power Apps Grid currently only supports Lookup fields with N:1 relationship.

However, depending on the operation, we want to use N:1 or N:N relationships.

Once this feature is implemented, we will be able to use Dynamics 365 and Power Apps more conveniently.

We release to production outside of office hours. Once we planned to release solutions to production at the same time Microsoft was also uploading Solutions to production which blocked out production release. We would like to be able to define time windows or have another solution to prevent Microsoft from uploading solutions to an environment to prevent interference with a production release.

At this moment Microsoft releases are organized globally according to Micrososft Support and can't be manually managed.

Introduction: The Power Platform is a dynamic environment for building and deploying applications and workflows. To further enhance security, streamline solution management, and facilitate an efficient Application Lifecycle Management (ALM) process, we propose a series of improvements. These enhancements aim to provide finer control over solution visibility, deletion, editing permissions, and flow run history access within Power Apps.

Proposed Power Platform Improvements on the Solutions:

• Selective Solution Visibility: Currently, when a new App or Flow is added to a solution, it becomes visible to all users with System Customizer and Environment Maker roles. To bolster solution security, we suggest introducing a feature that allows the solution creator to restrict solution visibility. By default, only the solution creator should have visibility to the solution. This ensures that sensitive applications and flows remain accessible only to authorized individuals, enhancing overall data security.

• Granular Solution Deletion and Editing Permissions: To address concerns regarding solution integrity and accidental alterations, we recommend refining solution deletion and editing permissions. By limiting solution deletion and editing rights to administrators and solution creators, the Power Platform ensures that only authorized personnel can modify or remove solutions. This change enhances accountability and safeguards against unauthorized actions that could compromise solutions.

• Enhanced Flow Run History Privacy in Solution: Recognizing the GDPR concerns related to flow run history visibility, we propose limiting access to flow run history data. Rather than exposing flow run history to all makers for a fixed 28-day period, the Power Platform should implement role-based access controls. This approach restricts flow run history visibility to solution creators, administrators, and designated personnel. This measure significantly reduces the risk of personal data exposure and aligns with data privacy regulations.

Conclusion: The proposed enhancements to the Power Platform address critical security and solution management concerns, aligning with the objective of achieving a robust ALM process. By allowing selective solution visibility, refining solution deletion and editing permissions, and safeguarding flow run history data, the Power Platform reinforces security measures and data privacy. Furthermore, to facilitate a more efficient ALM process, Power Platform could introduce features that enhance Solution Security and ensure that solution creators can work more efficiently, driving innovation while maintaining the integrity of their solutions.

Currently, if we create environment, we will be select "Add a Dataverse data store" and "Pay-as-you-go with Azure". We would like to make these selectables only for some administrators. If this feature is implemented, we think it would make Dynamics 365 more useful. 

With DES, Customers were able to add/remove entities programmatically from the DES profile. However, this isn't possible with Azure Synapse link. Due to unavailability of this feature, workloads which were previously using automation will now be left to be managed manually.

Please help provide a supported way to automate add/remove table in Azure Synapse Link profile for Dataverse.

In our company's scenario, we don't want users to be able to share their opportunities themselves, but through plugins.

So we need to make the "Manage Access" option of the "Share" button hidden by tools, for example, ribbon workbench.

Currently, "Manage users in Dynamics 365" sets the default view of the user entity with a pin. However, because each user must change the default settings, it takes time to display the same view to all users.

Being able to change default settings in bulk makes design easier for administrators. Therefore, if this feature is implemented, it will be very beneficial for users who use this app.

The features described in the docs below are currently only available in CSW and OCS.

URL : https://learn.microsoft.com/en-us/dynamics365-release-plan/2022wave2/service/dynamics365-customer-service/enhanced-settings-ai-suggestions-knowledge-articles-similar-cases

URL : https://learn.microsoft.com/en-us/dynamics365-release-plan/2022wave2/service/dynamics365-customer-service/auto-enabled-ai-suggestions-similar-cases-knowledge-articles

For users using Customer Service Hub app, being able to use the Dynamics 365 Customer Service as a feature is very beneficial for users who primarily use this app.

Add the scroll bar arrows back on all Views across all Dynamics 365 apps, or add the option to enable them organisation-wide.

Since the RW2 update in October the up and down arrows on the scroll bars have been removed. A number of our users have raised that they were a much easier way to move down long lists in small, precise increments than dragging the bar itself or clicking in the blank space above and below it, and for those users whose roles require small interactions with a lot of records one after the other this adds up quickly and has adversely impacted their efficiency.

The ability to have the arrows back on all Views would be a lot of help for users like this, and should have a minimal aesthetic impact as the arrows were already pretty discreet.