Microsoft Teams outbound webhooks
Microsoft has retired Office 365 connectors (the Incoming Webhook connector) in Microsoft Teams:
- Since August 15, 2024, you can no longer create legacy Microsoft Teams webhooks. The test message fails.
- On April 30, 2026, Microsoft ended support for existing connectors, so legacy Microsoft Teams webhooks no longer deliver notifications. Testing one now returns
401 Unauthorized(DirectApiRequestHasMoreThanOneAuthorization).
To keep receiving alert notifications in Microsoft Teams, migrate to workflow-based Microsoft Teams outbound webhooks. See Migrate to workflow-based webhooks below.
For the recommended path, moving alerting to the Notification Center Cases model (native Teams connector, routing, and presets), see Migrate from outbound webhooks.
This page is kept for migration reference only and will be removed once all customers have moved to workflow-based webhooks.
Enhance your observability workflows by sending real-time event notifications and log data to Microsoft Teams. With this outbound webhook, you can integrate Coralogix with Microsoft Teams, automate responses to critical events, and improve your organization's incident management and alerting processes.
Native Microsoft Teams connector (private beta)
Instead of maintaining a webhook, you can connect Coralogix directly to your Microsoft Teams tenant. Case notifications and the full case lifecycle (assigned, acknowledged, resolved, closed) flow straight into your Teams channels, with threaded or new-message delivery and self-serve setup, with no webhook to manage. Each notification links to the case in Coralogix, where you can review it and update its state.
The connector is currently in private beta. To request access and the app package, contact your TAM or Coralogix Support.
To install the app, connect your tenant, and create a connector, follow Install and set up Microsoft Teams. For an overview, see the Microsoft Teams destination. To move existing alerting from webhooks to the Cases model, see Migrate from outbound webhooks.
Migrate to workflow-based webhooks
If you do not use Cases, or you want a like-for-like replacement for the retired webhook, migrate to workflow-based webhooks instead.
Because Microsoft retired Office 365 connectors, legacy Microsoft Teams webhooks can no longer be created and no longer deliver notifications. There is no automatic migration, because moving to the supported method requires creating a new webhook in your Microsoft Teams account. Migrate each legacy webhook as follows:
In Microsoft Teams, create a Workflows webhook and copy its URL. See the prerequisites for the workflow-based webhook.
In Coralogix, add a new workflow-based Microsoft Teams outbound webhook with that URL, then select Test Config to confirm the test message arrives.
Update every alert and notification that used the legacy webhook to use the new workflow-based webhook.
Confirm that notifications arrive in Microsoft Teams, then delete the legacy webhook.
Prerequisites
The steps in this section and the next describe the retired connector method. They are kept for reference only and no longer work. To set up a working webhook, follow Migrate to workflow-based webhooks above.
Configure Your Microsoft Teams endpoint URL if you have not already done so.
Navigate to Apps (in the left sidebar) in Microsoft Teams.
Search the apps for Incoming Webhook. Select Incoming Webhook.
Click Add to a team.
Select a channel to use for the webhook. Click Set up a connector.
Provide a name for the webhook. Click Create.
Once you create the webhook, copy the endpoint URL at the bottom of the dialog box.
Create a Microsoft Teams webhook
Access Integrations, then Integrations. Select Outbound Webhooks under Sections.
In the Outbound Webhooks section, select Microsoft Teams via Workflow.
Click Add New.
Enter the following details for your webhook:
- Webhook Name. Input a name for your webhook that will enable you to quickly identify this webhook later when attaching it to one of your alerts.
- URL. Paste the Microsoft Teams webhook URL previously copied in [Prerequisities].
Click Test Config.
The system will send a test message to the channel you specified in the Microsoft Teams webhook URL to check that your configuration is valid. If the test message is received successfully, a confirmation message is displayed.
Once the configuration is confirmed, configure your alert notifications.
Additional resources
| Documentation | Configure Alert Notifications for Outbound Webhooks |
Next steps
Route alert notifications to PagerDuty for incident management with PagerDuty outbound webhooks.