Skip to main content

Troubleshooting M365 Connection

Resolve common Microsoft 365 integration issues

troubleshootingMicrosoft 365errorsconnection

Troubleshooting M365 Connection

Resolve common issues with the Microsoft 365 integration.

Connection Test Failures

Authentication Failed

Error: "Authentication failed" or "Invalid client"

Causes:

  • Incorrect Client ID
  • Invalid Client Secret
  • Wrong Tenant ID
  • Expired secret

Solutions:

  1. Verify Client ID

    • Open Azure Portal > App registrations
    • Confirm Application (client) ID matches
  2. Regenerate Client Secret

    • Go to Certificates & secrets
    • Create new secret
    • Update in Securtea
  3. Check Tenant ID

    • Verify Directory (tenant) ID
    • Ensure app is in correct tenant

Permission Denied

Error: "Insufficient privileges" or "Access denied"

Causes:

  • Missing API permissions
  • Admin consent not granted
  • Conditional Access blocking

Solutions:

  1. Check Permissions

    • Open app in Azure Portal
    • Verify all required permissions added
    • Look for green checkmarks
  2. Grant Admin Consent

    • Click "Grant admin consent"
    • Confirm with Global Admin
  3. Check Conditional Access

    • Review if CA policies block service principals
    • Exclude the app if needed

Connection Timeout

Error: "Connection timed out" or "Service unavailable"

Causes:

  • Network issues
  • Microsoft service outage
  • Firewall blocking

Solutions:

  1. Check Microsoft Status

    • Visit status.office365.com
    • Check for Graph API issues
  2. Verify Network

    • Ensure graph.microsoft.com is accessible
    • Check firewall rules
  3. Retry Later

    • Temporary issues may resolve
    • Wait 15-30 minutes and retry

Data Sync Issues

Data Not Updating

Problem: Dashboard shows stale data

Causes:

  • Sync not running
  • API throttling
  • Partial failure

Solutions:

  1. Force Refresh

    • Go to integration settings
    • Click "Refresh Data"
    • Wait for completion
  2. Check Sync Logs

    • Review sync history
    • Look for errors
  3. Verify Schedules

    • Confirm monitoring schedules active
    • Check next scheduled sync

Missing Resources

Problem: Expected data not appearing

Causes:

  • Permission not granted
  • Resource type not supported
  • Filter excluding data

Solutions:

  1. Check Permissions

    • Verify permission for that resource type
    • Add missing permissions
  2. Check Feature Support

    • Some resources require specific licenses
    • Review supported resources
  3. Check Filters

    • Review any scope filters
    • Ensure resource isn't excluded

Partial Data

Problem: Some data present, some missing

Causes:

  • Mixed permission grants
  • Propagation delay
  • Resource-specific issues

Solutions:

  1. Review Sync Status

    • Check which resources succeeded
    • Identify failing resources
  2. Wait for Propagation

    • New permissions may take time
    • Wait up to 24 hours
  3. Check Individual Resources

    • Some may require additional setup
    • Review resource-specific docs

Specific Errors

AADSTS Error Codes

Common Azure AD error codes:

CodeMeaningSolution
AADSTS700016App not foundVerify Client ID
AADSTS7000215Invalid secretRegenerate secret
AADSTS65001No consentGrant admin consent
AADSTS50076MFA requiredConfigure CA exclusion
AADSTS50079User registration requiredCheck policy

Graph API Errors

Common Graph errors:

ErrorMeaningSolution
401 UnauthorizedAuth failedCheck credentials
403 ForbiddenNo permissionGrant permission
404 Not FoundResource missingVerify resource exists
429 Too Many RequestsRate limitedWait and retry
503 Service UnavailableMS outageWait for resolution

Verification Steps

Test Authentication

Verify app can authenticate:

  1. Go to Integrations > Microsoft 365
  2. Click Test Connection
  3. Review results

Test Permissions

Verify specific permission works:

  1. Run a compliance assessment
  2. Check which controls pass/fail
  3. Permission issues show as errors

Check Azure Logs

Review access attempts in Azure:

  1. Open Azure AD > Sign-in logs
  2. Filter by Application
  3. Look for errors or failures

Getting Help

Before Contacting Support

Gather:

  • Error messages (screenshots)
  • Tenant ID
  • App registration Client ID (not secret)
  • Steps to reproduce
  • When the issue started

Support Channels

Microsoft Support

For Azure AD issues:

  • Microsoft 365 admin center
  • Azure support ticket
  • Microsoft community forums

Preventive Measures

Regular Verification

Periodically:

  • Test connection
  • Review permissions
  • Check secret expiration
  • Monitor sync status

Secret Management

Prevent authentication failures:

  • Set calendar reminder before expiration
  • Rotate secrets proactively
  • Keep old secret until new verified

Permission Documentation

Document your configuration:

  • List all permissions granted
  • Note any customizations
  • Record admin consent date

What's Next?

Global Search

Search for pages, settings, and documentation