Using Webhooks to Integrate Confluent Cloud and Microsoft Teams

Data streaming equips modern organizations to rapidly ingest and understand new information and use it to solve real-world problems at scale. For some of these real-time insights—critical operational cues that demand a timely response—delivering that information directly to your team’s inbox is the best way to act on it. That’s why many of our customers not only take advantage of service event notifications directly in their Confluent Cloud accounts but also integrate them with their Microsoft Teams tenants.

Integrating alerts for Apache Kafka® metrics with an enterprise collaboration platform like Teams allows you to be immediately aware of and responsive to:

• Critical incidents: Kafka cluster expansion failure, Apache Flink® statement failure, connector in FAILED state

• Important warnings: Kafka cluster shrink failure, Flink statement degraded, Flink statement auto-stopped

• Useful information: Kafka cluster expansion completed, Kafka cluster shrink completed, connector state transition from PROVISIONING to RUNNING

Historically, you may have received these notifications in Teams by generating and using incoming webhooks, which provide a unique URL where external applications could send a JSON payload with a message to Microsoft Teams channels in a Message Card format.

Recently, Microsoft announced the deprecation of Microsoft 365 connectors, which means the old method no longer works. Fortunately, you can use Power Automate to get the same result with Microsoft’s new webhook implementation and the Adaptive Card format. In this guide, we’ll show you how. Let’s get started.

Not yet on Confluent Cloud? Try it for free or explore our product demos.

5 Steps for Real-Time Teams Workflows Using Power Automate

Here’s how to create a new workflow between Confluent Cloud and Microsoft Teams using Power Automate, a solution for automating enterprise workflows and optimizing business processes. This approach is based on the assumption that you already have the Cloud notifications you want in Teams set up in your Confluent account.

Note: This method only works with the Adaptive Card format. The Message Card format will reportedly be supported by mid-October 2025.

1. Build an automated cloud flow in Power Automate.

To create a flow, first go to Power Automate in your web browser. Click the “New flow” button and then select “Automated cloud flow” from the drop-down menu.

This will take you to setting up and naming your automated cloud flow, which you can change or update later. You’ll also be asked to choose your flow’s trigger, but skip this step for now.

The trigger you need (“When a Teams webhook is received”) is not available via search here but will be in the next step.

2. Add “webhook received” as your workflow trigger.

In the next screen, you’ll see that you have this option in the middle of the screen: “Add a trigger.” Click to add a trigger, type “teams” in the search bar, and then select “When a Teams webhook request is received” as the trigger.

Then set up the parameters so that “Anyone” can trigger the flow. This will ensure that you continue to receive notifications from Confluent.

3. Allow the workflow to post cards in Teams chat or channels.

Now click the +  button below the trigger card labeled “When a Teams webhook request is received” to add the action that will be performed in response. Then search “post card” and select “Post card in a chat or channel” as the action.

Then, for the “Post in” parameter, select the “Channel” option from the drop-down list.

4. Configure the workflow action and add Team and Channel IDs.

After selecting the “Channel” option, you’ll have the option to add Team ID, Channel ID, or Adaptive Card JSON. Note that it may take a minute or two for these fields to load.

Hover over the Adaptive Card field and click on the blue “fx” button that appears (shown in the next screen capture), which will open a dialog box. Click the “Dynamic Content” tab, select “Body” from the list of options, and then click “Add.”

Once you’ve set the Adaptive Card parameter, click “Save” in the top right corner to generate a Microsoft Teams webhook URL.

In your Power Automate flow, click on the card labeled “When a Teams webhook request is received” and copy the HTTP URL. Now you’re ready to configure your webhooks in Confluent Cloud and verify that everything works as expected.

5. Add Teams webhooks in Confluent Cloud and validate your integration.

There are two parts to adding a new Microsoft Teams integration to your Confluent Cloud deployment and specific notifications.

Part 1: Add a new global integration to make your Microsoft Teams webhook URL accessible to all Confluent Cloud notifications.

First, click on the bell icon in the top right of the Cloud Console toolbar.

This will open the “Manage Notifications” settings. Click on the pencil icon next to Microsoft Teams to add a new integration to one of your notifications so you can verify the endpoint.

Next, you’ll see the following screen pop up. Click on the button that says, “Add Microsoft teams url.”

Next, you’ll name the integration and add the webhook URL that you copied or saved in Step 4. In the screenshot below, you’ll see the name “my msteams integration.”

Click on “Verify” and then “Save.” Now you have the Microsoft Teams integration ready to add to and test with an individual notification.

Part 2: Add the new Microsoft Teams integration to a specific Confluent Cloud notification in order to verify the endpoint.

Once again, click the bell icon in the Cloud Console toolbar to add the new Microsoft Teams integration to a specific notification.

Choose a specific notification to add the integration to, hover over it, and then click on the pencil icon that appears next to it to edit the notification settings.

This will open the settings of the specific notification you chose. Within the notification settings, select the Microsoft Teams checkbox and the named integration that you set up in Part 1 of this step. 

Then click on “Verify Microsoft Teams Integration.” At this point, your designated Microsoft Teams channel should receive a test message, confirming that the integration works.

Once that happens, click “update” in the notification settings to save these changes and to receive that type of notification in your chosen Microsoft Teams channel going forward.

You can also click on “Add another Microsoft Teams URL” to add other integrations (set up using Steps 1–4) directly to a specific notification.

Then the same fields for a new Microsoft Teams integration that you set up in Part 1 of this step—Name and Microsoft Teams URL—will appear.

Complete these fields the same way that you did when adding a new global integration, then click “Verify integration” and “Save” to add it to the specific notification you’re updating.

Now you can follow the same steps to add this integration to other notifications in Confluent Cloud or build automated flows for other Teams channels.

Learn More About Using Confluent Cloud

Now that you know how to integrate Microsoft Teams and Confluent Cloud, you can stream operational metrics and alerts directly into relevant Teams channels and accelerate troubleshooting, incident response, and productivity for your Kafka and Flink use cases. Plus, delivering in a user-friendly format within Teams makes real-time insights more accessible to collaborators that aren’t direct users.

Still getting up to speed with Confluent Cloud? Attend Fundamentals or Advanced onboarding sessions to get a full, guided introduction.

Apache®, Apache Kafka®, Kafka®, Apache Flink®, and Flink® are registered trademarks of the Apache Software Foundation. No endorsement by the Apache S oftware Foundation is implied by the use of these marks.