Teams
Sign in to the Azure portal. (https://portal.azure.com/)
Select Resource groups.
In the Resource Groups page, click Create button
Fill the following values:
Subscription: Select your Azure subscription
Resource group: Enter a new resource group name.
Region: Select an Azure location
Click on Review + create button
Select Create. It takes a few seconds to create a resource group.
The resource group list is refreshed
Then, return to the home page.
Create Azure bot
Select Bot services
Click on Create
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.
Click on Create.
Fill the required information:
Bot handle: it will be the name of your bot Teams. It can be changed later on the Azure portal.
Subscription: always Azure CSP
Resource group: select the resource group that you have created just before
Type of app: select Multi-Tenant
Then, click on Review + Create button.
Wait a few seconds. Then you can see this page:
Click on Create button.
Click on Go to resource button
Click on configuration in the left menu
Credentials in azure
Here you can find your Microsoft App ID:
Click on Manage to create the Microsoft App password in Certificates
Click on New client secret
description: a description of the client
expires: select “24 months”
Click on the Add button
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
Go back to the home page and open your created bot.
Click on Channels in the left menu.
Click on Microsoft Teams icon.
Click on Save
Accept terms of services
You can close the open window after accepting the terms of use.
Click on Configuration in the left menu to configure the endpoint of the connector and fill in the Messaging endpoint field and check the Enable Streaming Endpoint box.
NOTE
If you are on a app1 serveur, the endpoint to use is: https://sso.cloud.dydu-priv.com/gateway/api/dydubox_connector/teams/messages
On the sandbox serveur, the endpoint is: https://experimental.cloud.dydu-priv.com/gateway/api/dydubox_connector/teams/messages
On the uat serveur, the endpoint is: https://staging-sso.dydu-priv.com/gateway/api/dydubox_connector/teams/messages
Click on Apply
Dydu Channels
Create Teams configuration
Connect to the BMS.
Then go to Integration > Channels.
Clic on “Create”.
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.
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.
Click on "Continue with Teams account"
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).
Teams
Publish the bot on Teams
Go on Teams.
Click on Apps at the bottom left corner of your screen.
Click on Manage your applications at the bottom left of your screen.
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.
Select the ZIP configuration you saved before.
Your application is now present in the list.
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.
Click on the application you created.
Then click on the "Add" button.
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
| Feature | Support | Comment |
|---|---|---|
"Heading" tag | Supported | |
Bold | Supported | |
Italic | Supported | |
Underline | Supported | |
Text color | Supported | |
Text background color | Supported | |
Text alignment | Supported | |
Indentation | Supported | |
Ordered list | Supported | Bullets are not displayed but the list hierarchy is respected and displayed |
Non ordered list | Supported | Scheduling numbers/letters are not displayed but the list hierarchy is respected and displayed |
Link to an external URL | Supported | |
Link to knowledge (reword) | Supported | |
Display a table | Supported | |
Split bubble | Supported | |
Images / File from the gallery | Supported | |
Smiley | Supported | |
Using mathematical expressions | Unsupported | |
Display a side panel | Supported |
Features available for response
| Feature | Support | Comment |
|---|---|---|
Step actions | Supported | |
Alternative answers | Supported | |
Use a variable in an answer | Supported | |
Automatically redirected to an external URL | Unsupported | |
Automatically redirected to a knowledge | Supported | |
Display a template | Unsupported | |
Use a GUI action | Unsupported | |
Make an automatic switch of consultation space | Unsupported | 1 bot Teams = 1 language, 1 consultation space |
Modify the value of a variable before action | Supported | |
Modify the value of a variable after action | Supported | |
Requesting user satisfaction | Unsupported |
General sentences
| Feature | Support | Comment |
|---|---|---|
Response to misunderstood sentences | Supported | |
Too many misunderstood sentences | Supported | |
Answer to long sentences | Unsupported | |
Answer to empty sentences | Supported | |
Click on the links | Unsupported | |
Links open in new windows | Unsupported | |
Response to unpublished knowledge | Supported | |
Default response when action is empty | Supported | |
The answer is available in the default language | Unsupported | |
The answer is not defined for this consultation space | Supported | |
The answer is available from another consultation space | Unsupported | |
Refocusing sentence | Supported | |
Internal error response | Supported | |
Introduction of rewording | Supported | The rewords are displayed listed AND in buttons. Only buttons are clickable. Buttons contain the title of the knowledge. |
General suggestion for reformulations | Supported | The text defined in the general suggestion must be the same as the title of the knowledge to which this general suggestion redirects. |
Knowledges type
| Feature | Support |
|---|---|
Simple knowledge | Supported |
Decision tree | Supported |
Complementary answer | Supported |
Internaut activity | Unsupported |
Slot filling | Supported |
Other
| Feature | Support |
|---|---|
Capture user intent | Supported |
Use a context condition | Supported |
Metabot | Supported |
Using a WS | Supported |
SAML | Supported |
Features specific to the dydu chatbox
| Feature | Support | Comment |
|---|---|---|
Welcome sentence | Supported | |
Information banner | Unsupported | |
Top knowledge | Unsupported | |
Autosuggestion | Unsupported | |
Disclaimer GDPR | Unsupported | Managed in the privacy policy and the TOS of the Teams application. To be defined by the customer when configuring their Teams bot application. |
Onboarding | Unsupported | |
GDPR recovery request | Unsupported | |
GDPR deletion request | Unsupported | |
Allow the end-user to change the language | Unsupported | 1 bot Teams = 1 language, 1 consultation space |
Allow the end user to change the consultation space | Unsupported | 1 bot Teams = 1 language, 1 consultation space |
Last updated
