Overview#
This guide explains how to connect Microsoft Teams to WatchDog Security using OAuth authentication.Once connected, WatchDog can deliver organization-level notifications and alerts directly to Microsoft Teams channels through the Notification Center.Notifications are sent using the identity of the user who creates the integration, and can be configured to target specific Teams and channels.
What WatchDog Monitors#
This integration is used for notification delivery only. WatchDog does not collect or modify data within Microsoft Teams.
After the integration is connected, WatchDog can send Organization-level alerts from Notification Center
Requirements#
Before connecting the integration, ensure the following:You have access to Microsoft Teams
You're an Account Owner or Security Admin in WatchDog Security
The user connecting the integration is a member of the Team(s) where notifications will be sent
The Microsoft account used during authorization has access to the target Teams and channels
Important Behavior#
Understanding how notifications are delivered is critical for correct setup.
Notifications are sent using the identity of the user who connects the integration
The user must be a member of the Team and channel where alerts will be delivered
If the user is removed from the Team, notifications to that channel may fail
Channel visibility is limited to Teams the user has access to during setup
Connect Microsoft Teams to WatchDog Security#
2.
Navigate to Management → Integrations
5.
Sign in with your Microsoft account and review the requested permissions
6.
After authorization is completed, you will automatically be redirected back to WatchDog Security.
Initial Sync#
WatchDog will retrieve available Teams and channels
The integration is ready for use immediately after setup
Revoking Access#
To fully remove WatchDog access to Microsoft Teams, revoke access in both WatchDog and Microsoft.Step 1 — Disconnect in WatchDog#
1.
Log into WatchDog Security
2.
Navigate to Settings → Integrations
Step 2 — Remove OAuth Access in Microsoft#
This revokes OAuth permissions and prevents further message delivery.
Troubleshooting#
Verify:
The user who created the integration is still a member of the Team
The selected channel still exists
The integration is still connected