How to Publish a Copilot Studio Agent to a Microsoft Teams Channel
🔍 WiseChecker

How to Publish a Copilot Studio Agent to a Microsoft Teams Channel

You built a custom agent in Copilot Studio and now need to share it with your team inside Microsoft Teams. Without publishing to a specific channel, the agent remains private or only accessible via a direct link. This article explains how to publish your agent to a Teams channel so members can interact with it directly from the chat area. You will learn the prerequisites, the step-by-step publication process, and how to handle common errors during deployment.

Key Takeaways: Publishing a Copilot Studio Agent to Teams Channel

  • Copilot Studio > Agents > Publish > Channels > Microsoft Teams: Grants the agent access to a specific Teams channel.
  • Teams admin center > Teams apps > Setup policies > Allow third-party apps: Required to enable custom agents in your tenant.
  • Teams channel > Apps > Add a tab > Copilot Studio agent: Lets channel members install the agent from the channel itself.

ADVERTISEMENT

What Publishing a Copilot Studio Agent to Teams Involves

Publishing an agent to a Microsoft Teams channel makes the agent available as a bot that members can message directly within that channel. The agent can respond to questions, trigger flows, and access data sources you configured in Copilot Studio. Before you can publish, you must complete several prerequisites. Your Microsoft 365 tenant must have Copilot Studio licenses assigned to the users who will interact with the agent. You also need the Teams admin permissions to allow custom apps in the tenant. If your organization blocks third-party or custom apps, the agent will not appear in the channel even after publishing.

The publication process involves three main stages. First, you configure the agent in Copilot Studio and publish it to the Microsoft Teams channel. Second, you add the agent as a tab in the target Teams channel. Third, you verify that channel members can see and use the agent. Each stage has specific settings that must be correct for the agent to function.

Steps to Publish Your Agent to a Teams Channel

  1. Open your agent in Copilot Studio
    Sign in to Copilot Studio at copilotstudio.microsoft.com. Select Agents from the left navigation. Click the agent you want to publish. If you have not created an agent yet, you must build one first using the Create button and selecting New agent.
  2. Navigate to the Publish section
    In the agent editor, select Publish from the top menu bar. Then choose Channels from the left pane. This page lists all available channels where you can deploy the agent.
  3. Enable the Microsoft Teams channel
    Find Microsoft Teams in the channel list. Toggle the switch to On. A configuration panel opens. Enter a Bot name that appears in Teams. Optionally, upload an Icon image for the agent. Click Save to apply the channel settings.
  4. Publish the agent to the channel
    Return to the Publish tab. Click the Publish button in the top bar. A confirmation dialog appears. Review the changes and click Publish again. Copilot Studio packages the agent and makes it available to Teams.
  5. Go to the target Teams channel
    Open Microsoft Teams. Navigate to the team and channel where you want the agent to appear. For example, if you want the agent in the General channel of the Sales team, open that channel.
  6. Add the agent as a tab in the channel
    In the channel, select the + (Add a tab) button at the top of the channel tab bar. In the Add a tab dialog, search for Copilot Studio agent or scroll to find it. Click the tile. A new dialog opens asking you to select the agent. Choose the agent you published. Click Save. The agent tab appears in the channel.
  7. Verify the agent works
    In the channel, type @agentname followed by a question. The agent should reply within the channel conversation. If the agent does not respond, check the Copilot Studio > Analytics > Sessions page for error logs.

ADVERTISEMENT

If the Agent Does Not Appear or Respond in Teams

The agent tab is missing from the Add a tab dialog

This usually happens when the Teams admin has disabled custom apps. Contact your Teams administrator and ask them to enable Allow custom apps in the Teams admin center > Teams apps > Setup policies. Also verify that the Microsoft Teams channel is enabled in Copilot Studio for your agent.

The agent replies with an error message in the channel

Errors often come from missing data source permissions. In Copilot Studio, go to Settings > Generative AI. Ensure the data sources you configured are accessible to the agent. If the agent uses Microsoft Graph data, confirm that the user who is chatting has the correct SharePoint or OneDrive permissions. You can test the agent in the Test panel in Copilot Studio before publishing.

Channel members cannot see the agent tab

Only team owners and members with the Add apps permission can add tabs. If you added the tab but other members cannot see it, verify that the channel is not set to Private. In private channels, only members of that private channel see the tab. Also confirm that the agent is published to the correct environment. In Copilot Studio, check the Environment selector at the top right and ensure it matches the environment where the Teams channel is configured.

Item Copilot Studio Agent in Teams Channel Copilot Studio Agent as a Personal App
Access location Inside a specific Teams channel In the Teams app drawer or sidebar
Visibility All channel members see the tab Only the installing user sees it
Installation method Add a tab in the channel Apps > Copilot Studio agent > Add
Use case Team-wide support, announcements, Q&A Individual productivity, personal workflows
Admin requirements Custom apps allowed in tenant Custom apps allowed in tenant

You can now publish a Copilot Studio agent to a Microsoft Teams channel and make it available to your entire team. After publication, test the agent by mentioning it in the channel with a sample question. To improve the agent further, consider adding Power Automate flows in Copilot Studio to trigger actions like creating a ticket or sending an email when the agent receives a specific command.

ADVERTISEMENT