Microsoft Teams Integration¶

Overview ¶

The Microsoft Teams Integration serves as a bridge between Microsoft Teams and Dataiku’s Generative AI capabilities. It allows users to interact with Dataiku Agents and LLMs directly within Teams, enabling seamless access to data insights and automated responses in both chats and channel conversations.

Key Features

Interactive Bot: Chat directly with Agents configured in Dataiku.
Azure Bot Service Integration: Use Azure Bot Service to connect Microsoft Teams to your Dataiku webapp backend.
Teams Conversation Support: Works in chats and in channel conversations where the app has been added.

Setup ¶

Pre-requisites ¶

The Microsoft Teams Integration is provided by the “Dataiku Agents on Microsoft Teams” plugin, which you must install. Please see Installing plugins.

You will need administrative access to Microsoft Azure and Microsoft Teams, alongside write permission in a Dataiku Project and code execution permission to configure the integration.

The Microsoft Teams Integration uses a webapp in DSS, with the backend exposing the messaging endpoint used by Azure Bot Service and relaying messages back & forth between Microsoft Teams and the Agent. The backend must be running to process events. Enable auto-start backend in the Edit tab to ensure it runs automatically.

DSS must be reachable through a public HTTPS URL so Microsoft Azure can call the messaging endpoint exposed by the webapp. DSS must also have outbound network access.

This section details the setup of the Azure Bot resource, the generation of the necessary credentials, and the configuration of the Dataiku Webapp backend to establish the connection.

Create the Azure Bot Service ¶

Navigate to https://portal.azure.com and create the bot resources. This is the bot that you will later install into Microsoft Teams to interact with the Dataiku Agent or LLM.

During setup, make sure you:

Create an Azure Bot resource. If you choose Create new Microsoft App ID, Azure will also create the related App Registration. You can also create the app registration in advance and link it during bot creation.
Under Azure Bot -> Settings -> Configuration, set Messaging Endpoint to your DSS public base URL plus the endpoint displayed in the Dataiku webapp setup page.
Under Azure Bot -> Settings -> Channels, add the Microsoft Teams channel.

Note

The full messaging endpoint must be publicly accessible over HTTPS.

If Microsoft Teams and the Azure Bot resource run in different tenants:

Go to the App Registration linked to the Azure Bot that you created.
In Azure Bot -> Settings -> Configuration, select Manage Password next to Microsoft App ID to open the corresponding app registration.

Under Manifest, make sure the JSON contains the following values:

"accessTokenAcceptedVersion": 2,
"signInAudience": "AzureADandPersonalMicrosoftAccount"

Save the manifest.

Generate App Credentials ¶

To let Dataiku authenticate with your bot, create the application credentials in Azure:

Go to the App Registration linked to the Azure Bot that you created.
In Azure Bot -> Settings -> Configuration, select Manage Password next to Microsoft App ID to open the corresponding app registration.
Under Certificates & secrets, create a new client secret.
Copy the secret value immediately and store it somewhere safe. Azure will not show it again.
In the Overview tab, also copy the Application (client) ID.

Important

Treat your client secret like a password. Never share it or commit it to version control. If it is compromised, rotate it immediately in the Azure portal.

Create and Configure the Visual Webapp in Dataiku ¶

In the webapp Edit tab, configure the following:

Azure Tenant ID: Paste the Microsoft Entra tenant ID where your Azure Bot and app registration are hosted.
Azure Bot Service Microsoft App ID (client ID): Paste the application client ID.
Azure Bot Service Microsoft App Password (client secret): Paste the bot client secret.
Agent/LLM: Select the Dataiku Agent or LLM to use for generating responses.

Save to apply your configurations.

When you save the webapp, the backend should automatically start (a notification indicates that the backend is starting).

If the backend does not start automatically:

Go to the Actions panel on the right side of the screen.
Select Start backend to manually start it.

In the backend configuration:

Make sure Auto-start backend is enabled.
Make sure Require authentication is disabled.

Note

For Dataiku Cloud, add the webapp ID to Administration -> Settings -> Security & Audit -> Other security settings -> Webapps -> Public webapps.

Test the Bot in Azure ¶

Before installing the app in Microsoft Teams, run a quick test in Azure to confirm that Microsoft can reach your Dataiku webapp.

In the Azure Bot resource, open Settings -> Test in Web Chat.
Send a message in the chat window. The Agent or LLM you configured earlier should respond.
Check the DSS webapp Logs tab if the bot does not respond.

Generate the Teams App Manifest ¶

Before you can install the Agent in Teams, you need a Teams app manifest. You can create one in the Teams Developer Portal or with the manifest creator available in the webapp.

Scroll down to the Manifest creator card in the webapp.
Enter the Teams app details you want to use, such as the name and icons.
Select Create manifest zip to download the manifest.

Install the App in Teams ¶

Upload the manifest to Microsoft Teams or to your organization’s app catalog.

In Teams, open Apps in the left sidebar, then select Manage your apps.
Select Upload an app, then choose the manifest zip file that you created earlier.

Note

You may need administrator approval before you can install the app.

Test the integration in Microsoft Teams, as per the Usage section below.

Usage ¶

In Microsoft Teams:

Open the bot in a chat, or add the app to a channel where you want to use it.
Send a message in the chat or @mention the app in a channel where it has been added.
Check the DSS webapp Logs tab if the bot does not respond.