Someone posts a question in a Teams channel at 4pm on a Friday. The people who know the answer are in meetings or have already signed off. The post sits there over the weekend. On Monday, someone eventually replies - but by then the person asking has already made a decision without the information they needed.

Deploy your agent to Microsoft Teams and that question gets answered immediately, sourced from your actual documentation, regardless of who is online or what time it is. The knowledge your organisation has built stops being locked behind availability and starts being accessible the moment someone needs it.

In this article, you'll learn:

• How the Microsoft Teams deployment works
• How to connect Microsoft Teams from the Deploy tab
• How team members interact with the agent

How It Works

Once connected, your agent is available inside Microsoft Teams. Your agent lives inside Teams as a bot. Team members can message it directly or mention it in a channel to get instant answers - no tab-switching or separate tools required.

This deployment is best suited for internal agents - for example, an HR agent that answers employee questions about policies, an IT agent for troubleshooting, or a general knowledge agent for your team's most common internal questions.

Note: Deploying your agent to Microsoft Teams is different from using Microsoft Teams as a knowledge source. This article covers making your agent available in Microsoft Teams. To use Microsoft Teams conversations as a source of knowledge for your agent, see Connecting Microsoft Teams as a Knowledge Source.

How to Deploy to Microsoft Teams

1. Go to the Deploy tab.
2. Scroll to the Team Chat section.
3. Find the Microsoft Teams card and click Connect.
4. Log in to your Microsoft Teams account when prompted and authorize Outlearn.
5. Follow the on-screen setup steps to complete the connection.

How Team Members Use the Agent

Once deployed, team members can message the agent directly as a bot in Teams, or mention it in a channel. The agent responds inline. No individual setup is required for team members.

Best Practices

• Make sure your agent's knowledge sources are configured for internal content before deploying to Microsoft Teams - internal agents should be drawing from internal sources, not public-facing help articles.
• Set the agent's accessibility to Internal in its Settings to ensure only authenticated team members can interact with it.
• Announce the deployment to your team and show them how to use it - even the best agent goes unused if people don't know it exists.
• Monitor the Conversation & Training tab for the first week to see what your team is asking and identify gaps in your sources.