Workflow and security do have strong relation in Microsoft Dynamics 365 Finance and Operations. A user not assigned to a workflow task can’t approve a workflow instance. Also, the user should have correct permissions from the security settings as I explained before in another blog. (Workflow security in Dynamics 365 Finance and Operations)
In this blog, I will explain the behavior of a setting available on the Workflow parameters form, called Require explicitly assigned users.
Read more
This week, I presented about AI in Microsoft Dynamics 365 F&O together with Hylke Britstra at a Dutch Dynamics Community event. While preparing for the session, I created some demos to extend the Copilot sidecar and found some hints in the coding for using natural language to navigate the application. I will elaborate on the upcoming feature and show you how you can already enable the option to use Copilot for opening e.g. the Workflow history page.
Read more
Starting in Microsoft Dynamics 365 F&O version 10.0.39, Microsoft enforced security guidelines for external users. Effectively, Microsoft disabled the cross-tenant access in Dynamics 365 F&O. This means that external users from a different tenant, can’t log in to Dynamics 365 unless they are created as a guest user in your own client. In this post, I will elaborate on the change, how it can impact your environments and how to setup external users correctly.
Read more
Security in Dynamics 365 Finance and Operations (F&O) is not easy. When you want to define custom roles, this also has a licensing impact. Sometimes, you expect a particular license for your role, but the application states something different. In this post, I will provide a scenario where the license expectation is a Team members SKU as the intention is to have a read only role, but the role will end up as Operations license.
Read more
Image created by AI using Microsoft Designer