Don't be confused about Teams app visibility for Copilot Studio

You built an agent in Copilot Studio, published it to Teams, shared it with users… and yet they can’t find it — or it only works in Copilot Chat, not as a standalone Teams app. This usually isn’t an environment problem.

The key thing to know: Teams is tenant-scoped. Copilot Studio is environment-scoped. When you publish an agent to Teams, the Teams app lives at tenant level, not inside your Power Platform environment.

Common misconceptions:

• ❌ “I shared the agent in Copilot Studio — users should see it” → Agent Sharing controls access, not Teams installation
• ❌ “Teams channels belong to environments” → Teams channels are tenant objects

What actually needs to happen: For a user to use the agent in Teams, the Teams app must be installed. That means one of the following:

1. The app is approved and assigned in Microsoft Teams Admin Center.
2. The user installs it via the direct installation link from Publish → Teams in Copilot Studio.

If the app behaves oddly: If it works in Copilot Chat but not as a standalone Teams app:

• Uninstall the app
• Clear Teams cache
• Re-install
• This is a known Teams client issue, especially for users who installed the app early.

Quick checklist:

• Check the app in Teams Admin Center → Manage apps
• Don’t rely only on Agent Sharing
• Use the Teams install link for testing
• Test with users who never installed the app before

Bottom line: Publishing an agent ≠ making it available in Teams. Copilot Studio handles the agent. Teams Admin Center controls visibility and rollout.