foundry-teams-bot

Generate Teams bot code, Azure infrastructure, and sideload packages for Foundry hosted agents.

5|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-teams-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-teams-bot
Source: https://github.com/aiappsgbb/awesome-gbb/tree/main/skills/foundry-teams-bot
Command: npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-teams-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you expose an already-deployed Microsoft Foundry Hosted Agent as a Microsoft Teams bot, so users can chat with your agent directly inside Teams with the right infrastructure and Teams app manifest.

Core Features & Use Cases

  • Teams bot frontend generation: Creates bot code (bot.py/app.py), container deployment assets (Dockerfile), and the Teams sideload package (manifest.json + icons).
  • Azure infrastructure for hosting and routing: Deploys Azure Bot Service with the Teams channel plus an Azure Container Apps-based hosting layer for ACA, including UAMI identity and RBAC.
  • Foundry integration with streaming + files: Connects to the Foundry agent via Responses or Invocations patterns (depending on hosted agent protocol) and supports sending agent-generated reports to Teams via the FileConsentCard flow.

Quick Start

Use the skill to connect a deployed Foundry hosted agent to Teams by providing your agent name and Foundry project endpoint, then run the postprovision step to build the Teams package zip for sideloading.

Frequently Asked Questions about foundry-teams-bot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect a Microsoft Foundry hosted agent to Microsoft Teams?

To connect a Foundry hosted agent to Microsoft Teams, you need a bot frontend that bridges the Teams channel to your agent's endpoint. This involves generating bot code, configuring Azure Bot Service, and packaging a Teams sideload manifest for deployment.

How does streaming work for a Foundry agent in a Teams bot?

Streaming for a Foundry agent in a Teams bot works by handling Responses or Invocations SSE protocols. The generated bot code correctly routes these streaming patterns to ensure real-time message delivery within the Teams chat interface.

Do I need managed identity to deploy an Azure bot for Foundry agents?

Yes, you need User Assigned Managed Identity (UAMI) to deploy an Azure bot for Foundry agents. The deployment includes configuring UAMI-based authentication and RBAC permissions for the Azure Container Apps hosting layer to securely access Foundry resources.

Can I send agent-generated files through a Microsoft Teams bot?

Yes, you can send agent-generated files through a Microsoft Teams bot using the FileConsentCard flow. This mechanism allows the bot to deliver reports and other generated content directly to users within the Teams chat experience.

What is included in a Teams sideload package for a Foundry bot?

A Teams sideload package for a Foundry bot includes a manifest.json file compliant with Teams manifest v1.21, application icons, and the necessary configuration to register the bot within the Microsoft Teams app store for internal distribution.

Why is my Azure Container Apps bot failing to reach the Foundry agent endpoint?

Your Azure Container Apps bot may fail to reach the Foundry agent due to missing environment variables or incorrect UAMI RBAC permissions. The generated infrastructure includes validation guardrails and retry/reset logic to help diagnose these protocol and authentication issues.