Skip to main content



In order to create a bot on Teams that will be connected to your dydu bot, we will follow these steps:

  1. Azure Portal: create a new configuration and setup connection with dydu. The operations to do on this part are the following:

    • Create a resource group
    • Create a Azure bot
    • Set up Microsoft credentials
    • Connect resource group to azure bot
  2. Dydu Channels: configure your dydu bot and choose consultation space & language

    • Create Teams configuration
    • Download the bot application
  3. Teams: publication

    • Publish the bot in Teams

Azure Portal

Create Resource group

  1. Sign in to the Azure portal. (

  2. Select Resource groups.

  1. In the Resource Groups page, click Create button

  1. Fill the following values:
    • Subscription: Select your Azure subscription
    • Resource group: Enter a new resource group name.
    • Region: Select an Azure location

  1. Click on Review + create button

  1. Select Create. It takes a few seconds to create a resource group.

  1. The resource group list is refreshed

  1. Then, return to the home page.

Create Azure bot

  1. Select Bot services

  1. Click on Create

  1. Look for Azure Bot in the Bot Services list.
    • Click on Load more at the bottom of the page if Azure Bot is not displayed on first page.
    • Then, click on Azure Bot.

  1. Click on Create.

  1. Fill the required information:
    • Bot handle: choose a name (you can change it after)
    • Subscription: always Azure CSP
    • Resource group: select the resource group that you have created just before
    • Type of app: select Multi-Tenant

  1. Then, click on Review + Create button.

Wait a few seconds. Then you can see this page:

  1. Click on Create button.

  1. Click on Go to resource button

  1. Click on configuration in the left menu

Credentials in azure

Here you can find your Microsoft App ID:

  1. Click on Manage to create the Microsoft App password in Certificates

  1. Click on New client secret

  1. Fill with the required information:

    • description: a description of the client
    • expires: select “24 months”

  2. Click on the Add button

  1. Important: Copy the value of the client secret and save this value since later you will not be able to see.

Create connector between azure service and microsoft teams

  1. Go back to the home page and open your created bot.

  1. Click on Channels in the left menu.

  1. Click on Microsoft Teams icon.

  1. Click on Save

  1. Accept terms of services

  1. You can close the open window after accepting the terms of use.

  1. Click on Configuration in the left menu to configure the endpoint of the connector. The endpoint to use is the following:

  1. Click on Apply

Dydu Channels

Create Teams configuration

  1. Connect to the BMS.

  2. Then go to Integration > Channels.

  3. Clic on “Create”.

  4. Give it a name, click on Teams icon to select it, and click on “Start the integration”.

IMPORTANT: the name used for configuration will be the name that will appear to contact your bot in Teams.

  1. Choose the consultation space and language your Teams chatbot will use. If your chatbot only has one language and one space you don't need to make a choice.

  2. Click on "Continue with Teams account"

  3. Fill with the ID and the password you copied before from MS Azure and fill the different elements of your bot presentation in Teams:

Bot descriptions

These are the descriptions displayed for your bot within Teams.

These fields are mandatory.

The short description must not exceed 80 characters and must not be repeated in the full description.

The full description must not exceed 4000 characters.

  • Bot names

This is the name displayed to designate your bot within Teams.

The "short name" field is mandatory and must not exceed 30 characters.

The "long name" field is not mandatory, you can use it if the chosen name exceeds 30 characters. It must not exceed 100 characters.

  • Bot avatar

Your bot in Teams must have two icons:

  • the main avatar of the bot and
    • it must respect a dimension of 32*32 pixels and can be in colour
  • the icon of the application (which appears in the sidebar of Teams
    • it must respect a dimension of 192 x 192 pixels and must be transparent

The accepted format for these icons is PNG.

  • Name of the bot's author

This is the name of the bot creator. This is a required field that must not exceed 30 characters.

  • Available URLs

These are the urls :

  • Website
  • Privacy policy
  • Terms of use

The urls are required.

They are displayed in the "About" tab within your bot Teams:

Download the bot application

Save the configuration ZIP and click on “Save and quit”.

NB: if required inputs are not filled, you won't be able to download the ZIP configuration (no button will be displayed to do so).


Publish the bot on Teams

  1. Go on Teams.

  2. Click on Apps at the bottom left corner of your screen.

  1. Click on Manage your applications at the bottom left of your screen.

  1. Click on the Submit an application to your organisation button

This will take you to the page listing the different applications you have submitted to your organisation. Click again on Submit an application.

  1. Select the ZIP configuration you saved before.

  2. Your application is now present in the list.

  1. Once approved by your administrator you can find it in the application catalog designed for your organization. You may need to restart your Teams to see the app appear in the catalog.To open the application catalog of your organisation, click on Build for your org on the left.

  1. Click on the application you created.

  1. Then click on the "Add" button.

  1. You can start the dialog with your bot.

Features available for a dydu bot under Teams

The following tables show the supported and unsupported features for a dydu bot under MS Teams.

  • Supported = The functionality is available and works as part of a dydu bot in MS Teams
  • Unsupported = The functionality cannot be implemented for a dydu bot in MS Teams

Formatting the response

"Heading" tagSupported
Text colorSupported
Text background colorSupported
Text alignmentSupported
Ordered listSupportedBullets are not displayed but the list hierarchy is respected and displayed
Non ordered listSupportedScheduling numbers/letters are not displayed but the list hierarchy is respected and displayed
Link to an external URLSupported
Link to knowledge (reword)Supported
Display a tableSupported
Split bubbleSupported
Images / File from the gallerySupported
Using mathematical expressionsUnsupported
Display a side panelSupported

Features available for response

Step actionsSupported
Alternative answersSupported
Use a variable in an answerSupported
Automatically redirected to an external URLUnsupported
Automatically redirected to a knowledgeSupported
Display a templateUnsupported
Use a GUI actionUnsupported
Make an automatic switch of consultation spaceUnsupported1 bot Teams = 1 language, 1 consultation space
Modify the value of a variable before actionSupported
Modify the value of a variable after actionSupported
Requesting user satisfactionUnsupported

General sentences

Response to misunderstood sentencesSupported
Too many misunderstood sentencesSupported
Answer to long sentencesUnsupported
Answer to empty sentencesSupported
Click on the linksUnsupported
Links open in new windowsUnsupported
Response to unpublished knowledgeSupported
Default response when action is emptySupported
The answer is available in the default languageUnsupported
The answer is not defined for this consultation spaceSupported
The answer is available from another consultation spaceUnsupported
Refocusing sentenceSupported
Internal error responseSupported
Introduction of rewordingSupportedThe rewords are displayed listed AND in buttons. Only buttons are clickable. Buttons contain the title of the knowledge.
General suggestion for reformulationsSupportedThe text defined in the general suggestion must be the same as the title of the knowledge to which this general suggestion redirects.

Knowledges type

Simple knowledgeSupported
Decision treeSupported
Complementary answerSupported
Internaut activityUnsupported
Slot fillingSupported


Capture user intentSupported
Use a context conditionSupported
Using a WSSupported

Features specific to the dydu chatbox

Welcome sentenceUnsupported
Information bannerUnsupported
Top knowledgeUnsupported
Disclaimer GDPRUnsupportedManaged in the privacy policy and the TOS of the Teams application. To be defined by the customer when configuring their Teams bot application.
GDPR recovery requestUnsupported
GDPR deletion requestUnsupported
Allow the end-user to change the languageUnsupported1 bot Teams = 1 language, 1 consultation space
Allow the end user to change the consultation spaceUnsupported1 bot Teams = 1 language, 1 consultation space