Socket can now send alerts and supply chain attack notifications to Microsoft Teams, with filters that route the right updates to each channel.
- Jeppe Hasseriis
Today, we’re excited to add Microsoft Teams as a notification channel in Socket. Security and engineering teams can now send organization alerts and supply chain attack campaign notifications directly to the Teams channels they already monitor, with filters that control exactly which events reach each destination.
When Socket finds something that needs attention, teams shouldn’t have to keep another dashboard open to find out. Microsoft Teams notifications bring relevant security activity into the flow of day-to-day work, so the right people can see it and respond faster.
Notifications arrive as structured Adaptive Cards with alert totals by severity, the number of affected repositories, a preview of individual findings, and a direct link back to the Socket dashboard.
Add Microsoft Teams as a notification channel
Microsoft Teams is now available alongside email in Settings → Integrations → Notifications. Owners and Admins can connect a Teams channel using a Microsoft Workflows incoming webhook, then use that destination in one or more notification subscriptions.
In Microsoft Teams, create a Workflows flow using the Post to a channel when a webhook request is received template and copy its HTTP POST URL. In Socket, click Create Channel, select Microsoft Teams, and add a channel name and the webhook URL.
When the channel is created, Socket sends a test Adaptive Card to verify the connection. A successful test marks it as Active and ready to receive notifications.
Route the right security activity to each channel
Once Microsoft Teams is connected, create a subscription to choose what Socket should send and where it should go. Subscriptions combine an event, a filter, and one or more destinations, giving teams precise control over the notifications that reach each channel.
For organization alerts, you can subscribe to alerts as they are created, changed, or cleared. Filters can narrow delivery by:
- Alert category, including supply chain risk, vulnerability, quality, maintenance, and license
- Severity and Socket priority
- Repository
Attack campaign notifications can be filtered by package ecosystem or affected repository. This makes it possible to send critical supply chain activity to a central security channel while routing repository-specific findings to the engineering teams responsible for them.
Get the signal without flooding the channel
A scan can surface many related alerts at once. Socket groups organization alert activity into digests before posting it to Microsoft Teams, helping teams see what changed without filling the channel with dozens of individual messages.
Each digest summarizes alerts by severity, shows how many repositories are affected, previews individual findings, and links directly to the Socket dashboard for investigation.
See whether an attack campaign affects your organization
When Socket publishes a new supply chain attack campaign, Microsoft Teams notifications can show whether affected packages are present in your organization.
If the campaign impacts your organization, the notification summarizes the attack, identifies the affected repositories, and links directly to the full campaign details so teams can begin investigating immediately.
Socket can also confirm when a campaign is not detected in your organization. The notification summarizes the threat, confirms that no monitored repositories contain affected packages, and links to the campaign details, giving security teams a clear answer without having to check each repository manually.
Available now
Microsoft Teams notifications are available now on Team, Business, and Enterprise plans. To get started, go to Settings → Integrations → Notifications in the Socket dashboard and create a Microsoft Teams channel.
See the notification documentation for complete setup instructions, subscription options, permissions, and troubleshooting.