Power Platform Community Forum Thread Details

I’ve created and published an agent in Copilot Studio and shared it for internal use, however other team members are unable to see or use the agent in Microsoft 365 Copilot.

What I’ve done:

Created the agent in Copilot Studio

Published the agent successfully

Shared the agent internally using Share (Viewer permission)

Enabled channels:
- Microsoft Teams (agent appears and functions for me)
- Microsoft Copilot

Enabled Availability options → Show to my teammates

Confirmed the agent appears in my own M365 Copilot

Confirmed teammates are in the same tenant

Confirmed teammates do have Microsoft 365 Copilot licenses

Republished the agent after changes

Issue:

Other users cannot see the agent in M365 Copilot (Custom copilots / Organization copilots)

I can share the link from M365 Copilot but when they click to view the agent they get an error

No errors are shown during publishing or sharing

Question:

Are there known tenant‑level, environment, or policy‑based restrictions that can prevent Copilot Studio agents from appearing in M365 Copilot for other licensed users?

Is there an additional approval, admin setting, or propagation dependency beyond Share + Microsoft Copilot channel availability?

Categories:

Publish & channel management

Yes, there are several tenant-level, environment, and policy-based factors that can prevent Copilot Studio agents from appearing in Microsoft 365 Copilot for other users, even if you have shared and published the agent correctly. Here’s what you should check:

1. Environment Restrictions
Agents published in Copilot Studio are environment-specific. If your teammates are not in the same Power Platform environment, they may not see the agent.
Confirm both you and your teammates are accessing the agent from the same environment (e.g., “Default” or a specific named environment).
2. Data Loss Prevention (DLP) and Security Policies
Tenant admins can set DLP or security policies that restrict agent visibility or usage, especially for custom or organization copilots.
Check with your Power Platform or M365 admin if there are DLP policies or security groups limiting access.
3. Admin Approval and Publishing
Some tenants require an admin to approve custom copilots before they appear in M365 Copilot for others.
There may be an “admin review” or “publish to organization” step in the Power Platform Admin Center or M365 Copilot admin settings.
4. Propagation Delay
It can take several hours (sometimes up to 24 hours) for new agents or changes to propagate across Microsoft 365 services.
If you just published or changed settings, wait and try again later.
5. Channel and Permission Settings
“Viewer” permission allows users to see and use the agent, but not edit. Double-check that the sharing is with the correct users or groups.
Ensure the Microsoft Copilot channel is enabled and not just Microsoft Teams.
6. License and Service Plan
Users need the correct Microsoft 365 Copilot license, but also must have access to the Power Platform service plan (sometimes restricted by admins).