Microsoft Teams Integration
Maintained by: Aether365 Team Audience: IT administrators Scope: Microsoft Teams webhook integration setup and usage
Aether365 can post scan results to a Microsoft Teams channel automatically when a scan completes or fails.
Setup
See the step-by-step setup guide at Setting Up Teams Alerts.
Message Format
When a scan completes, Aether365 posts an adaptive card to your Teams channel:
On scan complete:
✓ Compliance Scan Complete - Contoso Production
Security score: 87%
Passed: 74 | Failed: 11 | Skipped: 5
Critical failures: 1
High failures: 3
Medium failures: 5
Low failures: 2
→ View full resultsOn scan failure:
✗ Scan Failed - Contoso Production
The compliance scan could not complete.
Reason: [error message]
→ View detailsMultiple Tenants
If you have multiple Microsoft 365 tenants connected, the scan message includes the tenant label so you can identify which tenant the results belong to.
Using Different Webhooks Per Tenant
Currently, one Teams webhook is configured per Aether365 account and applies to all connected tenants. If you need per-tenant routing, use the REST API to build a custom notification layer.
Troubleshooting
No message appears after a scan:
- Verify the webhook URL is correct in Settings > Notifications
- Check that the Connector or Workflow is still active in Microsoft Teams (webhooks can be deleted by Teams admins)
- Verify the Teams channel still exists
- Check that
teamsOnCompleteis enabled in notification settings
Message appears but content is truncated: This can happen if the Teams channel has a message size limit configured by your Teams admin. Contact your Teams administrator.
Webhook request rejected with 403: The webhook has been disabled or deleted. Create a new incoming webhook in Teams and update the URL in Aether365.