- Receive messages from Teams users, starting a new run with the message content.
- Respond directly in Teams conversations using the Bot Framework.
- Access Teams channels and messages through Microsoft Graph API tools.
Prerequisites
- An existing agent in Fleet (see Quickstart to create one)
- An Azure account with permission to create resources
- Permission to upload and install custom apps in your Microsoft Teams organization. Your Teams administrator may need to enable custom app uploading.
Set up the Teams bot
Create an Azure Bot, connect it to Fleet, and install it in Teams:1
Create an Azure Bot resource
- Go to the Azure Portal.
- Search for Azure Bot and click Create.
- Fill in the required fields:
- Bot handle: A unique identifier for your bot.
- Subscription: Select your Azure subscription.
- Resource group: Create a new one or select an existing one.
- Pricing tier and Data residency: Choose settings for your organization. See Azure Bot pricing and regionalization. A regional bot alone does not guarantee end-to-end data residency.
- Type of App: Select Single Tenant.
- Creation type: Select Create new Microsoft App ID.
- Click Review + create, then Create.
Azure no longer allows new Multi Tenant bots.
2
Get your app credentials
After the resource is created:
-
Navigate to your bot resource and click Configuration in the left sidebar.

-
Copy the Microsoft App ID and the App Tenant ID for the Fleet setup wizard.

- Click Manage Password next to the App ID.
- Click New client secret, add a description, and click Add.
- Copy the secret Value, not the secret ID. The value is only shown once; if you lose it, create a new secret.
3
Configure the Azure connection
-
In Fleet, open Integrations > Slack & Teams. In Teams Bots, click Add Teams Bot.

- Copy the webhook URL from the first screen of the Fleet wizard.
- In your Azure Bot resource, go to Configuration. Paste the URL into Messaging endpoint and click Apply. Streaming Endpoint is not required.
- Go to Channels, select Microsoft Teams, and agree to the terms of service.
- On the Messaging tab, select the cloud environment for your Teams organization and click Apply.
-
Confirm Microsoft Teams appears in the connected channels list and check its status.

4
Register and link the bot
-
Return to Fleet, click Continue to Credentials, and enter:
- Bot display name: A name for the bot.
- Azure App ID (Client ID): The Microsoft App ID from Azure.
- Azure Tenant ID: The App Tenant ID from Azure, not your Fleet workspace ID.
- Client Secret (App Password): The secret value you copied.

-
Click Continue, then Download Teams App Package. Keep the ZIP for installation.

-
Click Continue, select your agent, and click Finish. Confirm Fleet displays Teams bot configured successfully.

5
Install and test the bot in Teams
- In Teams, go to Apps > Manage your apps > Upload an app.
-
Select Upload a custom app and choose the ZIP downloaded from Fleet.

- Follow your organization’s approval process if required, then add the app to a team or chat.
- Send a message and confirm the agent replies. In channels and group chats, @mention the bot.
Link an existing bot to an agent
If you selected an agent during setup, the bot is already linked. Otherwise, use either option:- In Fleet, open Integrations or Slack & Teams, select the bot, choose an agent, and click Attach.
- Open the agent’s Channels drawer, select Teams, and choose the bot.
Add Teams tools
Fleet attempts to add theteams_reply_to_message tool when you link an agent to a Teams bot. It may appear as Teams Bot Reply. Use this tool to send a reply to the originating Teams conversation. A response in Fleet alone is not a Teams reply. Bot replies use the bot credentials and do not require separate Microsoft Graph authorization.
To read channels or take other Teams actions, add the relevant Teams tools in the agent’s Connections drawer. Microsoft Graph tools may require authorization. The teams_bot_send_proactive_message tool is for messages outside a direct reply, such as notifications.
Troubleshooting
Resolve installation errors
Teams can reportInvalidUserId with “Incorrect bot configuration/registration, please check the bot settings.” This message alone does not identify the cause.
Before recreating the bot or changing settings, check the following:
- Azure and Fleet: Confirm the Teams channel is enabled for the correct cloud. Verify the bot’s App ID, tenant ID, and Single Tenant app type. Use the same IDs in Fleet, and finish setup with an agent linked.
- App package: In the ZIP’s
manifest.json, check thatbots[].botIdmatches the Azure Bot’s App ID. The top-levelididentifies the Teams app and can differ from the bot ID. - Teams organization: Install in the intended organization and confirm its policies allow the custom app.
- The exact failure time and time zone, the step reached, and an error screenshot.
- The failed request URL, HTTP status, error response, and request or correlation IDs, if available.
- The Azure Bot’s App ID, App Tenant ID, app type, and Teams channel status and cloud environment.
- The exact app ZIP used for the failed installation.
Agent does not respond
- Check the Fleet run for a
teams_reply_to_messagecall and its result. If the tool is missing, add it to the agent. If the agent does not call it, update its instructions and test again. Instructions do not guarantee a tool call. - Check the Fleet thread for approvals, the Feed tab for errors, and whether the agent’s channels are paused.
- In channels and group chats, @mention the bot and confirm the app is installed in that team or group chat.
- Verify the Azure messaging endpoint matches Fleet’s webhook, and the bot is linked to the intended agent.
- Check the App ID, tenant ID, and client secret value in Fleet against Azure. Confirm the secret has not expired. Saving credentials in Fleet does not test Azure authentication.
Connect these docs to your agent of choice via MCP for real-time answers.

