Image by Kris from Pixabay In my previous blog post, I talked about missing parts on forms when you only focus on granting permissions on menu items. This is mainly the case if you start privileges and duties from scratch to ensure a least permissions principle. Form parts are a type of form control where security can be managed with other menu items. There is more to take into account next to the previously discussed form parts. There are also other form controls where you need to take care of permissions in another way. This blog post is an addition to my previous post where you will now read about additional form control permissions on privileges.
Read morePosts
Image by Reimund Bertrams from PixabayImplementing the correct security is not only about granting access to menu items. You need to understand the full architecture and realize the menu item linked to a menu is only one option when Microsoft mentions user interface elements in their documentation about the security architecture. I will spend several blogs explaining more options that you need to consider to get the result required by the business. In this post, I will share knowledge about securing form parts.
Read more
Image by forium from Pixabay In the past, I already wrote a blog for awareness about the session date in Microsoft Dynamics. When you read this blog, you will learn about the purpose, but also that there are two options to change the session date in the standard application. However this is a great and helpful feature, some organizations might want to lock this option to prevent incorrect usage of this option and ensure people will post in the most recent period by default unless they would need to backdate a transaction. In this blog, I will demonstrate how to disable the option for all or particular end users.
Read more
Image by Thomas Breher from Pixabay During the past years, I have seen a lot of questions about setting up users who are not part of the Azure AD tenant linked to a Dynamics 365 Finance and Operations environment. Usually, there is a simple reply by stating that the Provider field on the User details should be altered to indicate where to authenticate the user. This reply does not cover the licensing requirements, components that require an app registration in Azure AD, and users not part of an Azure AD, but having e.g. a Microsoft Account. With this post, I will provide the full details to correctly enable external users.
Read more