-
Inconveniences encountered when copying the environment.
We've highlighted the inconveniences encountered when copying the environment:
- All connections will require manual reconnection.
- All the flows (our customer has more than 200 flows) need manual activation in this scenario. Additionally, certain flows will require opening and editing to establish connections.
- Activating the flows and connections results in the addition of an unmanaged layer.
By design:
=======
- Flows - In the target environment, existing solution flows will be deleted but existing non-solution flows will remain. Review the flows in the target environment to ensure that triggers and actions are pointing at the correct locations. Solution flows will be disabled so enable flows as needed.
- Connection References - Connection References will require new connections. Create and set connections on Connection References.
- Custom Connectors - Custom connectors should be reviewed and, if needed, deleted and reinstalled.
Document: https://learn.microsoft.com/en-us/power-platform/admin/copy-environment#review-components
-
Prevent users to Dynamics CRM Default Environment.
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.
-
Restrict users from taking screenshots with Dynamics app to prevent sensitive data.
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.