What problem does it solve? Setting up an Azure Bot involves many disconnected steps—identity creation, bot registration, channel configuration, and deployment—which are error-prone when done manually through the portal or ad-hoc CLI commands. ## Core Features & Use Cases - Full Bot Lifecycle: Create Azure Bot resources with Single-Tenant app registrations or User-Assigned Managed Identities, including resource groups and SKU selection. - Channel Configuration: Connect bots to Microsoft Teams, Slack, Telegram, Direct Line, Facebook Messenger, Email, and Web Chat with the correct credentials for each. - Deployment to App Service: Provision App Service plans and web apps, set MicrosoftApp* configuration values, and deploy bot code via zip deploy. - Use Case: You want to connect an OpenClaw agent to Microsoft Teams. Use this Skill to create the app registration, register the bot, enable the Teams channel, and deploy the messaging endpoint end to end. ## Quick Start Create an Azure Bot named my-support-bot in a new resource group with a single-tenant identity and connect it to Microsoft Teams.