Dataverse Long Term Retention

I would like to be able to set a view to LookUp field on Business Process Flow(BPF). Since we can do it to the same field on the form, It would be nice to see customizations on the same field on BPF.

Currently, there is no audit for any change made to the Environment Settings in Power Platform Admin Center. So, when there is an unknown change in a setting such as 'Audit settings' for the log retention policy for an environment, we have no clue to who changed it.

All current audit features are for changes inside the environment Dataverse and access to environment. Even Azure Purview.

I'd be great if we can have an audit to record change for general Settings in Power Platform Admin Center as well.

Good thing that Teams, Azure and Outlook have Dark Themes. Now it will be better if we can have Dark Theme button on D365 Environments that Users can have the choice to turn on or off.

Currently, row checksums are created when doing an Excel export and are not present in the table.

However, placing the row checksum in the table, via a connection to OData, would allow for the following actions.

1. Connect the information in the Power Apps table to Excel by acquiring data from Odata.

2. Use PowerQuery in Excel to prepare an Excel file with the same information as the view of the Power Apps application in use.

3. If you want to modify the records in the table, modify the data in the Excel format.

4. Import the corrected Excel file into PowerApps using Excel Import.

This allows data modification through the Excel format when the table within Power Apps is not to be directly modified by an unspecified number of users.

Currently, row checksums are created when doing an Excel export and are not present in the table.

However, placing the row checksum in the table, via a connection to OData, would allow for the following actions.

1. Connect the information in the Power Apps table to Excel by acquiring data from Odata.

2. Use PowerQuery in Excel to prepare an Excel file with the same information as the view of the Power Apps application in use.

3. If you want to modify the records in the table, modify the data in the Excel format.

4. Import the corrected Excel file into PowerApps using Excel Import.

This allows data modification through the Excel format when the table within Power Apps is not to be directly modified by an unspecified number of users.

Microsoft should add the features to restrict the access of the Dynamics 365 environment to a specific IP address. This is practical and to avoid any security risk.

Expectation:

==========

We need to restrict users from taking screenshots within the Dynamics app to prevent sensitive data from being leaked outside of our organization.

Investigation:

============

Upon exploring the out-of-the-box features of Dynamics, we have not found a native solution or workaround to fulfill this requirement.

Additionally, our investigation into utilizing Microsoft Intune revealed that while it is a powerful tool for device management and security, it does not directly address our need to restrict screenshot functionality. Furthermore, as we do not enroll users' devices into Intune due to lack of control over user-owned devices, this avenue does not provide a viable solution for our situation. We have also consulted with Microsoft Intune engineers to explore potential options within the tool, but have not found a suitable solution.

Ask:

===

In light of the above, we kindly request if there could be an out-of-the-box feature or workaround that could be implemented to restrict users from taking screenshots within the Dynamics app. Enhancing data security is of utmost importance to us, and we would greatly appreciate any assistance or guidance you can provide in this matter.

We believe that implementing such a feature would significantly bolster the security measures within the Dynamics app, ensuring that our organization's sensitive data remains protected from unauthorized access or leakage.

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

https://community.dynamics.com/forums/thread/details/?threadid=49b615f4-14e6-ee11-904d-00224827eb85

Right now, Power apps only supports 44 languages. There are thousands of languages and of course not all of them need support immediately, but it would be good to add some of the more popular ones such as Somali which is growing at a very fast rate.

Issue description: There is no way to block auto-assign roles for users in the Default Environment.

Example:

Users with the Power App license is always auto-assigned the System Maker role in the Default environment. Please note that we cannot remove it.

Actions taken:

I attempted to deactivate automatic license-based user role management and remove licenses for an organization. For further information, please refer to the following resource: https://learn.microsoft.com/en-us/power-platform/admin/opt-out-automatic-license. However, this process doesn’t apply to the default environment with specific roles.

From the document: "Does this impact the "Default" environment too? For the "Default" environment, Environment Maker and Basic User roles will continue to be automatically assigned to users even after opt-out."

Expectations:

==========

We should have an OOB workaround to prevent users, especially Guest Users, from accessing the Default Environment. Alternatively, if possible, the Opt-out option could be applied for the Default environment.