Troubleshooting M365 Connection
Resolve common Microsoft 365 integration issues
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:
-
Verify Client ID
- Open Azure Portal > App registrations
- Confirm Application (client) ID matches
-
Regenerate Client Secret
- Go to Certificates & secrets
- Create new secret
- Update in Securtea
-
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:
-
Check Permissions
- Open app in Azure Portal
- Verify all required permissions added
- Look for green checkmarks
-
Grant Admin Consent
- Click "Grant admin consent"
- Confirm with Global Admin
-
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:
-
Check Microsoft Status
- Visit status.office365.com
- Check for Graph API issues
-
Verify Network
- Ensure graph.microsoft.com is accessible
- Check firewall rules
-
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:
-
Force Refresh
- Go to integration settings
- Click "Refresh Data"
- Wait for completion
-
Check Sync Logs
- Review sync history
- Look for errors
-
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:
-
Check Permissions
- Verify permission for that resource type
- Add missing permissions
-
Check Feature Support
- Some resources require specific licenses
- Review supported resources
-
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:
-
Review Sync Status
- Check which resources succeeded
- Identify failing resources
-
Wait for Propagation
- New permissions may take time
- Wait up to 24 hours
-
Check Individual Resources
- Some may require additional setup
- Review resource-specific docs
Specific Errors
AADSTS Error Codes
Common Azure AD error codes:
| Code | Meaning | Solution |
|---|---|---|
| AADSTS700016 | App not found | Verify Client ID |
| AADSTS7000215 | Invalid secret | Regenerate secret |
| AADSTS65001 | No consent | Grant admin consent |
| AADSTS50076 | MFA required | Configure CA exclusion |
| AADSTS50079 | User registration required | Check policy |
Graph API Errors
Common Graph errors:
| Error | Meaning | Solution |
|---|---|---|
| 401 Unauthorized | Auth failed | Check credentials |
| 403 Forbidden | No permission | Grant permission |
| 404 Not Found | Resource missing | Verify resource exists |
| 429 Too Many Requests | Rate limited | Wait and retry |
| 503 Service Unavailable | MS outage | Wait for resolution |
Verification Steps
Test Authentication
Verify app can authenticate:
- Go to Integrations > Microsoft 365
- Click Test Connection
- Review results
Test Permissions
Verify specific permission works:
- Run a compliance assessment
- Check which controls pass/fail
- Permission issues show as errors
Check Azure Logs
Review access attempts in Azure:
- Open Azure AD > Sign-in logs
- Filter by Application
- 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
- Email: support@securtea.io
- In-app: Help > Contact Support
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?
- App Registration - Setup reference
- Permissions - Permission details
- Microsoft 365 Overview - Integration features