Hi @NT-15101604-0
"This agent is not open to the entire org yet but only has 'viewer' access to a security group." VS "You can't share this app as it's not available right now"
The two statements above brings down us in one point - the agent is ready for the Team but Team don't have any clue!
On @Valantis suggested video, if the tip ("Microsoft team admin center --> Upload custom apps swithed on.") doesn't work, we need to drill one bit down: Let's go deeper:
Viewer Access in Copilot Studio vs. Teams App Availability: "Viewer" access in Copilot Studio means users in that security group can interact with the agent if they can access it. However, for Teams, the agent must be published as a Teams app and made available to those users via Teams app catalog or app permission policies. If the app is not published, approved, or assigned properly, users won’t see or be able to share it in Teams.
App Not Published or Approved in Teams: The Teams app package for the agent might be in a draft state, not yet approved by Teams admins, or not assigned to the security group or users. Until this happens, Teams will block sharing or usage.
Teams App Permission Policies: Even if the agent is shared in Copilot Studio, Teams admins can restrict app availability via permission policies. If the app is blocked or not allowed for the group, the sharing will fail.
Propagation Delay or Cache: By this time we know it but as a quick reminder - sometimes, after publishing or assigning the app, it takes time to propagate across Teams services. During this period, sharing may be temporarily disabled.
I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!
