Feridun Kadir Expert CRM Services Ltd Principal Consultant

In Dynamics Portals, we can use auth0 as an identity provider. This works. However, the portal logout does not logout of auth0 which means that after a user has "logged out" their auth0 token is still valid. When the user next clicks sign-in on the portal they are logged in immediately. There is a workaround which is not elegant and it would be great for the portal to support logging out of auth0.

This applies to multiple Dynamics 365 products. Starting in August 2020, merging records became an asynchronous operation (https://docs.microsoft.com/en-us/power-platform/admin/async-cascading) This was not a helpful change and is making the system less efficient to use. Most end-users don’t know or care what asynchronous processing or cascading transactions means. Moreover, they want to see the result of whether the merge worked or not without having to go to another area (system jobs) that they rarely use. Can we please go back to the old behaviour or at least make it a configurable setting at the org level?