Share via

Copilot agent issue

Ashok K 0 Reputation points
2026-03-05T07:19:34.78+00:00

I have created Copilot agent in M365 and shared the agent to my team members of total 7 members and how ever i see that the shared agent is getting disappeared for my team members in the agent store .

What is the root cause and every time i need to reshare the agent again and again and why does this is getting disappeared.

Microsoft Copilot
Microsoft Copilot

An AI companion integrated into Microsoft products that enhances productivity through intelligent assistance, content generation, and task automation.

0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-03-05T07:20:02.02+00:00

    The behavior is most likely caused by how availability and sharing work between:

    • Microsoft 365 Copilot Agent Builder sharing
    • Copilot Studio / Teams “Built with Power Platform” discovery limits
    • Admin governance policies that can change after you share

    Key points from the documented behavior:

    1. Sharing vs. discovery in Teams / Agent Store
      • When an agent is configured to “Show to my teammates and shared users,” it appears in the Built with Power Platform section of the Teams app store only for users it is shared with.
      • This listing is also subject to the Teams app store discovery policy limits for your tenant. If the number of shared users exceeds those limits or the policy changes, the agent may stop appearing for some or all users, even though it is still technically shared.
      • Removing or changing availability options (for example, switching between “Show to my teammates and shared users” and “Show to everyone in my org”) also affects whether the agent appears in the store.
    2. Admin governance changes can invalidate existing sharing
      • Tenant admins can centrally control who can share agents and how broadly (All users, Specific users/groups, or No users).
      • If an admin tightens these settings after the agent has been shared, the agent’s current sharing option can become non‑compliant. In that case, owners see errors like “Can no longer update agent” and must change the sharing setting to a compliant option before further updates.
      • These policy changes apply only to new sharing actions, but they can affect how the agent is surfaced and updated, which can result in it no longer appearing in the store as expected.
    3. Store listing vs. installed agent
      • Removing an agent from Built with Power Platform or disconnecting the Teams/Microsoft 365 Copilot channel does not uninstall it for users who already have it installed; it only removes it from discovery (store / shared link).
      • If the agent is repeatedly disappearing from the store but users can still use it if already installed, the issue is with the availability options / discovery policy, not with the agent itself.
    4. What to check to stop the repeated “reshare” cycle
      1. In Copilot Studio, open the agent → ChannelsTeams and Microsoft 365 CopilotAvailability options and confirm:
        • Show to my teammates and shared users is selected, and
        • Show in Built By Your Colleagues is checked if you want it in Built with Power Platform.
      2. Confirm that the total number of shared users is within the limits of your tenant’s Teams app store discovery policy. If you are close to or over the limit, work with your admin to either:
        • Reduce direct sharing and instead
        • Submit the agent for admin approval using Show to everyone in my org so it appears in Built for your org / Built by your org instead of relying on the “Built with Power Platform” section.
      3. Ask your Microsoft 365 / Teams admin to verify:
        • Agent‑sharing governance settings in the Microsoft 365 admin center (they may have recently changed from “All users” to “Specific users or groups” or similar).
        • Teams app setup and discovery policies that might hide or limit “Built with Power Platform” apps.

    If the agent is correctly configured and within discovery limits, but still disappears intermittently, capture the time and affected users and open a support ticket, as the documentation also notes that internal service errors (“Something went wrong”) can affect sharing and may require support intervention.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.