Overview
For organizations running on Microsoft 365, the Teams integration brings your Claws into the environment your team already uses every day. Claws appear as native bot users inside Teams: they show up in the member list, respond in channels, and send Adaptive Cards that look and feel like any other Teams app. There is no external UI to juggle; your AI agent is just another participant in the conversation.
The integration is built on the Azure Bot Framework, which means it works with your existing Azure AD permissions, tenant policies, and compliance configurations. If your organization has strict IT governance requirements, the Teams integration was designed with that in mind.
What Your Claw Can Do
Participate in channels. Add your Claw to any Teams channel. It can monitor conversations, respond when mentioned, or proactively post updates based on triggers from other integrations. Channel messages are processed in real time through the Azure Bot Framework’s messaging pipeline.
Handle direct messages. Team members can message your Claw privately for one-on-one interactions: asking questions, requesting reports, or triggering workflows without cluttering a shared channel.
Send Adaptive Cards. Instead of plain text, your Claw can respond with rich Adaptive Cards that include formatted text, images, buttons, and input fields. Use cards to present structured data, collect approvals, or create interactive mini-workflows directly inside Teams.
React to events. Beyond messages, Claws can respond to channel membership changes, file uploads, tab interactions, and other Teams activity events. These events can trigger automated workflows across your connected tools.
Respect tenant policies. Because the integration uses Azure Bot registration, your Claw operates within the same security boundary as your other Teams apps. IT admins can control which users and channels have access to the Claw using standard Teams app permission policies.
Who Can Reach Your Claw
Teams whitelisting controls who can communicate with your Claw:
- By user. Whitelist specific Teams users. Only messages from those users are processed.
- By channel. Whitelist specific channels. The Claw only operates in designated channels.
- By Teams group. Whitelist Teams groups. Only members of the group can interact.
- By app permission policy. IT admins can restrict Claw access using standard Teams app policies, layering organizational controls on top of ClawStaff whitelisting.
This works alongside three Claw scoping levels:
Private Claw. Only the creator interacts via direct message. The Claw is a personal assistant within Teams, and nobody else can message it. Example: a personal Claw that you DM to check your calendar, search for documents, or get a summary of unread channels.
Team Claw. Whitelisted team members share the Claw in a specific channel. Only the Engineering team can interact with the Claw in the Engineering channel. Other departments see the bot in the member list but get no response when they message it.
Organization-wide Claw. Any member of the Teams tenant can interact. The Claw serves as a company-wide resource: HR assistant, IT help desk, or knowledge bot. Whitelisted to the tenant, so external users cannot interact.
How It Works
-
Register an Azure Bot. From the ClawStaff dashboard, follow the setup guide to register an Azure Bot in your Azure portal. ClawStaff provides the messaging endpoint and configuration values you need.
-
Install the app in Teams. Upload the generated Teams app manifest to your organization’s app catalog, or sideload it for testing. The manifest defines your Claw’s display name, icon, and the scopes it operates in (personal, team, or group chat).
-
Configure your Claw. In the ClawStaff dashboard, connect the Azure Bot credentials to your Claw. Define which channels to monitor, set trigger conditions, and configure Adaptive Card templates for structured responses.
-
Deploy to a ClawCage. Your Claw is deployed inside an isolated Docker container. The Azure Bot credentials are securely injected at runtime. The container receives messages through the Bot Framework’s messaging pipeline and responds through the same channel.
-
Claw joins your team. Once deployed, your Claw appears as a bot user in Teams. Team members can mention it, message it directly, or interact with it through Adaptive Cards. All processing happens inside the ClawCage, with data flowing only between the container, the Azure Bot Framework, and any integrations you have explicitly connected.
Security
- Azure AD integration. Your Claw authenticates through Azure AD, operating within your tenant’s existing security policies and conditional access rules.
- Credentials encrypted at rest. Azure Bot credentials, including the app ID and client secret, are encrypted before storage and only decrypted inside the ClawCage at runtime.
- Tenant isolation. Each organization’s Claws run in separate containers with no shared state between tenants. Your Teams data never crosses organizational boundaries.
- IT admin controls. Teams app permission policies let IT admins restrict which users and channels can interact with your Claw. No special exceptions or workarounds are required.
- Audit logging. Every message sent, Adaptive Card rendered, and workflow triggered by your Claw is logged and available in the ClawStaff dashboard.
- Revoke anytime. Remove the bot registration from Azure or uninstall the Teams app. Credentials are immediately invalidated and the Claw stops receiving events.
Cross-Integration Workflows
The Teams integration works well alongside your other connected tools:
- Teams to Jira. A team member reports an issue in a Teams channel. Your Claw creates a Jira ticket with the relevant details, assigns it based on the channel context, and posts the ticket link back as an Adaptive Card with a direct link.
- Teams to Confluence. After a meeting discussion in Teams, your Claw summarizes the conversation and creates a Confluence page with decisions, action items, and owners. The page link is posted back to the channel.
- GitHub to Teams. A deployment completes on GitHub Actions. Your Claw posts a formatted Adaptive Card in the relevant Teams channel with the deployment status, commit summary, and links to the release.
- Approval workflows. Your Claw posts an Adaptive Card with approve/reject buttons. When a team member clicks a button, the Claw processes the response and updates the corresponding record in Jira, Notion, or your internal system.