Implementing OAuth 2.0 for MS Dynamics Customers

Modified on Wed, 8 Jan at 4:28 AM

Introduction

This document provides a step-by-step guide for MS Dynamics customers to implement OAuth 2.0 authentication for seamless integration with SupportLogic.


Actions to be Performed by the Customer Admin

1. Register the Application in Azure Portal

  1. Open the Azure Portal.

  2. Navigate to App Registrations.

  3. Click on New Registration

  4. On the App Details page:

    • Enter SupportLogic Plugin under Name.

    • Choose Single Tenant under the Supported Account Type.

    • Click on Register.

  5. After successful creation of the app:

    • Note down the Application ID and Directory ID for later use.


2. Add API Permissions

  1. Open the API Permissions tab.

  2. Click on Add a permission to add Dynamics CRM to the permissions list.

  3. Select Dynamics CRM from the list.

  4. Choose Delegated Permissions:

    • Select user_impersonation.

    • Click on Add Permissions.

3. Create a Client Secret

  1. Open the Certificates & Secrets tab.

  2. Click on New Client Secret.

  3. In the Client Secret form:

    • Enter SupportLogic Plugin under Name.

    • Set the Expiry Time to Never.

    • Click on Add.

  4. Copy the Client Secret and note it down for later use.

    • Note: The secret will not be visible after refreshing the page.

4. Configure the Application User in Dynamics 365

  1. Navigate to Advanced Settings → System → Security → Users in the Dynamics 365 Instance.

  2. Click on New Application User.

  3. Fill in the Application ID in the form:

    • Other fields will populate automatically.

  4. Under Roles, select System Administrator.

  5. Click on Save.


Final Steps

Verify the following values and forward them to SupportLogic for the backend integration:

  • Dynamics 365 Instance URL

  • Application (Client) ID

  • Directory (Tenant) ID

  • Client Secret



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article