If your Dynamics 365 Customer Engagement organization is setup to authenticate with OAuth, follow the steps below to setup an OAuth token.

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.
   • This is specific to your SmartConnect region, so it will vary slightly depending on that.  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:

1. Login to login.smartconnect.com if not already.
2. Navigate to Connections and click the Create Connection button (or edit an existing CE connection).
3. Select Dynamics 365 Customer Engagement.
4. Enter a description for the connector and check the “Use OAuth to Connect” and “Use Token Authentication” options.
   • 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.
5. 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.
   • 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.
6. 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.
7. 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.
8. Click Validate.  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.
9. After successful validating you will be redirected back to the Dynamics 365 Customer Engagement connector and can now choose your organization.
   • Note: If using the crm or crm9 regions and the “Use Regional Discovery Service” is checked, the connection setup is complete after validating and choosing an organization.
10. Once the organization is selected, the “Enable Regional Access” must be clicked to complete the setup.
    
    1. Note: The Customer Engagement connector cannot connect to organizations across different regions. If there are organizations across regions, a different instance of the CE connector will need to be setup for each region.
11. After successfully completing the validation and access steps, you can now save the connector.