Manage Azure Bot Service Resources with Python SDK

Azure Bot Service Management SDK for Python manages Azure Bot Service resources - bots, channels, and connections - through the AzureBotService management client, authenticated with DefaultAzureCredential.

client.bots creates a bot with a location, SKU (F0 free tier with limited messages, or S1 standard/unlimited), a kind, and properties (display name, description, messaging endpoint, and Microsoft App ID/type), and gets, lists (by resource group or across the whole subscription), updates, or deletes it. client.channels configures channel integrations on a bot: Microsoft Teams (a simple enable flag), Direct Line (one or more named sites, each independently enabling v1/v3 protocol support), Web Chat (named sites with an enabled flag for the embeddable widget), plus Slack, Facebook, and Email channels via their own typed classes. Channels can be fetched by name, and list_with_keys retrieves channel secrets - for Direct Line, the per-site keys used to authenticate custom clients. client.bot_connection manages OAuth connection settings for a bot (a client ID/secret, requested scopes, and a service provider ID), used for scenarios like connecting a bot to Microsoft Graph, and connections can be listed per bot service.

Use it when you need to provision and configure Azure Bot Service infrastructure - the bot resource itself, its channel integrations, and OAuth connections - as infrastructure-as-code, rather than manually through the Azure Portal. Start with the F0 free SKU for development and move to S1 only when you need unlimited messaging in production, per the skill's own guidance.

Input is bot/channel/connection configuration (display name, endpoint, App ID, channel-specific site settings, OAuth client credentials). Output is the created/updated bot, channel, or connection resource, or channel keys for client authentication. Install it with:

pip install azure-mgmt-botservice
pip install azure-identity

Its own best practices: use DefaultAzureCredential for authentication, start with the F0 SKU for development and upgrade to S1 for production, store the MSA App ID/secret securely (in Key Vault, not in code), enable only the channels you actually need to reduce attack surface, rotate Direct Line keys periodically, prefer managed identity over client secrets for bot connections where possible, and configure CORS properly for the Web Chat channel.

It provisions channel integrations for Microsoft Teams, Direct Line, Web Chat, Slack, Facebook Messenger, and Email, and OAuth connections (for example to Microsoft Graph) via the azure-mgmt-botservice management plane paired with azure-identity.

Python developers and platform engineers provisioning Azure Bot Service infrastructure - bots, channel integrations, and OAuth connections - as part of infrastructure automation rather than manual portal configuration.