Azure Bot Services¶
Deprecation: Handover Providers in Endpoint Settings
The Handover Providers section in the Endpoint settings has been deprecated in 4.97. The removal date is September 2025. We encourage you to try our new Handover Providers interface, which offers greater flexibility for managing your integration with contact centers. For a smooth migration, refer to the migration guide.
Within our Cognigy.AI platform, you're able to connect your Cognigy Agent to Azure Bot Services by using our Azure Bot Services Endpoint integration.
Generic Endpoint Settings¶
Find out about the generic endpoint settings available with this endpoint on the following pages:
- Endpoints Overview
- Data Protection & Analytics
- Transformer Functions
- NLU Connectors
- Session Management
- Handover Settings
- Real-Time Translation Settings
Supports Inject & Notify
You can use the Inject & Notify functionality with this type of Endpoint.
Specific Endpoint Settings¶
The Azure Bot Services Settings dropdown menu is where Cognigy.AI needs to be provided with the credentials to connect with an Azure Bot Services deployment.
Access Scope¶
This setting determines who can access this application, choosing being Multi Tenant and Single Tenant.
Restrict to Azure AD Accounts¶
When choosing Multi Tenant, you will have an additional toggle. The Restrict to Azure AD Accounts setting prevents public access to your Endpoint, and only allows access to the Teams' accounts that are managed by an organization in Azure Active Directory.
Microsoft App ID¶
This value is the Microsoft App ID, which is obtained in the settings page of your bot in the Azure Bot Services Dashboard.
Microsoft App Password¶
This value is the Microsoft App Password of your Bot, also referred to as the Client Secret. This is obtained by creating a new Client Secret in the App Registrations page for your bot in the Azure Bot Services Dashboard.
SSO Connection Name¶
This value is the SSO Connection Name when using this endpoint with an SSO integration.
Help Center
More detailed information on how to set up an Azure Bot Services Endpoint refer to the Help Center articles.
Microsoft Teams¶
As of release v4.9, the display changes for clicked postback buttons in a Microsoft Teams chat.
When clicking the postback button in a quick reply, gallery, list, or button configuration, the button title is displayed now on the user side of the chat. For other Azure bot service channels, this change is not relevant.
Channel Priority when using Azure Bot Services¶
You can use the Azure Bot Services Endpoint to serve multiple channels, such as Line, Messenger, Microsoft Teams, and others.
To define where the output will be delivered, select these channels in the Say, Question, or Optional Question Nodes.
However, the sequence of using these channels in the Node is determined by their fixed priority.
Priority rules exist for the following supported Azure Bot Services channels:
- Line
- Messenger
- Microsoft Teams
- Slack
- SMS
- Azure Bot Services
- AI
Examples¶
Consider the following examples when using the Azure Bot Services Endpoint from the perspective of channel priority.
Example 1
The Say Node is configured with AI, Azure Bot Services, and Microsoft Teams channels.
Result: The user will receive the text output from the Microsoft Teams channel.
Example 2
The Question Node is configured with AI and Azure Bot Services channels.
Result: The user will receive the text output from the Azure Bot Services channel.
Example 3
The Optional Question Node is configured with only the AI channel.
Result: The user will receive the text output from the AI channel.