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 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.