Azure AD Connection Issues

Troubleshoot common Microsoft Entra ID connection errors and permission issues in fixSignatures.

“Insufficient privileges” Error

Cause: Admin consent has not been granted for the required API permissions.

Solution:

1. Go to Azure Portal
2. Navigate to Microsoft Entra ID → App registrations
3. Select your fixSignatures app
4. Go to API permissions
5. Click Grant admin consent for [Your Organization]
6. Confirm by clicking Yes
7. Wait for all permissions to show green checkmarks
8. Return to fixSignatures and click Test Connection

“Invalid client secret” Error

Cause: The client secret has expired, been deleted, or was entered incorrectly.

Solution:

1. Go to Azure Portal → Your app registration
2. Navigate to Certificates & secrets
3. Check if any secrets exist and their expiration dates
4. If expired or missing, click + New client secret
5. Enter a description and choose expiration (we recommend 24 months)
6. Click Add
7. Immediately copy the Value (it won’t be shown again)
8. In fixSignatures, go to Settings → Microsoft 365 Setup
9. Click Edit and update the Client Secret
10. Click Save, then Test Connection

“Invalid tenant ID” or “Invalid client ID” Error

Cause: The Tenant ID or Client ID was copied incorrectly or the app registration was deleted.

Solution:

1. Go to Azure Portal → Your app registration
2. On the Overview page, find:
   • Application (client) ID – This is your Client ID
   • Directory (tenant) ID – This is your Tenant ID
3. Copy these values carefully (use the copy button)
4. In fixSignatures, update the configuration with the correct values
5. Click Save, then Test Connection

“Consent required” Error

Cause: New permissions were added but admin consent wasn’t granted for them.

Solution:

1. Go to Azure Portal → Your app registration → API permissions
2. Look for any permissions without a green checkmark
3. Click Grant admin consent for [Your Organization]
4. Confirm and wait for all permissions to show green checkmarks

Users Not Syncing

If the connection works but users aren’t appearing, check these common causes:

Allowed Domains Filter

If you’ve set Allowed Domains, only users with those email domains will sync:

1. Go to Settings → Microsoft 365 Setup
2. Check the Allowed Domains setting
3. Either add the missing domain or clear the field to sync all domains
4. Click Save, then Sync Users Now

User Has No Email

Users without a valid email address in Microsoft Entra ID won’t be synced:

• Check the user’s profile in Microsoft Entra ID
• Ensure they have a value in the “Mail” or “UserPrincipalName” field

Missing User.Read.All Permission

Verify the app has the required permission:

1. Go to Azure Portal → Your app registration → API permissions
2. Confirm User.Read.All is listed with type “Application”
3. Confirm it has admin consent (green checkmark)

Test Connection Fails

If “Test Connection” fails without a specific error message:

• Check network connectivity – Ensure your server can reach Microsoft’s APIs
• Verify all three credentials – Tenant ID, Client ID, and Client Secret must all be correct
• Check for typos – Extra spaces or newlines in the credential fields can cause failures
• Try a new secret – Create a fresh client secret and update the configuration

Required Permissions Reference

fixSignatures requires these Microsoft Graph API permissions:

Permission	Type	Purpose
User.Read.All	Application	Read all user profiles
Group.Read.All	Application	Read group memberships

Both permissions require admin consent.

Still Having Issues?

If you’ve tried all the above and still can’t connect:

1. Take a screenshot of the error message
2. Take a screenshot of your app’s API permissions page in Azure
3. Contact support with these details