---
title: "Configuring Microsoft Teams App"
slug: "configuring-microsoft-teams-app"
updated: 2025-09-12T16:23:50Z
published: 2025-09-12T16:23:50Z
canonical: "documentation.encodify.com/configuring-microsoft-teams-app"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.encodify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Microsoft Teams App

## Overview

---

> [!WARNING]
> **Important:** Before enabling Microsoft Teams, an Encodify administrator must first ensure that it’s enabled within your infrastructure.

To configure a Notification Rule using the Microsoft Teams channel, three key steps must be completed:

1. **Microsoft Teams App in Microsoft Developer Portal** – Create and configure the app, which acts as the bridge between your system and Microsoft Teams. This step is covered in detail in this article.
2. [**Microsoft Teams Connected Service**](/v1/docs/ms-teams-connected-service) – Set up the connected service to allow secure communication between your system and the Teams app.
3. [**Notification Rule Configuration**](/v1/docs/configuring-a-notification-rule) – Configure the rule for the relevant trigger, specifying recipients, channels, and message content so notifications are sent automatically when the event occurs.

## Microsoft Teams App Configuration in Microsoft Developer Portal

---

### **Step 1: Create a new app**

1. Go to [Microsoft Teams Developer Portal](https://dev.teams.microsoft.com/apps).
2. Click **+ New App** (or import an existing one).
3. Enter the **App Name** and click **Add**
4. Complete all required fields on the **Basic Information** tab.

![Screenshot 2023-10-26 115434.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14410414755357.png)

### Step 2: Configure Bot

1. Navigate to **Tools → Bot Management**.

**![Screenshot 2023-10-26 114855.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14410414760221.png)**

1. Click **+ New Bot**, enter a **Bot Name**, and click **Add**.
2. Click **Client secret → Add a client secret for your bot**.

![Screenshot 2023-10-26 120130.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14410647561501.png)

1. Store the generated **Client Secret** securely for later use.

**![Screenshot 2023-10-26 120145.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14410630856605.png)**

### Step 3: Assign Bot to App

1. Navigate to **Apps → {App Name} → Configure → App Features → Bot**.

![Screenshot 2023-10-26 120941.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14410891399069.png)

1. Ensure your bot is selected under **Select Existing Bot**.

![Screenshot 2023-10-26 121010.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14411585975325.png)

### Step 4: Retrieve Manifest ID and Client ID

1. Navigate to **App → App Package Editor → Manifest**.

**![Screenshot 2023-10-26 121852.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14411585982109.png)**

1. Note the **Manifest ID** and **Client ID (Bot ID)**; these are required for the Microsoft Teams connected service.

![Screenshot 2023-10-26 123610.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/14411585983517.png)

1. Publish the application by clicking **Publish → Publish to your org**.
  1. The publishing request must be approved by an admin via the [Teams Admin Portal](https://admin.teams.microsoft.com/policies/manage-apps).

## Microsoft Teams Bot Configuration in Microsoft Azure

---

### Step 1: Locate the Bot Application

1. Go to **Microsoft Azure → Enterprise Applications → All Applications**.
2. Use the global search to find your **Microsoft Teams Bot** created in the Developer Portal.

![Azure bot.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/22002736956061.png)

### Step 2: Copy Directory (Tenant) ID

1. Select **Overview** under the **Manage** section.
2. Copy the **Directory (Tenant) ID**; it is required for the connected service configuration.

![Overview Tenant ID.png](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/22002785435933.png)

### Step 3: Configure API Permissions

1. Switch to the **API Permissions** tab.
2. Add **Microsoft Graph** permissions with **Application** type and grant **Admin Consent**:
  - `AppCatalog.ReadWrite.All`
  - `TeamsActivity.Send`
  - `User.Read.All`
  - `TeamsAppInstallation.ReadWriteForUser.All`

![](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/Screenshot 2025-07-18 at 13.53.11.png)

> [!WARNING]
> **Note:** `AppCatalog.ReadWrite.All` is required to install the app for a user for the first time. This can also be performed manually or by an administrator.

Take careful note of the **Client ID**, **Client Secret, Manifest ID,** and **Tenant ID** during the app setup, as they are required to complete the [Microsoft Teams Connected Service](/v1/docs/ms-teams-connected-service).