Knowledge Base

If your Dynamics 365 Customer Engagement organization is setup to authenticate with OAuth, follow the steps below to setup an OAuth token. Required SC version: 21.1.0.366 or higher Setting up the application in Azure:

1. Navigate to portal.azure.com
2. Search for App registrations in the top search bar and select App registrations.
3. Click New Registration and enter a name for the application.
4. Choose the appropriate Supported Account Type, most companies will use “Accounts in this organizational directory only”.
5. For the Redirect URI, choose Web and enter the correct URL found in the SmartConnect connection window.
   • When setting up an Oauth CRM/CE connection, the redirect URL will be displayed in the connection window.
     
6. Click Register.
7. Click “Certificates & secrets” in the navigation on the left.
8. Click “New client secret”.
9. Give the secret a description and choose how long you want the secret to last.  It is important to note that when the secret expires any connections using this secret will no longer connect successfully until a new secret is generated and used in the connection. Make sure to have a process in place for someone to create another secret and update any SmartConnect connections prior to the secret expiring in the future.
   
10. Click Add to generate the new secret. Copy and save the Value somewhere as it will not be fully visible again once you navigate away from the Azure Portal.
    
11. Click on “API Permission” in the navigation bar on the left.
12. Click “Add a permission” and choose Dynamics CRM.
13. Select Delegated permission if it is not already and enable user_impersonation and click Add permissions.
    
14. Click on Overview in the navigation bar on the left.
15. Copy and save the “Application (client) ID” value.
16. With the Application ID and the Secret Value copied and saved from the application setup, the CRM/CE connection in SmartConnect can now be configured.

Setting up the connector in SmartConnect 21:

1. Login to the SmartConnect app if not already.
2. Navigate to Connections and click the Create button (or edit an existing CE connection).
3. Select Dynamics 365 Customer Engagement.
4. Enter a description for the connection.
5. For the CRM Server, enter your server address excluding the organization name. This will vary depending on which region CRM/CE is located in – ie. crm4.dynamics.com, crm.dynamics.com, crm11.dynamics.com, etc.
6. Check the “Use OAuth 2.0” option.
   • Note: If using the main “crm” region, or the “crm9” region, also check the option for “Use Regional Discovery”. Those regions have a local discovery service that simplifies the connection process.
7. Enter the same Application Id from the application that was registered in the Azure portal. It can be found on the Overview page in Azure Portal.
8. Enter the Client Secret from the application, if the secret value was not saved when registering the application then a new secret and value will need to be created.
   
9. Click Verify.  This will start the OAuth process and you will be directed to a Microsoft login if not already logged in.  If you were still logged in, you will be asked to grant permissions.  Click accept to grant the permissions.  If your user does not have the proper permissions, you will need to have an admin user grant the permissions.
10. Click the “Get Access Token” button to continue the validation process.
    
11. Click the Refresh button to pull a list of organizations and select one of them to continue.
    • Note: At this point if you are using the crm or crm9 region with the “Use Regional Discovery” option marked, the setup is complete and you can save and close the window. If using a different region the steps below will need to be followed to complete another OAuth process.
12. Click “Verify Organization”. This will start another OAuth process for the organization selected (Microsoft requires authentication at both the discovery and tenant level now) and you will be directed to a Microsoft login if not already logged in. Permissions should already be granted from the steps above so once the page refreshes you can continue within the app.
13. Click “Get Organization Token” as the final step to complete the authentication process. The connection window can now be saved and closed.
    • Note: The “Allow Meta Updates” and “Allow Advanced Messages” options can also be checked, those options refer to enabling additional functionality within integrations using this connection.
      

If your Dynamics 365 Customer Engagement organization is setup to authenticate with OAuth, follow the steps below to setup an OAuth token. Required SC version: 20.18.1.56 or higher Setting up the application in Azure:

1. Navigate to portal.azure.com
2. Search for App registrations in the top search bar and select App registrations.
3. Click New Registration and enter a name for the application.
4. Choose the appropriate Supported Account Type, most companies will use “Accounts in this organizational directory only”.
5. For the Redirect URI, choose Web and enter the correct URL based on deployment/region:
   • SmartConnect 2018.1.56 – https://loginsmartconnect.azurewebsites.net/oauth/genericrestredirect
   • SmartConnect 2018.1.57 – https://loginsmartconnect.azurewebsites.net/oauth/genericrestredirect
   • SmartConnect 2018.1.58 – https://login.smartconnect.com/oauth/genericrestredirect
   • When setting up an Oauth CRM/CE connection, the redirect URL will be displayed in the connection window.
     
6. Click Register.
7. Click “Certificates & secrets” in the navigation on the left.
8. Click “New client secret”.
9. Give the secret a description and choose how long you want the secret to last.  It is important to note that when the secret expires any connections using this secret will no longer connect successfully until a new secret is generated and used in the connection. Make sure to have a process in place for someone to create another secret and update any SmartConnect connections prior to the secret expiring in the future.
   
10. Click Add to generate the new secret. Copy and save the Value somewhere as it will not be fully visible again once you navigate away from the Azure Portal.
    
11. Click on “API Permission” in the navigation bar on the left.
12. Click “Add a permission” and choose Dynamics CRM.
13. Select Delegated permission if it is not already and enable user_impersonation and click Add permissions.
    
14. Click on Overview in the navigation bar on the left.
15. Copy and save the “Application (client) ID” value.
16. With the Application ID and the Secret Value copied and saved from the application setup, the CRM/CE connection in SmartConnect can now be configured.

Setting up the connector in SmartConnect 2018:

1. Login to the SmartConnect app if not already.
2. Navigate to Setup – Setup, and go to the Connector Setup tab.
3. Open the “SmartConnect Dynamics CRM Connector”.
   
4. For the CRM Server, enter your server address excluding the organization name. This will vary depending on which region CRM/CE is located in – ie. crm4.dynamics.com, crm.dynamics.com, crm11.dynamics.com, etc.
5. Set the Authentication Type to “Microsoft Online Federation”
6. Check the “Use OAuth” option.
   • Note: If using the main “crm” region, or the “crm9” region, also check the option for “Use Regional Discovery Service”. Those regions have a local discovery service that simplifies the connection process.
7. Enter the same Application Id from the application that was registered in the Azure portal. It can be found on the Overview page in Azure Portal.
8. Enter the Client Secret from the application, if the secret value was not saved when registering the application then a new secret and value will need to be created.
   
9. Click Verify.  This will start the OAuth process and you will be directed to a Microsoft login if not already logged in.  If you were still logged in, you will be asked to grant permissions.  Click accept to grant the permissions.  If your user does not have the proper permissions, you will need to have an admin user grant the permissions.
10. Click the “Get Access Token” button to continue the validation process.
    
11. Click the Refresh button to pull a list of organizations and select one of them to continue.
    • Note: At this point if you are using the crm or crm9 region with the “Use Regional Discovery” option marked, the setup is complete and you can save and close the window. If using a different region the steps below will need to be followed to complete another OAuth process.
12. Click “Verify Organization”. This will start another OAuth process for the organization selected (Microsoft requires authentication at both the discovery and tenant level now) and you will be directed to a Microsoft login if not already logged in. Permissions should already be granted from the steps above so once the page refreshes you can continue within the app.
13. Click “Get Organization Token” as the final step to complete the authentication process. The connection window can now be saved and closed.
    • Note: The other checkbox options can also be marked, those options refer to enabling additional functionality and features within integrations using this connection.