> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/webhooks/teams-workflows.md).

# Teams(WorkFlows)

## Configure Microsoft Teams Workflows Webhook for ARM Notifications

***

## Overview

Microsoft is deprecating **Office 365 Connectors** and **Incoming Webhooks** in Microsoft Teams. To continue receiving ARM notifications in Microsoft Teams, customers must migrate to the new **Microsoft Teams Workflows** webhook integration.

This guide explains how to:

* Create a Microsoft Teams Workflow webhook
* Generate the Workflows webhook URL
* Configure the webhook in ARM
* Map notification events to Teams channels

***

## Prerequisites

Before configuring the integration, ensure the following:

* Microsoft Teams desktop or web application
* Permission to install Microsoft Teams apps (or Workflows app already installed)
* ARM Administrator access
* A Microsoft Teams Team and Channel where notifications will be posted

***

## Step 1: Install the Microsoft Teams Workflows App

1. Open **Microsoft Teams**.
2. Click **Apps** from the left navigation.
3. Search for **Workflows**.
4. Click **Install**.

> **Note:** If the Workflows app is already installed, you can skip this step.

***

## Step 2: Create or Select a Teams Channel

Create a new Team/Channel where ARM notifications should be posted.

If you already have an existing channel, you can use it directly.

***

## Step 3: Open Workflows from the Channel

1. Navigate to the required Teams channel.
2. Click the **More options (⋯)** menu.
3. Select **Workflows**.

<figure><img src="/files/axDXmhQqXRAbsE0qKURJ" alt=""><figcaption></figcaption></figure>

***

## Step 4: Create a Webhook Workflow

From the available templates:

Select:

**Send webhook alerts to a channel**

<figure><img src="/files/m6pbCFcAAWhksnwv7eeN" alt=""><figcaption></figcaption></figure>

This template creates a webhook endpoint that external applications (such as ARM) can use to send notifications.

***

## Step 5: Select Team and Channel

Choose:

* **Team**
* **Channel**

where notifications should be delivered.

Click **Save**.

<figure><img src="/files/T14JaadUCBXwr7FBiv3s" alt=""><figcaption></figcaption></figure>

***

## Step 6: Copy the Webhook URL

After saving the workflow:

1. Open the newly created workflow.
2. Click **Copy webhook link**.
3. Save the generated URL.

<figure><img src="/files/YR5IZaEOeMAel3yjXeof" alt=""><figcaption></figcaption></figure>

This URL will be required while configuring ARM.

***

## Step 7: Configure Microsoft Teams in ARM

Navigate to:

**ARM → Settings → Notifications**

Expand:

**Teams/Slack Settings**

Select the **Microsoft Teams** tab.

<figure><img src="/files/u2BfnucgHqGNuDfioOqy" alt=""><figcaption></figcaption></figure>

***

### Add Notification Channel

**Add Channel**

Provide:

| Field                   | Description                                                          |
| ----------------------- | -------------------------------------------------------------------- |
| Channel Name            | Friendly name for identification (Example: Production Notifications) |
| Webhook Integration URL | Paste the Microsoft Teams Workflows webhook URL copied earlier       |

Click **Test Connection**.

If the test succeeds, click **Save**.

***

## Step 8: Configure Notification Events

After adding the Teams channel:

Navigate to:

**Configure Notification Channels**

Choose which ARM events should send notifications to Microsoft Teams.

Examples include:

### CI Jobs

* CI Job Failed Report
* CI Job Success Report

### EZ-Commit

* Gated Check-ins
* Pre-Validation Approval
* Pre-Validation Rejection
* Mentioned Comments

### Environment

* Environment Provision

### Merge

* Merge Expiration Report

> Select the Teams channel created in the previous step for each required notification.

Click **Save**.

Sample Notifications:

<figure><img src="/files/V5EU1D9xnn4FfaaEC4vy" alt=""><figcaption></figcaption></figure>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/webhooks/teams-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.