- Getting started
- UiPath Conversational Agents
- UiPath Agents in Studio Web
- UiPath Coded agents
- Build with Coding Agents
Dedicated Microsoft Teams App
Deploy a chat agent as a dedicated Microsoft Teams app to give users a persistent, context-aware channel separate from the shared Autopilot app.
A dedicated Microsoft Teams App gives each chat-based conversational agent its own channel in Teams, providing a context-aware experience separate from the shared UiPath Autopilot Teams App.
Using a dedicated Teams App offers the following advantages:
- Persistent context — Each agent maintains its own chat history. Switching between agents no longer resets your conversation.
- Reduced friction — Access your agents directly from the Teams sidebar without using the Switch Agent command.
- Concurrent conversations — Run multiple agents simultaneously without overlap or confusion.
Prerequisites
- The conversational agent must be published and deployed to Orchestrator.
- You must have permission to upload custom apps in Microsoft Teams.
Create a dedicated Teams App
Create and deploy a dedicated Teams App for a specific conversational agent.
-
Go to Agents > Instance Management and open your conversational agent's management page.
-
Select the Channels tab.
-
Select Create a Teams App and configure the following options:
- Logo — Optional. Add a logo that meets the Teams app icon guidelines.
Note:The app name is set automatically from your agent name. Teams app names cannot exceed 42 characters, so longer agent names are automatically truncated.
Note:UiPath provisions an Azure Bot resource in the background. Provisioning takes approximately 3–5 minutes.
-
When provisioning is complete, select Download to save the Teams manifest ZIP file.
-
Upload the manifest to your Microsoft Teams environment. For instructions, see Upload an app in Microsoft Teams.
The dedicated Teams App is available in Microsoft Teams. Users can access the agent directly from the Teams sidebar.
Use the agent in a channel
As well as one-on-one chats, you can add a dedicated Teams App to a channel and bring the agent into your team's conversations. Anyone in the channel can mention the agent in a thread, and it replies in that same thread.
Channel prerequisites
In a channel, users don't sign in to UiPath. The agent authenticates through a UiPath-managed external client and runs under the identity of an unattended robot account. Before you add the agent to a channel, you need the following:
- External client registration — An organization administrator registers the Conversational Agents external client in your organization. This is a global client that UiPath provides, so you don't create an external application or manage a client secret. You register it once, and it applies to every agent in the organization. To register it, open the agent's Channels tab, select the Teams App, and then select Register external client.
- Unattended robot account — Assign an unattended robot account to the agent's Orchestrator folder. Channel conversations run under this robot's identity. For details, see Orchestrator folder requirements.
- Standard channel — Use a standard channel. Private and shared channels are not supported.
Chat with the agent in a channel
- Add the dedicated Teams App to the team that contains the channel.
- In a channel post or reply, enter
@followed by the agent's name and your question. - Send the message.
The agent replies in the same thread.
To ask a follow-up, mention the agent again in the same thread. The agent takes the recent messages in the thread into account, so you can build on the earlier discussion without repeating yourself. Each thread is its own conversation, so different threads stay independent.
The agent only responds when you mention it and doesn't participate in other parts of the channel discussion.
Channel limitations
- Standard channels only — Mentioning the agent is supported in standard channels, not in private or shared channels.
- Files are not supported — You can't share files with the agent in a channel. To share a file, message the agent in a one-on-one chat instead.