Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email support@alteryx.com for assistance.

Alteryx Designer Knowledge Base

Definitive answers from Designer experts.

How to register and create Dynamics CRM Application on Azure

DiganP
Alteryx Alumni (Retired)
Created

How To Register and Create Dynamics CRM Application on Azure

Prerequisites

The user who is registering the application must have a user account with System Administrator security role and the global administrator role for the Azure subscription. An Azure subscription for application registration is required. A trial account will also work.

Procedure

1) Sign into the Azure portal using an account with administration permission. You use an account within the same tenant (subscription) as the Dynamics CRM.

2) After logging into the Azure portal, click on the Azure Active Directory > App registrations > New registration.

DiganP_0-1576626517560.pngDiganP_1-1576626529179.png

3)In the Register an application page, we need to enter in a couple of things.

  • Name: Enter your application name that will be shown to users.
  • Supported account types: This is something that the Azure admin should know and has been configured.
    • If your Azure Active Directory is set up with a single tenant, select Accounts in this organizational directory only (.com only - Single tenant)
    • If your Azure Active Directory is set up with a multitenant, select Accounts in any organizational directory (Any Azure AD directory - Multitenant)
  • Redirect URI: Make sure it is set to Web and the URI is https://login.live.com/oauth20_desktop.srf
    • Note, this is very important. If it is not configured correctly, the user won’t be able to log in. This URI applies to the rest of the connectors such as Azure Data Lake Tools, OneDrive Tools and PowerBI Output Tools.
  • Click Register.

DiganP_2-1576626631628.png

4)After you press register, it will take you to the overview page. This page a summary of the application settings. Here, we are interested in 2 things:

  • Application (client) ID – This is an unique ID assigned to the application we just created.
  • Directory (tenant) ID – This is an unique ID for the tenant that is assigned to your Azure Active Directory. Make sure this is the correct tenant ID, it should match the Tenant ID of the end users.

Copy these 2 IDs to a clipboard for later use.

DiganP_3-1576626672281.png

5)On the left, click on Manifest. In the Manifest editor, set the allowPublicClient property to true and click save. This will allow the client to have access to this application.

DiganP_5-1576626694639.png

6)Select API permissions tab, click on Add a permission.

DiganP_6-1576626705064.png

In the Request API permissions console, under Microsoft APIs, click on the Dynamics CRM icon. Select the Delegated permissions and add the user_impersonation permission.

DiganP_13-1576626917026.pngDiganP_14-1576626950015.png

Your API permissions tab should look something like this:

DiganP_8-1576626730246.png

7)Click on the Certificates & secrets tab. Under Client secrets, click on New client secret.

DiganP_9-1576626741212.png

Pick the appropriate length of the secret and press add.

DiganP_10-1576626749749.png

A new key will be automatically generated for you. This client secret will be masked when revisited later so it is recommend to copy this into the notepad as well.

Summary

We successfully set up the Dynamics CRM application. Keep in mind, these 4 things are needed to connect to the Dynamics CRM Input and Dynamics CRM Output tool.

  • Organization URL: This is provided to you when you log into the dynamics platform. For ex: https://[Organization Name].crm.dynamics.com/
  • Azure Active Directory tenant ID: This is found in the application summary page (step 4).
  • Client ID: This is found in the application summary page (step 4).
  • Client secret key: This is found in the Certificates & secrets (step 7).

Common Issues

Error: no attribute 'populate_token_attributes'

The reply url specified in the request does not match the reply urls

Additional Resources

No ratings