Skip to main content

Troubleshooting

This document covers common troubleshooting scenarios for Exchange integration with Dime.Scheduler, including authentication, connectivity, and data synchronization issues.

Authentication Failures​

Azure AD App Configuration Issues​

Symptoms:

  • "Invalid client" or "Invalid client secret" errors
  • "AADSTS700016: Application not found in the directory"
  • "Insufficient privileges to complete the operation"
  • Authentication fails despite credentials appearing correct

Cause​

Incorrect Azure AD app registration configuration, including wrong Client ID, Client Secret, Tenant ID, or missing API permissions.

Solution​

Step 1: Verify Client ID, Client Secret, and Tenant ID​

These are the most frequently reported configuration issues:

  1. Double-check the Client ID (Application ID):

    • Go to Azure Portal > Azure Active Directory > App registrations
    • Find your Dime.Scheduler app
    • Copy the Application (client) ID - this is your Client ID
    • Ensure this matches exactly what's configured in Dime.Scheduler connector settings

  2. Verify the Tenant ID:

    • In the same Azure AD app overview page, copy the Directory (tenant) ID
    • Ensure this matches exactly what's configured in Dime.Scheduler
    • Common mistake: Using the wrong tenant ID if you have multiple tenants

  3. Check or regenerate the Client Secret:

    • Go to Certificates & secrets in your Azure AD app
    • Check if the secret has expired (secrets expire after 6, 12, or 24 months)
    • If expired or unsure, create a new client secret
    • Copy the secret value (not the Secret ID) immediately - you can only see it once
    • Update the secret in Dime.Scheduler connector configuration
warning

Client secrets expire! Set a reminder to rotate secrets before they expire to avoid service interruptions.

Step 2: Verify API Permissions​

This is a frequently reported issue. The Azure AD app must have the correct permissions assigned:

  1. Go to your Azure AD app > API permissions
  2. Ensure the following permissions are added:
    • Microsoft Graph:
      • Calendars.ReadWrite (Application permission) - Required for calendar sync
      • MailboxSettings.ReadWrite (Application permission) - Required for mailbox configuration
      • User.Read.All (Application permission) - Required to read user information
  3. After adding permissions, click Grant admin consent for [Your Organization]
    • This step is critical and often forgotten
    • Without admin consent, the permissions won't take effect
Important

After adding or modifying permissions, you must grant admin consent. Simply adding the permissions is not enough.

Step 3: Update Dime.Scheduler Configuration​

  1. Go to the Exchange setup page in Dime.Scheduler
  2. Enter the correct values in the Microsoft Entra ID section:
    • Client ID: Application (client) ID from Azure AD
    • Client Secret: The secret value (not the secret ID)
    • Tenant ID: Directory (tenant) ID from Azure AD
  3. Save the configuration to apply the changes