If your company lives in Microsoft Teams, security alerts should show up there. Safeguard supports two documented ways to connect. Both are send only in practice, since the docs say Teams is send-only.
What it is
A Teams integration lets Safeguard post notifications to a channel. Inbound commands are not available for Teams.
How to use it
Open Settings → Integrations and click Connect on the Teams tile. On the Credentials step enter a unique Integration Name, an optional Description and an Authentication Type.
- Incoming Webhook (Send Only),
WEBHOOK: paste the webhook URL, which starts withhttps://outlook.office.com/webhook/. - Bot Framework (Full Access),
BOT_FRAMEWORK: enter the Microsoft Tenant ID, the App ID (Client ID) and the App Secret (Client Secret). All three are required together.
Click Next. Safeguard validates the credentials before listing anything. With Bot Framework you then choose a Team and a Channel within it. With a webhook there is nothing to choose beyond an optional display name.
Troubleshooting
If no teams appear, the Azure AD app may not have been granted access to the tenant or to the specific teams. Ask your Microsoft 365 admin to check that grant. The docs do not list the exact Graph permissions, so do not assume them.
Good practice
A webhook is simpler and has a smaller blast radius. Pick Bot Framework only if you need the team and channel picker. Store the app secret in your password manager, not in a chat message.
All integrations send everything to one default channel today. Per-event routing exists in the data model but has no screen.
Quick check
Which three values does Bot Framework require?
Microsoft Tenant ID, App ID (Client ID) and App Secret (Client Secret), all together.
