--- title: "Microsoft Teams" slug: "microsoft-teams" updated: 2026-09-18T12:24:44Z published: 2026-09-18T12:24:44Z canonical: "docs.turbo360.com/microsoft-teams" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Teams ## Overview Microsoft Teams can be configured as a notification channel in Turbo360 to receive alert and monitoring notifications. Turbo360 sends notifications to a Teams channel using an incoming webhook URL, automatically posting alert incidents so your team can stay informed and respond quickly. ### Business value Routing Turbo360 alerts into Microsoft Teams keeps incident visibility within your team's existing collaboration workspace. Teams can triage and respond to issues without switching between tools. ## Prerequisites - An active Microsoft Teams workspace with a channel designated for receiving Turbo360 alerts. - Permissions to add apps and create workflows in the target Teams channel. - An incoming webhook URL generated from a Power Automate workflow in Teams. See [Create incoming webhooks with Workflows for Microsoft Teams](https://support.microsoft.com/en-us/office/create-incoming-webhooks-with-workflows-for-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498) for instructions. ### Required permissions You must have permission to add apps and create cloud flows in Microsoft Teams to generate the incoming webhook URL. ### Dependencies - A Power Automate (Workflows) flow must be configured in the target Teams channel before you can generate the webhook URL. - Turbo360 must have outbound connectivity to the webhook endpoint. ## How it works Turbo360 connects to Microsoft Teams using an incoming webhook URL. When an alert condition is met, Turbo360 sends a notification payload to the webhook, which triggers a Power Automate flow that posts an adaptive card to the configured Teams channel. You validate the connection during setup by sending a test notification before saving. ## Steps ### Create an incoming webhook URL in Microsoft Teams Use the following steps to create the Power Automate workflow and generate an incoming webhook URL. Open Microsoft Teams to get started. 1. Create a channel in Microsoft Teams to capture alert incidents from Turbo360. 2. In the channel, click the **+ (Add a tab) icon** → select **Apps** → choose **Workflows** → click **Save** to create a workflow. 3. Click **New flow** → select **Instant cloud flow** → choose **When a Teams webhook request is received** → click **Create**. 4. Configure the workflow with the following four actions: **a. Initialize variable** - Provide a variable name. - Set **Type** to **Object**. **b. Post card in a chat or channel** - Select the required Team and Channel. - Set **Post as** to **Flow bot**. - Set **Post in** to **Channel**. - Set **Adaptive card** to **Adaptive card**. **c. Set variable** - Enter the name of the initialized variable. - Set **Value** to **Body** from the **Post card in a chat or channel** action. In the **Set variable** action settings, enable: **Has timed out**, **Is skipped**, and **Has failed**. **d. Response** - Set **Status Code** to **200**. - Set **Body** to **variable**. In the **Response** action settings, enable: **Is successful**, **Has timed out**, **Is skipped**, and **Has failed**. Note: Actions **4.b** and **4.c** must be placed inside a **For each** loop. 1. Save the workflow. 2. Copy the webhook URL generated in the first action of the workflow. ### Configure the Microsoft Teams channel in Turbo360 1. In Turbo360, navigate to the notification channel configuration and select **Microsoft Teams**. 2. Enter a **Friendly name** to identify this channel in the Turbo360 application. 3. Paste the **Incoming webhook URL** generated from your Teams workflow. 4. Click **Validate**. Turbo360 sends a test notification to the webhook URL to verify the configuration. 5. After successful validation, click **Save** to complete the setup. ## Configuration | Field | Required | Description | | --- | --- | --- | | Friendly name | Yes | Display name for this channel in Turbo360 | | Incoming webhook URL | Yes | The webhook URL generated from the Power Automate flow in your Teams channel | ## Permission behavior **With access:** Turbo360 can post notifications to the configured Teams channel via the webhook URL and send test notifications using the **Validate** action. **Without access:** If the webhook URL is invalid or the Power Automate flow is disabled, the validation will fail and notifications will not be delivered. Ensure the flow is active and the URL has not expired. ## Example scenario Your operations team monitors Azure services using Turbo360. You configure a Microsoft Teams notification channel and link it to your `#ops-alerts` channel. When a monitoring rule triggers, Turbo360 posts an adaptive card to the channel, giving the on-call engineer immediate visibility of the incident without leaving Teams. ## Limitations - Microsoft Teams no longer supports the legacy Incoming Webhook connector. Use the Power Automate (Workflows) approach described in this article. - The webhook URL is tied to the Power Automate flow; if the flow is deleted or disabled, the channel stops receiving notifications. - Only one Teams channel can be configured per notification channel entry. Create separate channels in Turbo360 for different Teams channels. ## Troubleshooting 1. **Validation fails after entering the webhook URL** Cause: The webhook URL is incorrect, expired, or the associated Power Automate flow is disabled. Fix: Verify the URL was copied from the first action of the correct workflow. Check that the flow is active in Power Automate. Regenerate the webhook URL if needed. 2. **Notifications are not appearing in the Teams channel after validation succeeds** Cause: Actions 4.b and 4.c are not inside a **For each** loop, or the action settings (timed out, skipped, failed) are not configured correctly. Fix: Review the Power Automate flow structure and confirm the loop and action settings match the steps in this article. 3. **Adaptive card posts but content is missing or malformed** Cause: The **Set variable** or **Response** action is misconfigured. Fix: Confirm that **Value** in the **Set variable** action is set to **Body** from the **Post card** action, and that the **Response Body** is set to the initialized variable. 4. **Alert fires in Turbo360 but no notification appears in Teams** Cause: The notification channel is not linked to the alert or escalation policy. Fix: Verify the alert rule or escalation policy references this Teams channel. 5. **Webhook URL stopped working after working previously** Cause: The Power Automate flow was modified, disabled, or the webhook trigger was regenerated. Fix: Return to Power Automate, confirm the flow is enabled, and copy the updated webhook URL from the trigger action. Update the channel configuration in Turbo360. ## FAQs 1. **Can I use a legacy Teams Incoming Webhook connector instead of Power Automate?** Microsoft has retired the legacy Incoming Webhook connector for Teams. You must use the Power Automate (Workflows) approach to generate a webhook URL. 2. **Can I configure multiple Teams channels in Turbo360?** Yes. You can create multiple Microsoft Teams notification channels, each with a different webhook URL pointing to a different Teams channel. 3. **Do I need to recreate the Power Automate flow if the webhook URL expires?** No. You can regenerate the webhook URL from within the existing flow by opening the trigger action in Power Automate. Once you have the new URL, update the Incoming webhook URL field in the Turbo360 channel configuration and re-validate. ## Related articles - [Create incoming webhooks with Workflows for Microsoft Teams](https://support.microsoft.com/en-us/office/create-incoming-webhooks-with-workflows-for-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498)