> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scoutos.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Microsoft Teams
> Integrate Microsoft Teams with Scout to let agents respond to messages, search history, and deliver your daily briefing directly in your channels.
Connecting Teams to Scout lets your agents work where your team already communicates. An agent can post pipeline summaries to a sales channel, summarize a support thread before a rep picks it up, or answer questions in a dedicated help channel. Setup takes about five minutes, and you'll be prompted to connect to Teams directly in Scout.
## What Scout Agents Can Do in Teams
| Capability | Example |
| ----------------------- | ------------------------------------------------------------------ |
| **Post to channels** | Share daily pipeline summaries, incident alerts, or weekly digests |
| **Read threads** | Understand context from a conversation before responding |
| **Search history** | Find past decisions, discussions, or referenced documents |
| **React and reply** | Acknowledge messages and continue in-thread conversations |
| **Respond to mentions** | Answer questions when someone mentions the agent in a channel |
## How to Connect Teams
Go to [studio.scoutos.com/integrations](https://studio.scoutos.com/integrations), find **Microsoft Teams bot**, and click **Add Connection**. You'll see a pop-up window to a Teams authorization page.
Enter the Teams Tenant ID for the workspace you want to connect, then sign in with your account.
This step must be completed by an admin of your Microsoft Teams tenant.
**Deployments (channel-first)**
Use this when you want the agent to live in a Teams channel, responding and staying in the conversation rather than acting only on demand.
1. Go to your agent's **Settings**
2. Click **+ Add Deployments** → **Teams**
3. In the configuration panel, select your **Teams Workspace** and the **Channel** where the agent should operate
4. Configure the deployment options (see below) and click **+ Add channel** to save
| Option | What it does |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Workspace** | The Teams workspace to deploy to. Must be connected first. |
| **Channels** | The specific channel this deployment monitors and responds in |
| **Threaded context** | Passes prior thread messages to the agent for in-context replies |
| **Respond if** | An optional condition that filters when the agent responds, such as "the user is asking a technical question." Leave blank to respond to all messages. |
| **Additional instructions** | Channel-specific instructions appended to the agent's system prompt, useful for adjusting tone or scope per channel |
If you leave **Respond if** blank, the agent replies to every message in the channel. That's right for a dedicated support bot, but too noisy for a general channel like #general. Use a condition to keep the agent focused.
Scout can only read messages posted *after* it's added to a channel. It won't have access to earlier history. If you need context from past discussions, copy the relevant content into your agent's instructions or a connected knowledge source.
Scout can only be deployed to **public channels**. Private channels are not supported due to Microsoft's permissions model for Teams bots.
## Teams as a Deployment Channel
Some of the most useful Teams setups run on a schedule. Instead of posting only when someone asks, the agent delivers something useful every day on its own.
A few examples of what this looks like in practice:
**Daily pipeline brief.** An agent connected to Salesforce runs each morning, pulls open deals with no activity in the last seven days, and posts a summary to #sales-leadership before standup. The team reviews it instead of pulling a manual report.
**Incident summaries.** An agent monitors #incidents, reads the thread when a new incident is posted, and replies with a structured summary of what's affected, the current status, and the latest update. On-call engineers get context without reading back through a noisy thread.
**Weekly digest.** An agent reads activity across your engineering channels each Friday afternoon, generates a summary of decisions, PRs merged, and open questions, and posts it to #general-engineering before the weekend.
## Instruction Examples
Add channel-specific instructions to your agent so it knows what to post and where:
```markdown theme={null}
For Teams tasks:
1. Post pipeline summaries to #sales-leadership in a bullet list format.
2. Keep posts under 400 words. Use headers for readability.
3. Always mention the data source (e.g., "Source: Salesforce as of [date]").
4. Never post PII or customer contact information to public channels.
5. Use threaded replies rather than new top-level messages when responding in context.
```
## Prompt Examples
These prompts work once Teams is connected and enabled on your agent:
* "Summarize the discussion in #engineering and post the key points to #general."
* "Find messages about the API outage yesterday and create a timeline."
* "Post a weekly digest to #general-engineering based on activity this week."
* "Read the thread in #support about the login issue and propose solutions."
* "Post today's pipeline summary to #sales-leadership using Salesforce data."
## Testing Your Integration
Go to one of your configured channels in Teams, mention the agent or send a message that matches your **Respond if** condition, and verify it replies in the thread.
## Next Steps
Feed Salesforce data into your Teams pipeline summaries.
Post email summaries and follow-up drafts to Teams automatically.
Summarize documents from Drive and post results to channels.
See the full integration stack and recommended connection order.