Example Name

Note that you will need to construct a full URL using the [Base URI](https://learn.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#base-uri) (sometimes referred to as "Service URL") and a version path (example: `https://smba.trafficmanager.net/apis/v3/conversations/abcd1234/activities/bf3cc9a2f5de...` where `https://smba.trafficmanager.net/apis/` is the Base URI, `v3` is the version, and the remainder is the REST API action to perform).

Please refer to the [Bot Framework REST API Reference](https://learn.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#conversation-operations) for details on their API surface.


See [adaptivecards.io](https://adaptivecards.io/) for documentation on constructing card payloads.


The Microsoft Bot Framework component authenticates using OAuth 2.0 Client Credentials associated with your Azure Bot's App Registration.

To begin you will need to [create a new Azure Bot](https://learn.microsoft.com/en-us/composer/quickstart-create-bot-with-azure) or retrieve the app id and app password (client secret) for an existing bot. If creating a new bot you will likely want to set its type to "Multi Tenant" to allow using your bot across tenants.

Open the Azure Bot and ensure that [appropriate Channels are enabled and configured](https://learn.microsoft.com/en-us/azure/bot-service/bot-service-manage-channels) for your intended use case. Each will require additional configuration - [Microsoft Teams](https://learn.microsoft.com/en-us/azure/bot-service/channel-connect-teams), for example, will require a [Teams app](https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/apps-publish-overview) containing a manifest file specifying your bot's configuration with Teams.

Next, navigate to the "Configuration" blade of the bot and click "Manage" next to "Microsoft App ID". This will take you to the Azure AD App Registration for the bot. From here you are able to create a new **Client Secret** from the "Certificates & Secrets" blade. This will be your "Client secret" (some Microsoft documentation also refers to this as the "app password").

The Client ID and Tenant ID (for Single Tenant bots) can be retrieved from the "Overview" blade.

Next supply the following values to the **OAuth 2.0 Client Credentials** connection in your integration within Prismatic:

-   For **Client ID** enter the value for "Microsoft App ID" or the "Client ID" from the app registration.
-   For **Client Secret** enter the value from "Certificates & Secrets" of the app registration.
-   If your bot is configured as "Single Tenant" you will need to use the conventional **Token URL** for Azure: `https://login.microsoftonline.com/tenantId/oauth2/v2.0/token` and replace `tenantId` with the ID of your tenant.


Manage conversational interactions across platforms using Microsoft Bot Framework

[Microsoft Bot Framework](https://dev.botframework.com/) is a comprehensive framework for building enterprise-grade conversational AI experiences.
This component allows you to interact with the Bot Framework REST API to manage conversations and activities.


Trigger that validates incoming requests as coming from Bot Framework

Action Name	Action Description
Send Message	Create a message to a Conversation
Send Adaptive Card Message	Send an adaptive card message
Create Conversation	Create a new Conversation
Get Conversation Members	Get list of members of the conversation
Raw Request	Issue a raw HTTP request

Microsoft Bot Framework Connector

Integrate with customers’ other SaaS apps, fast

About the Microsoft Bot Framework Connector

Actions

Triggers

Ready to get started?