Adding on-premise Dynamics 9 as a Relying-Party (RP) trust in ADFS 4.0 follows the same path as listed here but ADFS 4.0 has few changes to wizard options as detailed below:

In the next step of the wizard make sure the metadata end point is accessible through IE, in the example below the URL is https://crm.idynamics.dev/FederationMetadata/2007-06/FederationMetadata.xml, give a display name and choose Next

 

Access Control Policies defines the level of access that can be provided to RP

Click Next after reviewing the following settings

The Relying Party (RP) will be added successfully the next step will the configuring Claims Issuance Policy (aka adding Claims Rules in ADFS 3.0 and below…)

Right click on RP and select Edit Claim Issuance Policy and add the claims rule set as indicated here

Once the RP has been successfully accessing the CRM organisation will display the following error because of certain defaults in ADFS 4.0

In the event viewer on ADFS server the above error will translate to a MSIS7102 error code of ADFS indicating an unsupported Authentication Method

In order to identify the Authentication Method  extract the redirection URL from CRM to ADFS and you will notice that Windows Integrated Authentication (WIA) is used as per wauth parameter, and this is not enabled in ADFS by default for Intranet scenarios

https://adfs.idynamics.dev/adfs/ls/?wa=wsignin1.0&wtrealm=https%3a%2f%2fcrm.idynamics.dev%2f&wctx=rm%3d1%26id%3df589b041-3924-4d87-a8f1-96057169b19f%26ru%3d%252fAPIS%252fdefault.aspx%26crmorgid%3df3f230c0-ddc6-e911-837e-0017fb000002&wct=2019-09-04T11%3a03%3a41Z&wauth=urn%3afederation%3aauthentication%3awindows

Bring up the ADFS management console and edit Primary Authentication Methods to include Windows Authentication and restart ADFS