integrations
Updated January 13, 2025
Microsoft Teams Integration
Send incident alerts to Microsoft Teams channels for enterprise team coordination
Microsoft Teams Integration
Connect StatusPageOne with Microsoft Teams to receive incident alerts in your team channels. Perfect for enterprise environments and organizations using Microsoft 365 for team collaboration.
Why Microsoft Teams Integration?
✅ Benefits
- •Enterprise integration with Microsoft 365 ecosystem
- •Rich card formatting with adaptive cards and actionable content
- •Native notifications through Teams desktop and mobile apps
- •Thread-based discussions for incident coordination
- •Unlimited notifications across all plan tiers
🎯 Perfect For
- •Enterprise organizations using Microsoft 365 suite
- •IT operations teams requiring formal incident management
- •Compliance environments with strict communication policies
- •Corporate teams standardized on Microsoft tools
- •Global enterprises with centralized communication policies
Teams Message Format
StatusPageOne sends rich adaptive cards to Teams channels with professional formatting:
Incident Alert Example
👥 Teams Incident Alert
🚨Monitor Alert: API Server
Status: DOWN
Region: us-east-1
Response Time: 30000ms
Status Code: N/A
Error: Connection timeout after 30 seconds
Previous Status: UP
Consecutive Failures: 3
Time: 2024-01-15 15:30:15 UTC
StatusPage One Monitoring
Recovery Alert Example
👥 Teams Recovery Alert
✅Monitor Recovered: API Server
Status: UP
Region: us-east-1
Response Time: 245ms
Status Code: 200
Service Restored: All systems operational
Previous Status: DOWN
Total Downtime: 12 minutes 15 seconds
Recovery Time: 2024-01-15 15:42:30 UTC
StatusPage One Monitoring
Setup Guide
Step 1: Create an Incoming Webhook in Teams
-
Open Microsoft Teams
- Navigate to the channel where you want alerts
- Click the "..." menu next to the channel name
- Select Connectors
-
Add Incoming Webhook Connector
- Search for "Incoming Webhook"
- Click Configure next to Incoming Webhook
- Give your webhook a name (e.g., "StatusPage Alerts")
- Optionally upload a custom image/icon
-
Copy the Webhook URL
- Teams will generate a webhook URL
- Copy the complete URL (starts with
https://outlook.office.com/webhook/) - Save this URL for StatusPageOne configuration
🔗
Teams Webhook URL Format
Teams webhook URLs are long and include unique identifiers:
https://outlook.office.com/webhook/[tenant-id]/IncomingWebhook/[channel-id]/[webhook-id]
Step 2: Configure in StatusPageOne
-
Access Integration Settings
- Navigate to your monitor in the console
- Click the Integrations tab
- Select Add Integration
- Choose Teams from the integration types
-
Enter Webhook Configuration
Webhook URL * [Configuration field]
The incoming webhook URL from your Teams channel
Integration Name [Configuration field]
Descriptive name to identify this integration
[Toggle to enable] Enable notifications
Step 3: Test the Integration
- Click Test Integration to send a sample alert to your Teams channel
- Check your Teams channel for the test message
- Verify the card formatting and information display correctly
Step 4: Save and Activate
- Click Save Integration
- Confirm the integration shows as Active
- Your Teams channel will now receive incident notifications
Advanced Configuration
Multiple Teams Channels
Set up different Teams integrations for various purposes:
Critical Operations
Channel: IT Operations - Critical
Audience: On-call engineers, management
Services: Production APIs, databases
High-priority incidents requiring immediate escalation
Development Team
Channel: Development - Alerts
Audience: Development team members
Services: Staging, development environments
Non-production alerts for development coordination
Executive Dashboard
Channel: Executive - System Status
Audience: Leadership team, C-level
Services: Customer-facing systems
High-level status updates for business continuity
Regional Teams
Channel: EMEA Operations
Audience: European team members
Services: Regional infrastructure
Timezone-specific alerts for distributed teams
Enterprise Integration Features
Teams Advanced Features
Adaptive Cards:
- • Rich visual formatting
- • Structured data presentation
- • Mobile-optimized display
- • Consistent enterprise branding
Enterprise Features:
- • Thread-based incident discussion
- • Integration with Office 365
- • Compliance and audit logs
- • SSO and security policies
Teams Workflow Integration
Power Automate Integration
Connect Teams alerts with Microsoft Power Automate for advanced workflows:
Automated Workflows
- • Incident Tickets: Automatically create incidents in ServiceNow or Azure DevOps
- • Email Escalation: Send escalation emails to management after delays
- • Calendar Updates: Block calendars during critical incidents
- • Document Creation: Generate incident reports in SharePoint
- • Team Notifications: Notify specific team members based on alert type
Teams Bot Enhancement
Custom Teams Bot Features
For advanced setups, consider building a custom Teams bot that can:
- • Acknowledge incidents directly from Teams
- • Query current system status via chat commands
- • Create incident war rooms automatically
- • Provide real-time status updates
Enterprise Compliance
Security and Compliance Features
🔒 Enterprise Security
Data Protection:
- • Messages encrypted in transit
- • Microsoft 365 compliance policies
- • Data residency compliance
- • GDPR and SOC 2 alignment
Access Control:
- • Teams channel permissions
- • Azure AD integration
- • Conditional access policies
- • Multi-factor authentication
Audit and Logging
- • Message Retention: Teams messages retained per organizational policies
- • Audit Logs: Integration activity logged in Microsoft 365 audit center
- • eDiscovery: Incident communications discoverable through Microsoft tools
- • Compliance Reports: Integration usage tracked in compliance dashboards
Message Customization
Adaptive Card Structure
Teams messages use Microsoft's Adaptive Cards for rich formatting:
Card Components
Header Section: Alert type with status-color theming
Fact Set: Key-value pairs for incident details
Text Blocks: URLs, error messages, and descriptions
Container: Organized sections with visual separation
Footer: Attribution and timestamp information
Visual Design
Color Coding: Red accent for incidents, green for recovery
Typography: Microsoft's Segoe UI font family
Spacing: Consistent padding and margins
Icons: Emoji status indicators for quick scanning
Integration Management
Teams Integration Health
Monitor your Teams integration status:
Health Metrics:
- • Delivery Status: Success/failure rates of recent notifications
- • Response Times: Teams API response performance
- • Webhook Validity: Active webhook URL verification
- • Last Activity: Timestamp of last successful message
- • Error Tracking: Detailed error logs with Microsoft error codes
Webhook Management
⚠️
Webhook Lifecycle Management
- • Teams webhooks can be disabled by channel administrators
- • Webhook URLs change if the connector is reconfigured
- • Deleted channels automatically invalidate webhooks
- • Organization policies may restrict webhook usage
- • Regular testing recommended to ensure continued functionality
Troubleshooting
Common Issues
❌ Messages Not Appearing
Webhook Issues:
- • Verify webhook URL is complete and unmodified
- • Check that incoming webhook connector is still configured
- • Ensure Teams channel wasn't deleted or archived
- • Confirm webhook wasn't disabled by channel admin
Permissions:
- • Verify you have permission to add connectors to channel
- • Check if organization policies restrict webhooks
- • Ensure Teams license includes webhook functionality
⚠️ Formatting Problems
Adaptive Cards:
- • Cards may render differently on mobile vs. desktop
- • Some older Teams clients may not support all features
- • Corporate themes may affect card appearance
- • Long messages may be truncated in notifications
🔧 API Errors
Microsoft Teams API Responses:
- • 404: Webhook not found (deleted or disabled)
- • 400: Invalid message format or size
- • 429: Rate limited by Teams API
- • 500: Microsoft Teams service issues
Testing and Validation
🧪 Teams Integration Testing
1Set up incoming webhook connector in Teams channel
2Copy webhook URL and configure in StatusPageOne
3Use Test Integration to send sample adaptive card
4Verify card appears correctly in Teams channel
5Test on both desktop and mobile Teams clients
Best Practices
👥 Teams Integration Best Practices
Channel Organization
- • Create dedicated channels for different alert types
- • Use clear naming conventions: "IT-Alerts-Critical"
- • Set up private channels for sensitive monitoring data
- • Configure channel notifications appropriately
Enterprise Coordination
- • Use threads for incident discussion and updates
- • Set up escalation workflows with Power Automate
- • Document incident response procedures in channel tabs
- • Integrate with other Microsoft 365 tools
Compliance and Governance
- • Follow organizational policies for webhook usage
- • Ensure proper data classification for alerts
- • Set up appropriate retention policies
- • Monitor webhook usage through audit logs
Technical Management
- • Test integrations after Teams updates
- • Monitor webhook health in StatusPageOne console
- • Set up backup notification methods
- • Document webhook configurations for team reference
Teams vs. Other Platforms
When to Choose Microsoft Teams
Teams is Best For:
Enterprise Environments:
- • Microsoft 365 organizations
- • Compliance-regulated industries
- • Large corporate environments
- • Centralized IT management
Integration Requirements:
- • Office 365 ecosystem integration
- • Azure AD authentication
- • Power Platform workflows
- • Enterprise security requirements
Usage and Limits
Plan Limits
| Plan | Teams Notifications | Features |
|---|---|---|
| Free | Unlimited | Basic adaptive cards |
| Pro | Unlimited | Rich cards + channel customization |
| Business | Unlimited | Priority delivery + enterprise features |
Technical Specifications
Teams Integration Specifications:
- • Message Format: Adaptive Card v1.4 specification
- • Rate Limits: 4 requests per second per webhook
- • Message Size: 28KB maximum payload
- • Timeout: 30 seconds maximum response time
- • Retry Logic: 3 attempts for temporary failures
Enterprise Use Cases
Fortune 500 Deployment Examples
Global Financial Services
Multi-region incident coordination with compliance requirements
• Regional operations channels
• Executive escalation workflows
• Audit-compliant incident documentation
Healthcare Organization
HIPAA-compliant monitoring with strict security requirements
• Private channels for sensitive systems
• Integration with Azure AD
• Conditional access policies
Manufacturing Enterprise
Operations-focused incident management across facilities
• Site-specific operations teams
• Equipment monitoring integration
• Shift-based escalation workflows
Government Agency
High-security incident response with government compliance
• GCC High Teams environment
• FedRAMP compliance alignment
• Classified data handling procedures
Microsoft 365 Integration
Power Platform Workflows
Advanced Automation
- • Power Automate: Trigger complex workflows from Teams messages
- • Logic Apps: Enterprise-grade integration with Azure services
- • SharePoint: Auto-generate incident documentation
- • Outlook: Send escalation emails to management
- • Planner: Create incident response task boards
Next Steps
After setting up Microsoft Teams integration:
- Configure Email Alerts - Add comprehensive incident documentation
- Set Up SMS Notifications - Ensure critical alerts reach everyone
- Implement Webhooks - Enable automated incident response
- Explore Power Automate - Build advanced enterprise workflows
Teams integration provides excellent enterprise-grade incident coordination. Combine with other channels and Microsoft 365 services for comprehensive enterprise incident management.
Support
Need help with Microsoft Teams integration?
- Verify webhook URL from Teams connector configuration
- Check organizational policies for webhook restrictions
- Test webhook functionality with Microsoft's webhook tester
- Contact support for enterprise deployment assistance
Improve this page
Found an error or want to contribute? Edit this page on GitHub.