Integrating Alerts with Microsoft Teams

Overview

Microsoft Teams integration allows Server Scout to send real-time monitoring alerts directly to your team channels. This guide walks you through setting up a Teams Incoming Webhook connector and configuring Server Scout to deliver formatted notifications to your preferred channel.

Teams webhook integration uses Microsoft's connector framework, which differs from Slack's webhook format. Server Scout automatically handles the payload formatting to ensure your alerts display properly in Teams.

Creating a Teams Incoming Webhook

Step 1: Access Channel Connectors

1. Navigate to your desired Teams channel
2. Click the three dots (...) next to the channel name
3. Select Connectors from the dropdown menu
4. Search for "Incoming Webhook" in the connectors gallery

Step 2: Configure the Webhook

1. Click Add next to "Incoming Webhook"
2. Provide a descriptive name (e.g., "Server Scout Alerts")
3. Optionally upload a custom icon to identify Server Scout notifications
4. Click Create
5. Copy the generated webhook URL - you'll need this for Server Scout configuration

Important: Store this URL securely as it provides direct access to post messages in your channel.

Configuring Server Scout Notifications

Adding the Teams Webhook

1. Log into your Server Scout dashboard
2. Navigate to Settings → Notifications
3. Click Add New Notification Channel
4. Select Microsoft Teams from the channel types
5. Paste your webhook URL into the Webhook URL field
6. Assign a recognisable name for internal reference
7. Choose which alert types should trigger Teams notifications
8. Click Save Configuration

Notification Filtering

Configure which events trigger Teams alerts:

• Critical Alerts: System failures, service outages
• Warning Alerts: High resource usage, approaching thresholds
• Recovery Notifications: When issues resolve automatically
• Maintenance Notices: Planned downtime or configuration changes

Understanding Teams Message Formatting

MessageCard vs Adaptive Card Format

Server Scout utilises Adaptive Cards for Teams integration, providing richer formatting than the legacy MessageCard format. This enables:

• Colour-coded severity indicators: Red for critical, amber for warnings
• Structured data presentation: Server details, metrics, timestamps
• Action buttons: Quick links to Server Scout dashboard
• Formatted text: Bold headings, bullet points for clarity

Sample Alert Format

{
  "type": "AdaptiveCard",
  "version": "1.3",
  "body": [
    {
      "type": "TextBlock",
      "text": "Server Scout Alert",
      "weight": "Bolder",
      "size": "Medium"
    },
    {
      "type": "FactSet",
      "facts": [
        {"title": "Server", "value": "web-server-01"},
        {"title": "Alert Type", "value": "High CPU Usage"},
        {"title": "Current Value", "value": "87%"},
        {"title": "Threshold", "value": "80%"}
      ]
    }
  ]
}

Key Differences: Teams vs Slack Webhooks

Understanding these differences helps troubleshoot integration issues:

Authentication:

• Teams: Uses Office 365 connector tokens embedded in webhook URLs
• Slack: Simple webhook URLs without embedded authentication

Payload Structure:

• Teams: Requires Adaptive Card or MessageCard JSON schema
• Slack: Accepts simple JSON with text/attachment fields

URL Format:

• Teams: Contains outlook.office.com domain with connector-specific paths
• Slack: Uses hooks.slack.com domain structure

Testing Your Integration

Manual Test

1. In Server Scout, navigate to your Teams notification channel
2. Click Send Test Message
3. Verify the alert appears in your Teams channel within 30 seconds
4. Check formatting appears correctly with proper colour coding

Triggering Real Alerts

Temporarily lower a threshold (e.g., CPU warning to 1%) to generate genuine alerts, then restore normal settings once confirmed working.

Troubleshooting Common Issues

Webhook Connector Expiry

Problem: Messages stop arriving despite successful configuration. Solution: Teams connectors can expire or be removed. Recreate the webhook connector and update the URL in Server Scout.

Tenant Security Policies

Problem: "Forbidden" errors when sending messages. Solution: Contact your Office 365 administrator to verify external connector policies allow incoming webhooks for your organisation.

Invalid URL Format

Problem: "Invalid webhook URL" error during Server Scout configuration. Solution: Ensure the URL starts with https://outlook.office.com/webhook/ and contains the complete connector token. Re-copy from Teams if truncated.

Message Delivery Delays

Problem: Alerts arrive several minutes late. Solution: Check your internet connectivity and Teams service status. Server Scout sends alerts immediately, but Teams may experience processing delays during high load periods.

Best Practices

• Create separate channels for different alert severity levels
• Use descriptive webhook names to identify their purpose
• Regularly verify webhook functionality with test messages
• Document webhook URLs securely for team handovers

Your Teams integration should now deliver timely, well-formatted Server Scout alerts directly to your team's workflow.