Overview
The Security software can send alarms, events, and notifications directly to a Microsoft Teams channel using a Teams Workflow Webhook. This allows operators, administrators, and security personnel to receive real-time notifications within Microsoft Teams whenever important system events occur.
Examples include:
Door Forced Open
Door Held Open
Access Denied
Intrusion Alarm
Controller Offline
System Events
Custom Event Notifications
Notifications appear directly within a Teams channel and can optionally include a link back to the Security Software application for immediate investigation.
Prerequisites
Before configuring the integration, you must have:
A Microsoft Teams account
Permission to create Workflows within the desired Team
A Teams channel where notifications will be delivered
Creating a Teams Workflow Webhook
Step 1: Open Microsoft Teams
Launch Microsoft Teams and navigate to the Team and Channel where you want notifications to appear.
Step 2: Create a Workflow
Click the ... (More Options) button next to the channel.
Select Workflows.
Click Create Workflow.
If Workflows is not visible, search for Workflows using the Teams search bar.
Step 3: Select the Workflow Template
Search for:
Send webhook alerts to a channel
Select the template and click Next.
Step 4: Configure the Workflow
Select the Team.
Select the Channel.
Click Create Flow.
Microsoft Teams will generate a unique webhook URL.
Step 5: Copy the Webhook URL
After the workflow has been created, Teams will display a URL similar to:
https://prod-xx.westus.logic.azure.com/workflows/...
Copy the entire URL.
Important: This URL acts as a secret key. Anyone with this URL can send messages to your Teams channel.
Configuring the Software
System-Wide Notifications
Navigate to:
Configuration → System Settings
Select the Tools tab.
Scroll down to Teams Workflow Notification.
Enable Teams notifications.
Paste the Teams Workflow URL into the Teams URL field.
Save your changes.
Once configured, select system events can be delivered directly to the configured Microsoft Teams channel.
Configuring Event Notifications
The events that are sent to Microsoft Teams are configured within Log Manager.
Navigate to:
Configuration → Log Manager
Locate the event you wish to configure.
Review the Notify column.
The Notify field determines who will receive the notification:
System Administrator
Controller Group Administrator
Other configured recipients
When a Teams Workflow URL has been configured, notifications will be delivered to the appropriate Teams channel based on the Notify setting.
Testing the Integration
After saving the Teams Workflow URL:
Trigger a test event.
Verify the notification appears in the selected Teams channel.
A successful notification will display:
Event Title
Event Type
Date and Time
Optional link back to the Security Software application
Example Notification
Door Forced Open
Event Type: Door Forced Open
Time: 2026-06-22 2:15:43 PM
Open in Security Software
Troubleshooting
Notification Not Appearing
Verify that:
Teams notifications are enabled.
The Teams Workflow URL was copied completely.
The Workflow is enabled in Microsoft Teams.
The correct Team and Channel were selected.
The event has been configured for notification within Log Manager.
HTTP 200 Response but No Message Appears
This typically indicates that the Teams Workflow accepted the request but failed while processing it.
Open the Workflow in Microsoft Teams and review the Run History for additional details.
Workflow URL Changed
If a Workflow is deleted and recreated, Microsoft Teams generates a new webhook URL.
Update the Teams URL within the software and save the changes.
Security Considerations
Treat the Teams Workflow URL like a password.
Do not:
Share it publicly.
Post it on websites.
Include it in screenshots.
Email it to unauthorized users.
Anyone with the URL can submit messages to the configured Teams channel.
Additional Information
Microsoft Teams integration extends event awareness beyond the Security Operations Center (SOC) by delivering notifications directly to the personnel responsible for responding to incidents. This can improve response times, increase visibility, and help ensure critical events are not overlooked.