Overview 💥
Liongard integrates with Microsoft Teams to deliver Actionable Alerts directly into Teams channels, helping teams stay informed and respond quickly to important events.
Microsoft is actively modernizing Teams integrations and deprecating legacy webhook mechanisms. As a result, existing Teams integrations must be reviewed and, where necessary, migrated to prevent alert delivery failures.
⚠️ Important – Microsoft Deprecation Timeline
Microsoft is retiring legacy Office 365 Connector–based Incoming Webhooks and migrating Teams integrations to the Workflows (Power Automate) model. All Teams webhook integrations should be reviewed and updated before December 2025.
This article explains:
How Liongard’s Microsoft Teams integration works
Supported, deprecated, and unsupported webhook types
How to identify your current webhook configuration
Recommended setup steps using Teams Workflows
Common issues, troubleshooting steps, and best practices
Why Are These Changes Happening? 🤔
Microsoft is standardizing how applications post messages into Teams to improve:
Security and governance.
API consistency and reliability.
Tenant-level auditing and control.
As part of this initiative:
The Office 365 Connector app is deprecated and blocked for new webhook creation.
Teams now uses the Workflows (Power Automate) app for webhook creation.
Existing Power Automate HTTP trigger URLs are being migrated to newer endpoint formats.
If a webhook is not updated before Microsoft’s deadlines, Liongard alerts may stop appearing in Teams.
Supported Microsoft Teams Integration Methods ✅
Integration Method | Status | Notes / Recommended Action |
Incoming Webhook (via Teams Workflows – Recommended) | ✅ Supported | Created using the Teams Workflows app. Simplest and most reliable option. |
Power Automate / Workflows HTTP Trigger | ⚠️ Supported (Migration Required) | Existing URLs must be updated before Nov 30, 2025 due to Microsoft endpoint changes. |
Office 365 Connector App (Legacy) | ❌ Deprecated | Blocked for new creation since Aug 2024. Fully retiring Dec 2025. |
Portal / Designer URLs | ❌ Not Supported | Management URLs cannot receive webhook payloads. |
Correct and Incorrect Webhook URL Formats 🔗
✅ Supported Webhook URL Formats
URL Example | Valid? | Description |
| ✅ Yes | Power Automate / Workflows HTTP trigger webhook |
| ✅ Yes | Newer Power Automate / Workflows HTTP trigger |
| ✅ Yes (Legacy) | Classic Teams Incoming Webhook (retiring Dec 2025) |
❌ Unsupported URL Format
URL Example | Valid? | Reason |
| ❌ No | Portal/management link, not a webhook endpoint |
ℹ️ Liongard UI Warning
Liongard displays warnings when deprecated or soon-to-expire webhook URLs are detected.
How to Identify Your Webhook Type 🧭
Navigate to Liongard → Admin → Integrations → Microsoft Teams.
Review the configured webhook URL.
Compare it against the supported formats above.
If your webhook uses a legacy or migrating format, update it as soon as possible to avoid alert disruption.
How to Integrate Liongard with Microsoft Teams 🛠️
✅ Step 1 — Create a Webhook Using Teams Workflows.
✅ Step 2 — Add the Webhook to Liongard.
A successful test posts a message immediately into the Teams channel.
Using Liongard
Use Send Test to Teams from the integration page
Optional Manual Test
curl -H "Content-Type: application/json" \
-d '{"text":"Test from Liongard"}' \
"<YourWebhookURL>"
Common Issues and Resolutions 🚑
Issue | Likely Cause | Resolution |
Webhook rejected | Invalid or portal URL | Recreate webhook using Teams Workflows |
Alerts stopped after migration | Legacy URL expired | Update to new webhook endpoint |
No alerts delivered | Webhook deleted or rotated | Generate new webhook and update Liongard |
Duplicate alerts | Multiple templates applied | Review Actionable Alert templates |
Best Practices ⭐
Use Teams Workflows Incoming Webhooks for all new integrations
Review and migrate integrations before November 2025
Treat webhook URLs as secrets
Test integrations regularly
Use separate Teams channels for test and production alerts
Use service accounts for workflow ownership
When to Contact Support 🫡
Contact Liongard Support if:
You are unsure which webhook type is configured
Alerts stopped after Microsoft migration deadlines
You see deprecation warnings and need guidance
Tests succeed but alerts fail intermittently
When contacting support, include the webhook URL format and any error details.
Quick Reference 🤓
Liongard Docs
Microsoft Docs
External Resource Disclaimer ‼️
This article references external Microsoft resources. Liongard does not control availability, functionality, or accuracy of third-party sites. Use them as optional reference resources.
