I am not able to publish a copilot agent to 365 Copilot/Teams

Alex Hebert 0 Reputation points
2026-04-22T15:03:44.0833333+00:00

I have a risk message "Users with Editor permission will have full access to embedded connections used by Flows or Triggers added to this agent." and when I go to channel to share on 365/teams it says "My organization has prevented this from being added." Where do I go to fix this issue as I can't find any setting on the agent page to fix it

Microsoft Copilot | Microsoft 365 Copilot | Development

1 answer

Sort by: Most helpful
  1. AI answer

    2026-04-22T15:04:04.9933333+00:00

    "My organization has prevented this from being added" and the editor-permissions risk banner are both governed by tenant-level admin controls, not by a setting on the individual agent.

    To resolve this, a Microsoft 365/Teams/Power Platform admin must adjust the relevant policies:

    1. Check Copilot agent access policies (who can use agents)
      In the Microsoft 365 admin center, an admin must review the Copilot agent policies that control who can access agents and which types of agents are allowed:
      • They can choose whether All users, No users, or Specific users/groups can access agents.
      • They can also choose whether apps and agents from your organization, Microsoft, or external publishers are allowed.
        If these settings are too restrictive (for example, set to No users or excluding your organization’s agents), attempts to add or use the agent in Microsoft 365 Copilot/Teams can be blocked.
    2. Verify sharing and publishing controls for agents
      Admins can restrict who is allowed to share agents org-wide and how agents are distributed:
      • In the Microsoft 365 admin center, they can set sharing to All users, Specific users or groups, or No users for org-wide sharing of agents.
      • If org-wide sharing is disabled or limited to specific users/groups that do not include the maker, options like Show to everyone in my org or sharing to broader audiences may be blocked, which can surface as the organization preventing the agent from being added.
    3. Check Power Platform managed environment sharing limits (Editor/Viewer rules)
      If the agent is in a managed environment, the admin may have configured agent sharing rules that restrict how agents can be shared:
      • They can disable granting Editor or Viewer permissions, or limit sharing only to individuals and/or cap the number of viewers.
      • These rules are enforced when users try to share an agent. If the current sharing attempt violates these rules, only unsharing is allowed until the agent is compliant.
        These controls are what underlie the risk message about "Users with Editor permission will have full access to embedded connections" and can also prevent sharing if the admin has tightened sharing rules.
    4. Confirm Teams/Copilot app availability and sideloading
      After publishing an agent for Microsoft 365 Copilot, distribution to Teams and Microsoft 365 Copilot is controlled by availability options and Teams app governance:
      • The agent can be distributed via Share link, Show to my teammates and shared users, Show to everyone in my org, or Download as a .zip for manual upload.
      • If the tenant admin has blocked sideloading or publishing of custom apps, one or more of these options will be unavailable, and attempts to add the agent in Teams/Microsoft 365 Copilot can be blocked with an organization-level message.

    Because all of these controls are tenant-level, the fix is:

    • Contact the Microsoft 365/Teams/Power Platform admin.
    • Ask them to:
      • Review Copilot agent policies (who can access agents and which publishers are allowed).
      • Review agent sharing rules in the Power Platform admin center for the environment hosting the agent (especially Editor/Viewer sharing limits).
      • Ensure Teams app policies and upload/sideload settings allow custom/organizational agents to be added to Teams and Microsoft 365 Copilot.

    Once the admin relaxes or correctly configures these policies, the risk banner will remain informational, but the "My organization has prevented this from being added" block should be removed and the agent can be published/shared to Microsoft 365 Copilot and Teams.


    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.