Microsoft Teams

Lobu’s Microsoft Teams adapter supports direct chats, channel mentions, and interactive workflows. Under the hood, Lobu uses the Chat SDK Teams adapter with Azure Bot Framework.

GeneralLegalEngineeringSupportFinanceSalesLeadershipAgent CommunityMarket IntelligenceVenture Capital

C

Coding

online

List open PRs in lobu-ai/lobu12:01

Can't reach github.com — not in the agent's allowed domains. Grant access?12:01

Allow github.com

Allow for 1 hour12:01

Added github.com to allowed domains. 3 open PRs in lobu-ai/lobu: • #214 Fix worker memory leak • #219 Telegram adapter retries • #223 Add Bedrock provider12:01

O

Ops Assistant

online

Summarize my active Linear sprint12:01

I need the `linear` skill to query Linear. It bundles the Linear MCP and handles OAuth via Lobu.12:01

Install linear

Go ahead12:01

Installed and connected. Sprint "Week 15" (68% done): • 11 merged, 3 in review, 2 todo • Blocked: AUTH-234 (design) • At risk: API-89 (due tomorrow)12:01

A

Assistant

online

Switch to Claude Sonnet12:01

You can change the model from your settings — opens a scoped page with your current agent config.12:01

Open Settings

Done — set to claude-sonnet-4-612:01

Now running on claude-sonnet-4-6 via OpenRouter. Next messages will use the new model.12:01

Setup

1. Register a bot in the Azure Portal under Azure Bot (or Bot Framework Registration).
2. Note the App ID, App Password (client secret), and Tenant ID.
3. In the Azure Bot’s Channels section, enable the Microsoft Teams channel.
4. Run lobu connections add teams to add the connection (prompts for the app ID and app password), or run lobu init to scaffold a new project and pick Microsoft Teams in the wizard.

Configuration

Field	Required	Type	Description
appId	No	string	Microsoft App ID.
appPassword	No	string	Microsoft App Password.
appTenantId	No	string	Microsoft App Tenant ID.
appType	No	MultiTenant | SingleTenant	Microsoft App Type.
userName	No	string	Override bot username.

Connection Settings

These settings apply to all platform connections and are passed in the settings object.

Field	Required	Type	Description
allowFrom	No	string[]	User IDs allowed to interact with this connection. Omit to allow all; empty array blocks all.
allowGroups	No	boolean	Whether group messages are allowed (default true).
userConfigScopes	No	string[]	Scopes that end users are allowed to customize. Empty = no restrictions.

Authentication

The adapter supports two authentication modes:

• Password auth (default) — provide appPassword directly. Simplest setup.
• Managed Identity (MSI) — when appPassword is omitted, the adapter uses Azure Managed Identity. Useful for Azure-hosted deployments.

Features

• Direct messages and channel @mentions trigger the agent.
• Streaming responses with throttled message edits.
• Adaptive Cards for interactive elements (permission grants, user prompts, configuration).
• Access control — restrict which users or groups can interact.
• Multi-tenant and single-tenant deployment modes.

Typical Use Cases

• Internal assistant for engineering, HR, or IT teams.
• Workflow automation triggered by team conversations.
• Knowledge base bot accessible from Teams channels.