5 minute read

In previous article, we have looked at the possibility to connect Dynamics 365 on-premise directly with Azure AD, which is on one hand really cool, on the other, it doesn’t provide all the features like mobile apps integration. In this article, we are going to explore a production ready solution by leveraging Active Directory Federation Service and Azure AD as a Claims Provider Trust. Starting off, I am going to assume you already have ADFS installed and set up with Dynamics 365, if not I suggest starting here.

Identities in Dynamics 365

Basically, you have two kinds of identities in Dynamics 365 - identities sourced from Active Directory and identities sourced from a federation provider. By default, and in most simple deployments with ADFS, you use the first one - user has an account in Active Directory and is created in Dynamics 365 with username like AD\Jan Hajek which is their logon name into the AD. What happens on background in this case, is that Dynamics has a mapping table in MSCRM_CONFIG database, which is called SystemUserAuthentication and it basically maps the user’s SID to the identity in Dynamics 365. That is why it is super important, to include the user’s SID in the claims (as the tutorial mentioned above states), else, even if you include the UPN or logon name, the user won’t get mapped. Second option is sourcing the identity from a federation provider - ADFS. If you are a larger company which for example allows external users from other organizations to access their Dynamics instance, you have two options - either go with the option above and create a special account for that user in your directory - which may have certain negative security impact (like if the person gets fired from their company and their IT forgets to mention it, they still get to keep the account with all permissions etc.) or you can add their ADFS instance as a trusted claims provider for the Dynamics 365 relying party. The user will then get a prompt to choose which organization they belong to and be authenticated by proper ADFS instance. In this case, the user doesn’t have to exist in your Active Directory, their account is only in the specific Dynamics 365 instance’s database and no Active Directory is involved on your side for user authentication. Like mentioned above, the same SystemUserAuthentication table is used to map the UPN (User Principal Name) to the correct Dynamics account.

Why integrate with Azure AD?

I have already mentioned this in the previous article, but to recap - Azure AD adds enhanced security, logging and much more to the authentication and authorization process. It can help you easily enforce conditional access, multi-factor authentication and others while using it as your primary identity provider. Thanks to this, you don’t have to use Azure AD Connect to synchronize users from your Active Directory to Azure Active Directory and therefor you don’t need to keep users in your Active Directory at all and use pure cloud-only Azure AD instance. You also get a great set of B2B functionalities.

Why is ADFS still needed?

This has been already mentioned before - however to recap this as well: Dynamics can directly integrate with Azure AD so no ADFS is needed, however, you will loose the ability to use both desktop and mobile applications because their application IDs are reserved for Dynamics 365 Online usage.

What needs to get changed?

We are going to start off by adding Azure Active Directory as a claims provider trust into ADFS. It is basically reverse process of configure Azure AD to accept ADFS as the claims provider. Here’s what you have to do:

  1. Create a new application in Azure AD using Azure Portal or Azure AD Portal.
  2. Configure the Application Identifier to your ADFS’s address, for example: https://sts.crmlabs.tntg.cz
  3. Configure Reply URLs for the application to include your ADFS’s address - for example: https://sts.crmlabs.tntg.cz/adfs/ls
  4. Tip: You may want to set the Home page URL in application’s Properties to your CRM address - for example https://1box-03.crmlabs.tntg.cz in order for the user to be redirected to your Dynamics instance when clicking the application in their App Launcher or My Apps.
  5. In ADFS console, create a new Claims Provider Trust.
  6. Choose Import data about the claims provider… and put in your directory’s Federation Metadata’s address - for example: https://login.microsoftonline.com/thenetw.org/FederationMetadata/2007-06/FederationMetadata.xml (you can get this endpoint for your tenant using Endpoints _button on the _App Registration page in AAD).
  7. Specify a Display name, for example Azure AD and add the trust.
  8. Now you can use Azure AD as a claims provider in your ADFS.
  9. One more thing that you need to do is to configure the UPN claim - since Azure AD is not going to send it to you, because without it, Dynamics wouldn’t identify the user correctly (alternatively you could modify IdentityClaim in Dynamics database like mentioned in previous article).
  10. So after having the Trust created, go ahead and click Edit Claim Rules…
  11. Add a new rule from template Transform an Incoming Claim and set Incoming claim type to Name and Outgoing claim type to UPN.

Configuring relying party trust

If you have set up the Relying Party correctly, you already have the UPN passthrough rule created for the relying party. If not, look at Microsoft’s tutorial. Now we have to enable the Relying Party Trust to accept claims from Azure AD, we will have to use PowerShell (on the ADFS server) for this. First, we are going to check your relying party configuration:

Get-ADFSRelyingPartyTrust -Name "<your CRM IFD Relying Party Name>

When you check ClaimsProviderName property, you should have Active Directory there. Now if you want to add Azure AD alongside AD, you would execute:

Set-AdfsRelyingPartyTrust -TargetName "<your CRM IFD Relying Party Name>" -ClaimsProviderName @{add="Azure AD"}

If you want to use exclusively Azure AD only, you would execute following, however, beware before executing this (read below):

Set-AdfsRelyingPartyTrust -TargetName "<your CRM IFD Relying Party Name>" -ClaimsProviderName @("Azure AD")

Before you use exclusively Azure AD, you should modify at least one system administrator’s User Name in Dynamics to match their User Principal Name in Azure AD, so for example: jan.hajek@thenetw.org, else no one will be able to sign in. Generally, you should change your user’s User Names in Dynamics first before migrating to Azure AD login. If you have same UPNs in Azure AD and Active Directory, their logins should work both logging through Azure AD and Active Directory claims providers.



I am challenged with step 2, “Configure the Application Identifier to your ADFS’s address, for example: https://sts.crmlabs.tntg.cz”

The Application Identifier does not appear to be editable (it is a GUID). The only way I can change this is to setup SAML authentication – is that part of the process?

Doug Beebe

I’ve been looking for this solution, although our situation is slightly different. We are on a roadmap to get to the online version of Dynamics 365, but as interim step will be lifting our on-premise to an Azure Vnet. The ADFS notes make sense, but your steps on the App creation are a bit unclear to me and I’m trying to match with the Azure Portal. Do we create a Web App or are you talking about an App Registration within the Azure Active Directory service? Thanks again for this article!


Hi Jan,

I came across your article while researching a problem that I am currently troubleshooting. Although my scenario is different, perhaps this will help. I am trying to integrate Dynamics 365 on premise with Okta SSO using ws federation. In this scenario, Okta is providing the secure token service rather than ADFS. I did get it working, but only just. The web client connections are working, but the SDK connections all fail with a message: the authentication endpoint Username was not found on the configured Secure Token Service. I am guessing that “Username” is an endpoint specific to ADFS and the SDK connections submit the username to this endpoint, which does not exist in our case because we are using Okta. Perhaps if we add Okta as a Claims Provider Trust to ADFS, it will work. Do you have any ideas or have you done a similar implementation? I am doubtful that it is possible at this point.

Leave a Comment

Your email address will not be published. Required fields are marked *