-
Conditional access for Dynamics 365 environment.
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.
-
Improve cache reload performance so it does not affect user daily experience.
The patch request for the bookable resource booking entity is currently consuming way too much time due to the cache reload from the backend. This is also affecting a single-record transaction, which does not make sense and affects the user's daily experience.
The cache load should be done in an asynchronous way, so when users use the system, it does not take too much time.
-
Adding Button Control within Model-driven Apps
For now, the Dynamics 365 model-driven app provides a variety of controls that we can add to the main form; however, currently, the "Button" control is not yet available.
This is such a simple and amazing idea, which will help model-driven app developers add the button to a form much easier.
-
Create a button to disable the sync between Azure AD and CRM
Hi team,
Referring to your official article, System and application users it states that CDSUserManagement is responsible for provisioning and synchronizing users into Dataverse from Active Directory.
However, we’ve noticed that when we create a plugin, the System User updates our Mobile Phone table instead of CDS. To prevent this, could you please create an option (button) to disable this synchronization? This would ensure that System User and CDS won't update our table going forward.
Thank you, and I look forward to your assistance.
-
Expire period of trial environment should be 14 days
Hi team,
The 7 days period is to short for us to extend the environment. Please help make it 14 days. Thank you so much