Shared Copilot Agent That Colleagues Cannot Add: An Admin Settings Checklist
By Mirko Peters ·
You built a Copilot agent and sent it to colleagues, but they see an error that blocks installing it. Check the share dialog, the admin center agent settings, licenses and ownership in this order.
A colleague builds an agent in Microsoft 365 Copilot, shares it, and the people it was meant for cannot add it. They see a message such as "Your organization has prevented this agent from being installed" or "You don't have permissions to add this agent. Please contact your IT admin for help".
Key points
- Sending a link is not the same as sharing: in one 2026 thread the whole problem was an agent that was never shared.
- Three separate admin settings decide what happens: who may share agents, which agent types are allowed, and who may use agents at all.
- Agent Builder sharing and Copilot Studio sharing are different mechanisms with different roles and different documentation.
- Org-wide sharing that is not honored, while direct sharing works, was reported but has no confirmed fix.
Three Microsoft Q&A threads from April to August 2026 show different versions of this. In one, the maker had only sent a link. In another, an agent was visible under "Built by your org" but users could add it only after being named as a viewer. In a third, an admin handed an agent to a new owner, who could not find it. This article puts the checks in a sensible order. It is not an official Microsoft procedure. Menu names in the Microsoft 365 admin center change often, so compare each step with the current Learn page.
Which kind of agent is it?
The checks differ:
- Agent Builder agents are made inside Microsoft 365 Copilot. They are shared from the share dialog, and sharing is controlled by an admin setting.
- Copilot Studio agents are shared from Copilot Studio and may be published to the Microsoft 365 Copilot channel.
Microsoft Learn says the admin sharing setting applies only to agents built with Agent Builder. The Learn page on agent settings does not say how this setting relates to Copilot Studio sharing. Keep that gap in mind.
Step 1: Check that the agent is actually shared
The thread with a confirmed resolution is the simplest one. The asker came back and wrote that they had sent a link to colleagues but never shared the agent.
For Agent Builder, the Learn page describes the share dialog as follows:
- Add people, groups or email addresses and pick a role. Can chat lets people use the agent. Can edit makes them an owner. Groups can only get Can chat.
- Turn on Org-wide sharing for chat access to let everyone in the tenant find the agent in the Agent Store and chat with it.
- The dialog also offers copy links. Learn does not say whether a link alone gives access to someone who was not shared with. Do not assume it does.
Test: share the agent with one named colleague, ask them to look for it, and then widen the sharing.
Step 2: Check the admin sharing rule
In the Microsoft 365 admin center, go to Agents, then Settings, and open the sharing setting.
| Setting | Effect according to Learn | |---|---| | All users | Everyone can share with the organization. This is the default. | | Specific users or groups | Broad sharing is limited to those people. | | No users | Org-wide sharing is off. Users can still share directly with named people. The toggle in the share dialog is grayed out. |
Learn adds that changes apply to new sharing actions only. An agent that was already shared keeps the access it had until someone changes it.
Step 3: Check which agent types are allowed
Learn describes a section for agent and plugin access with separate switches for agents built by Microsoft, by your organization, and by external publishers. If a type is off, its agents do not show in the Agent Store.
In the August 2026 thread about the install block, an independent advisor named a page called "Allowed agent types". The current Learn page calls the same area agent and plugin access, so the label has changed or the thread used an older name. Look for the switch for agents built by your organization.
Step 4: Check user access
The user access setting is also under Agents, Settings. Learn lists three options:
- All users is the default.
- No users means nobody in the organization can access agents and plugins.
- Specific users or groups limits use to those people. Learn says that some users may have permission to install and use agents from the Agent Registry list, but only the users or groups you select can use agents and plugins.
The last option may fit the picture in the "visible but cannot add" thread. An AI-generated answer in that thread pointed to it. The asker did not confirm that this was the cause, so treat it as a candidate to rule out, not as the answer.
Step 5: Check the agent's status and requests
The same advisor suggested two more places in the admin center: the list of all agents, to see whether the agent is blocked, and the requests page, in case an admin approval is waiting. Learn says that agents published by an organization need approval before users can use them, and that admins manage agents and requests in the agent registry. The Learn page does not give exact menu paths for blocking, unblocking or approving. The paths in the thread are reported by an advisor, so verify them in your own admin center.
Step 6: Check licenses
Learn states that what an agent can do depends on the user's Microsoft 365 Copilot license, and that users without the required license may get an error. Copilot Studio sharing has its own rule on the Learn page. It says you can share only with users who have a Copilot Studio per-user license, and unlicensed users can sign up for a trial. Compare this with your agent type before you blame a setting.
Step 7: If an admin changed the owner
In the April 2026 thread, an admin changed the owner of an Agent Builder agent in the admin center. The new owner could not find it in the Agents area of the Copilot Chat page. The asker then wrote that it did not show under the Agents section of the Copilot Chat page and that they found it by choosing New agent and then Agent Builder. No ownership or permission change was needed to make it appear.
Learn confirms that admins can reassign ownership of shared agents, but it does not say where the new owner finds the agent. Treat the thread result as reported.
Step 8: Copilot Studio agent shown to everyone but not installable
One August 2026 thread reported a Copilot Studio agent that was published with the option to show it to everyone in the organization, listed under "Built by your org", and still not addable by licensed users. When the asker added a user as a viewer, that user could add and use the agent. Removing the viewer entry brought the error back. Republishing did not change this.
An AI-generated answer, which the asker accepted, pointed to the admin center settings above and suggested direct assignment as a workaround. The asker's own comments said that organization-wide permission looked like it was not being honored. No Microsoft staff reply and no confirmed root cause appear on the page.
What you can do today:
- Run through steps 2 to 4 and 6 above.
- Share with a security group instead of relying on the organization option. Learn says a Copilot Studio agent can be shared with security groups, and that sharing needs user authentication set to manual with Microsoft Entra ID and the setting that requires sign-in. Microsoft 365 groups that are not security enabled cannot be used for chat sharing.
- If a group does not help, note the time, the agent name, the user and the exact message, and open a support case.
Verification
After each change:
- Ask a test user with a Copilot license to sign out and back in, then look for the agent in the Agent Store.
- Try to add it.
- Start a chat and ask a question that needs the agent's knowledge.
Learn does not say how long admin center changes take to apply. In an unresolved August 2026 thread about a Copilot Studio agent deployed through a pipeline, the agent was still missing after more than eight hours and appeared only after the user signed out of the Copilot app and back in. That is one report, not a documented rule, but it is a reason to allow time and test with a fresh session before you undo a setting.
Limits of this checklist
- Only the "link was not shared" case has a confirmed solution in the threads.
- The org-wide sharing case and the ownership case rest on single threads.
- Admin center labels differ between the threads and the current Learn pages.
Related
Sources
- Microsoft Learn: Agent settings in the Microsoft 365 admin center
- Microsoft Learn: Manage agents in the Microsoft 365 admin center
- Microsoft Learn: Share and manage agents built in Agent Builder
- Microsoft Learn: Share agents with other users in Copilot Studio
- Microsoft Q&A: Copilot created agent, your organization has prevented this agent from being installed (August 2026)
- Microsoft Q&A: Users can see Copilot agent in Built by your org but cannot add it (August 2026)
- Microsoft Q&A: Created an agent on Copilot Chat and assigned a new owner, the new owner doesn't see it (April 2026)
- Microsoft Q&A: Intermittent post-deployment issues with Copilot agent using SharePoint knowledge sources (August 2026)