Azure AD App Setup Instructions for Dynamics CRM

1. Log in to Azure Portal

  1. Open Azure Portal.
  2. Log in with an account that has administrative privileges for your organization's Azure AD tenant.

2. Register a New Azure AD Application

  1. Navigate (in another tab or window) to Azure Active Directory and App Registrations.
  2. Click on + New registration.
  3. Enter the following details:
    • Name: Enter a meaningful name, e.g., SyncBox Dynamics CRM Connector.
    • Supported account types: Choose Accounts in this organizational directory only.
    • Redirect URI: Leave this blank.
  4. Click Register.

3. Gather Required Information

  1. Go to the Overview tab of your app registration.
  2. Copy the following values to the SyncBox application:
    • Application (client) ID to the Application ID field
    • Directory (tenant) ID to the Tenant ID field

4. Configure API Permissions

  1. Go to the API Permissions tab of the Azure Application Registration.
  2. Click + Add a permission.
  3. Select Dynamics CRM.
  4. Choose Delegated permissions (default selected) and add the following permissions:
    • user_impersonation (Allows the application to access Dynamics CRM as the signed-in user).
  5. Click Add permissions.
  6. Grant admin consent:
    • Click on the Grant admin consent for [your tenant name] button.
    • Confirm the consent.

5. Create a Client Secret

  1. Navigate to the Certificates & Secrets tab in the Azure AD App Registration.
  2. Under Client secrets, click + New client secret.
  3. Enter a description (e.g., SyncBox Secret) and choose an expiration period (e.g., 6 months, 1 year, or 2 years).
  4. Click Add.
  5. Copy the Value of the client secret. This value will not be shown again, so ensure you store it securely.
  6. Paste the copied secret into the Client Secret field in SyncBox
Note:Ensure the client secret value is securely stored and accessible only to authorized personnel. If permissions or access are not working as expected, verify that admin consent has been granted and that the app registration permissions match the required scopes.