> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/connections/microsoft-teams.md).

# Microsoft Teams

Understand the current boundary between Microsoft Teams conversational Agent access and the not-yet-self-serve Teams Workflow Connection.

The **Microsoft Teams Connection** under Connections and the **Lleverage Agent in Teams** under Channels are different product paths.

The current **Microsoft Teams Connection tile in Control → Connections is marked Coming soon** and is not a self-serve setup path. Do not use this page as instructions for configuring a new Teams Workflow trigger today. If you need Teams events or actions inside a Workflow, confirm current availability with the Lleverage team.

If you want people to talk to the Lleverage Agent from Teams, that is a current Channels capability. See [Set up Microsoft Teams](/administer-and-govern/control/channels/set-up-microsoft-teams.md) under **Control → Channels**.

## Connection authority

When a Teams Workflow Connection becomes available for your setup, the Microsoft identity behind it will still need access to the relevant Teams resources. Lleverage does not grant Teams membership or Microsoft permissions.

Keep this separate from the organisation-level Teams app installation used for Agent conversations. Installing the Llev app in a tenant does not create a Workflow Connection.

## Which Teams path is current?

Use **Channels → Microsoft Teams** when operators should give the Agent flexible work in Teams and continue the conversation there.

Treat **Connections → Microsoft Teams** as unavailable for new self-serve Workflow setup while the catalogue tile remains marked Coming soon.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lleverage.ai/administer-and-govern/control/connections/microsoft-teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.