Skip to main content

​
Introduction

The Microsoft Teams channel connects your Brain Studio agent to Teams so your coworkers and customers get fast, personalized answers without leaving Microsoft’s collaboration platform. The connection runs through an Azure Bot app that you register in Azure. Jelou receives messages from Teams, runs the published flow, and returns the agent’s replies to the same chat.

​
Prerequisites

Before enabling the channel, make sure you have:
  • An active Jelou account and access to the Channels section
  • An app registration in Microsoft Entra ID (formerly Azure AD), with these three values at hand:
    • App ID (client ID)
    • App password (client secret)
    • Tenant ID
  • An Azure Bot resource tied to that registration, with the Microsoft Teams channel enabled
  • Access to the Teams Developer Portal or the Azure Portal to configure the bot’s messaging endpoint
The Microsoft Teams channel is provisioned as single-tenant only. The app type is not selectable during activation.
If you don’t see the Microsoft Teams option in the channel list, your plan doesn’t include it. Contact your administrator or the Jelou support team.

​
Enable the channel

1

Open the Channels section

Sign in to Jelou, go to Channels, and select the Microsoft Teams option.
2

Name the channel and choose the project

Give the channel a descriptive name, for example Teams - Internal support. The name must be between 4 and 50 characters.Then select the Brain Studio project the channel will connect to.
Use a name that identifies the environment as well as the channel, for example Teams - HR Production, so it’s easy to tell apart in the list.
3

Enter the Azure Bot credentials

In the second step of the modal, complete all three required fields:
  • App ID: your Azure Bot’s App ID (client ID)
  • App password: the app’s client secret
  • Tenant ID: the Azure AD tenant ID
If you leave a field empty, the form marks it in red with the message This value is required and the create button stays disabled.
4

Create and connect the channel

Click Create and connect channel. Jelou creates the channel and shows the messaging endpoint URL you need to finish the connection on Microsoft’s side.
5

Configure the messaging endpoint in Teams

Copy the URL and paste it into the bot’s messaging endpoint field. You can do this from either place:
  • Teams Developer Portal: go to Tools → Bot management, select your bot, and fill in Endpoint address.
  • Azure Portal: open the Azure Bot resource and go to Settings → Configuration → Messaging endpoint.
You can find this URL again at any time in the channel properties, so there’s no need to store it separately.
6

Build the logic in Brain Studio

Open the project in Brain Studio, select the Microsoft Teams channel in the workflows list, and start building your flow.

​
Supported content

Teams renders messages as Adaptive Cards, so the channel supports a subset of the blocks available on WhatsApp: Other limits the channel applies:
  • Media caption: 1024 characters
  • Body of messages with buttons: 1024 characters
  • File name: 255 characters

​
Channel limitations

In the builder, some nodes and tools are not available on the Microsoft Teams channel because they depend on WhatsApp or other integrations.

​
Unavailable nodes and blocks

  • HSM template
  • WhatsApp Flows
  • Video
  • Audio
  • Document and File
  • Sticker
  • Carousel
  • Numbered list
  • Webview
  • Location
  • Contact
  • Quick replies
  • Payments
  • Connect (advisor)
  • Biometrics
  • Human handoff (HubSpot, Genesys, or others)

​
Unavailable AI Agent tools

  • Call to action (send_call_to_action)
  • Transfer to agent (transfer_to_agent)
  • Jelou Shop

​
Next steps

Once the channel is connected:
  1. Send a direct message to the bot from Teams to verify the connection
  2. Check the execution logs in Brain Studio to confirm the flow runs
  3. Adjust the flow using the blocks the channel supports
Test the channel with a real user from your organization before publishing, to confirm the messaging endpoint was set correctly in the Teams Developer Portal.