Microsoft Teams
Microsoft Teams can be used as a notification destination in Causely.
How you configure Microsoft Teams depends on how notifications are managed in your environment.
Causely supports two configuration paths:
-
Managed Notifications (recommended)
Routing rules are configured in the Causely UI based on impact, severity, and context.
Microsoft Teams delivery requires a one-time Teams Workflow setup, described below. -
Mediator-based Notifications (advanced)
Notifications are configured programmatically using the Causely Mediator and Causelybot.
Routing and notification rules for Managed Notifications are configured in the Causely UI: Set up notification routing in the UI
Managed Notifications (Recommended)
Most teams use Managed Notifications to route Causely insights to Microsoft Teams.
In this model:
- Notification routing and logic are defined in the Causely UI
- Microsoft Teams is used purely as a delivery destination
- Alerts are delivered as Adaptive Cards
To receive notifications in Microsoft Teams, you must configure a Teams Workflow to accept webhook requests and post Adaptive Cards to a channel.
Microsoft Teams Workflow Setup
Microsoft Teams requires a Teams Workflow to receive webhook requests from Causely and render notifications as Adaptive Cards. This workflow is configured once per Team or Channel.
Step 1: Create a New Workflow
- In Microsoft Teams, navigate to Workflows
- Select Create
- Choose Create from blank
Step 2: Add the Webhook Trigger
- Select the trigger When a Teams webhook request is received
- For Who can trigger the flow, select Anyone
This allows Causely to invoke the workflow using the generated webhook URL.
Step 3: Process Adaptive Card Attachments
Causely sends Microsoft Teams notifications as Adaptive Card attachments.
- Add a new step and select Apply to each
- For the input, select attachments from the webhook trigger output
This ensures each Adaptive Card attachment is handled correctly by the workflow.
Step 4: Post the Card to a Channel
Inside the Apply to each block:
- Add the action Post card in a chat or channel
- Configure the required fields:
- Post as: Flow bot
- Post in: Channel
- Team: Select your team
- Channel: Select the destination channel
- Adaptive Card: Select content from the attachments output
Example Workflow Configuration
The example below shows a completed Microsoft Teams Workflow with the webhook trigger, attachment handling, and channel post configured correctly.
Result
Once configured, each Causely notification triggers the Teams Workflow and posts a structured Adaptive Card into the selected channel, providing immediate, actionable context without alert noise.
Mediator-based Configuration (advanced)
To integrateMicrosoft Teams with Causely, you must install the Causelybot and configure it as your Microsoft Teams webhook endpoint. The bot listens for alerts from the Causely platform and posts them to your desired Microsoft Teams channels.
-
Follow the installation instructions for the Causelybot in the official GitHub repository: Causelybot
-
Once deployed, update your
causely-values.yamlfile to include the executor and the bot's URL endpoint.
For example, if you deploy the Causelybot in the foo namespace of your cluster, you can configure the webhook endpoint in your causely-values.yaml file like this:
executor:
enabled: true
notifications:
webhook:
url: 'http://<CAUSELYBOT_FQDN/IP>:5000/webhook'
token: '<YOUR_CAUSELYBOT_TOKEN>'
enabled: true
Make sure the Causelybot is accessible from your Causely deployment and properly configured to post to your Microsoft Teams workspace and channel. Ensure the Microsoft Teams channel webhook is set up to accept incoming messages and that the Causelybot has access permissions.
To install the Causely agent with the Microsoft Teams integration enabled, run:
causely agent install --cluster-name <cluster-name> --values ./causely-values.yaml
Notification Payload Format
Causely sends structured alert payloads to Microsoft Teams, including summaries of causal insights and service impact context.
For an example payload and explanation of each field, refer to the Notification Payload Format page.