From the Microsoft Dynamics 365/CRM Blogs: Server-to-server authentication; Filtering issue; Lookup views; Security roles in process flows

From this week's Microsoft Dynamics 365/CRM blogs:

• How to configure Dynamics 365 S2S authentication
• How to solve lookup filtering issue with Dynamics 365 version 8.2.2.128
• Customize lookup views in Microsoft Dynamics 365/CRM
• Adding and updating security roles to a migrated business process flow

How to Configure Dynamics 365 S2S authentication

On his blog, Microsoft Dynamics 365 consultant Joe Gill wrote that the combination of the Dynamics 365 Web API and Azure Active Directory enables a number of applications to integrate easily with Dynamics 365 to retrieve and update data. 

This can be any type of app, including a web site or a data integration process. It's commonly referred to as server-to-server or S2S authentication, he wrote.

Calling the Web API using S2S is a two-step process - the first step is to authenticate the calling application using Azure Active Directory, according to Gill.

In his blog post, Gill explained how to register an S2S application in Azure AD and how to create an application user in Dynamics 365 with a custom security role to give the app specific security rights.

You can read about it here.

How to solve lookup filtering issue with Dynamics 365 version 8.2.2.128

On the Magnetism blog, Jordan Hohepa wrote that the October 2017 Dynamics 365 Service Update 1 for 8.2.2 offers a number of updates and hotfixes for Dynamics 365 Online instances.

However, Hohepa wrote that one of Magnetism's clients discovered after the update, some of its lookup filtering on related records wasn't filtering correctly. It seemed to happen only with fields that were being filtered by a lookup, which is located in the header ...