Configuring Kyvos Dialogs Bot in Microsoft Teams

Important

This section is intended for administrators only and provides a structured, implementation-focused walkthrough specific to the Kyvos Dialogs Bot deployment.
For detailed Azure procedures, refer to official Microsoft documentation.

This section outlines the required Azure configuration, bot registration, authentication setup, and Microsoft Teams deployment steps to enable secure, seamless conversational analytics within the Microsoft Teams environment.

Dialogs Bot integrates with Microsoft Teams through Azure Bot Service and Microsoft Entra ID (Azure Active Directory). The configuration process includes:

Step 1: Registering the app in Microsoft Azure for Teams Bot
Step 2: Creating and configuring an Azure Bot resource
Step 3: Setting up app settings and manifest files
Step 4: Setting up the Kyvos Bot Server

This setup ensures secure communication between Microsoft Teams, the Kyvos Bot Server, and the Kyvos platform.

Step 1: App registration in Microsoft Azure for Teams bot

To enable secure communication between Microsoft Teams and the Kyvos Dialogs Bot, you must register an application in Microsoft Azure. An app registration provides the bot with a secure digital identity that includes:

Application (Client) ID
Client Secret
Tenant ID
Defined API permissions
OpenID Connect metadata document

This identity allows Microsoft Teams to authenticate and trust the bot within your organization’s tenant.

Note

To register your application in Microsoft Azure for a Microsoft Teams bot, follow the Microsoft documentation for the topics listed in the table below.

Microsoft Documentation Topic	Description

Microsoft Documentation Topic	Description
Add App Registration	Register the bot application in Azure Active Directory.
Add Web Authentication	Configure web platform settings and redirect URIs for secure authentication. Enter the redirect URI for your app by appending auth-end to the fully qualified domain name. For example, https://Kyvos-bot-server-app/auth-end or https://<FQDN>:3978/auth-end
Create a Client Secret	Generate a client secret to enable secure communication between the bot and Azure.
Add API Permissions	Grant the required Microsoft Graph and related permissions for bot functionality.
Add Application ID URI	Define the Application ID URI to expose the bot API.
Add a Scope	Create an access scope to allow Teams to call the bot’s API on behalf of the user.
Add Client Application	Authorize Microsoft Teams client applications to access the bot API.
Update the Manifest	Modify the Azure app manifest to configure the token version and required settings.

Step 2: Creating an Azure Bot Resource

Creating an Azure Bot resource is required to enable secure and seamless integration with Microsoft Teams. It:

Registers the bot with the Azure AI Bot Service for channel connectivity
Provides a secure identity (App ID and password) for authentication
Allows Microsoft Teams to verify and trust the bot within your tenant
Enables connection to the Kyvos Dialogs bot framework for message processing
Is required for deploying the Kyvos Dialogs bot as a Microsoft Teams application

Note

Without an Azure Bot resource, the bot cannot communicate with Microsoft Teams or be deployed within the Teams environment.

To create an Azure resource bot, refer to the Microsoft documentation and follow the instructions mentioned in the Create your bot section.

Once the deployment completes, click Go to resource. You should see the Kyvos Dialogs bot and related resources listed in the resource group you selected.

Step 2.1: Adding a messaging endpoint

Configuring the messaging endpoint specifies the HTTPS URL to which Microsoft Teams sends incoming bot messages. This endpoint enables the Bot Framework Service to securely forward user interactions to your bot application for processing.

Copy the Kyvos Bot Server (https URL) https://FQDN:3978.
On the Microsoft Azure portal, in the left pane, under Settings, select Configuration.
Update the Messaging endpoint in the following format:
https://FQDN:3978/api/messages
Select Apply.
You have successfully set up a bot in the Azure Bot Service.

Step 2.2: Adding an OAuth connection settings

Adding OAuth connection settings enables secure Single Sign-On (SSO) authentication between Microsoft Teams and your bot. It allows the bot to access protected resources on the user’s behalf using Azure Active Directory credentials and defined API scopes.

In the left pane, select Configuration.
Select Add OAuth Connection Settings.
Under New Connection Setting, update the following details:
- Name: Enter a name for your new connection setting. You can use the name in the settings of your bot service code.
- Service Provider: From the dropdown list, select Azure Active Directory v2.
- Client Id: Update your Microsoft App ID.
- Client secret: Update the client secrets Value.
- Token Exchange URL: Update the Application ID URI.
- Tenant ID: Enter Common.
- Scopes: Enter api://botid-<microsoft_app_id>/access_as_user
Select Save.