Overview of Microsoft Teams Bot Capabilities｜Mastering Microsoft Teams Bots 1.3

1.3 Overview of Microsoft Teams Bot Capabilities

In the previous section, we explored the architecture of Microsoft Teams as a platform — a landscape of channels, tabs, messaging surfaces, and integrated services. Now, let’s zoom in and focus specifically on what bots can do within that landscape.

Bots are among the most powerful and flexible components you can build for Microsoft Teams. They’re not just responders to user commands — they are fully interactive agents that can initiate workflows, surface data, and automate repetitive tasks.

To build effective bots, it's important to understand the scope of capabilities available to you as a developer. This section lays out what bots can (and cannot) do, where they can live inside the Teams interface, and how they can interact with users and services.

1.3.1 Modes of Interaction: Where Bots Can Live

• Personal Chat (1:1): Direct conversation for personalized workflows and reminders.
• Group Chat: Shared conversation context with multiple users. Great for collaborative tasks.
• Channel (Team): Bots can respond to mentions and serve shared team-wide functions.
• Proactive Messaging: Bots can initiate messages or alerts based on triggers.
• Task Modules & Adaptive Cards: Rich interactions with modals and structured cards.

1.3.2 What Teams Bots Can Do

• Respond to Messages: Listen and reply to user messages using rich formatting.
• Understand Intent: Integrate with LUIS or OpenAI for natural language processing.
• Send Adaptive Cards: Use JSON-based rich messages with buttons, inputs, and visuals.
• Access Microsoft 365 Resources: Through Graph API (calendars, files, users, etc.).
• Send Proactive Messages: Trigger conversations programmatically from backend services.
• Authenticate Users: Use Azure AD and Teams SSO for secure access tokens.
• Provide Message Extensions: Slash commands, search boxes, and action menus.

1.3.3 What Bots Can’t Do (Yet)

• Bots can’t fully control Teams UI layout outside approved surfaces.
• They can’t access data without explicit Graph API permissions.
• Bots cannot impersonate users — all messages are clearly labeled as sent by the bot.

1.3.4 Real-World Example: A Helpdesk Bot

Imagine a Helpdesk Bot:

• The user says: "I can’t access my email."
• The bot responds with a card offering common fixes or a "Create ticket" button.
• The user completes a form via Task Module.
• The bot submits the ticket to a backend system (e.g., Zendesk) using authenticated Graph API.
• Later, the bot sends proactive updates on ticket status.

This scenario leverages message handling, Adaptive Cards, Task Modules, API integration, authentication, and proactive messaging — all from a single Teams bot.

1.3.5 Summary: Think Beyond Chat

Bots in Microsoft Teams are not just text responders. They are workflow agents, notification hubs, form handlers, and integrated assistants. Their true strength lies in their ability to operate within the natural flow of work — where users already are.

In the next section, we’ll get hands-on: setting up your environment and building your very first bot.