Applies to: Microsoft Copilot (formerly the Microsoft 365 Copilot app), Agent Builder, Microsoft 365 admin center
So many agents had been shared with me that I couldn’t find the one built for a specific team. Each came with a link. Most I opened once and never again. When I needed the team’s agent, I had to scroll, guess at names, and dig for the old link.
So I went looking for a fix.
If you build agents for teams, your staff are in the same spot. You shared the agent. You sent the link. A week later, someone asks where it went.
The real cause: share, deploy and pin are three different things
Most people stop at “share.” In Microsoft Copilot, sharing is the first of three separate steps, and each one does a different job:
| Step | Who does it | What it does |
|---|---|---|
| Share | The agent’s owner | Gives people permission to chat with the agent. |
| Deploy | An admin | Installs the agent for a group, so it’s there without a link. |
| Pin | An admin (or each user) | Keeps the agent at the top of the Agents list. |
Sharing on its own does nothing to the list people see. Here’s what the Agents list looks like in Copilot:
Copilot > Agents
Four test agents, listed in the order they were last touched. Nothing here groups them by team, and More agents is where the rest end up.
The list is short and sorted by what you used lately. Microsoft’s own help page for SharePoint agents says you can’t browse every available agent from it. You only see the ones you’ve used recently.
A better name or a second email with the link helps a little. What actually puts the agent in front of the team is deploying and pinning it for their group.
For this post I built four small agents in Agent Builder, in the test tenant. One of them, Sales Proposal Drafter, plays the team agent. The steps below take it from shared to pinned for the Sales and Marketing group.
Step 1: Share it with the team’s group
In Copilot, select Agents, then More agents. Point at the agent, select More options (the three dots), then Share. Type the team’s group name, not each person’s name.
Agent > Share > Add people
Groups always get Can chat. Leave Send notification ticked so people get an email with the link.
- Groups only get Can chat. The dialog says so. To give someone edit rights, add them by name.
- Leave Send notification on. Per Microsoft, it emails the new users so they know they have access.
Skip the Org-wide sharing for chat access toggle for a team agent. It puts the agent in the Agent Store for everyone in the tenant. That’s one more agent in everyone’s way, and the wrong people will find it.
Why sharing isn’t enough
I went to the admin center next to pin it. Under Agents > All agents, I opened the agent and went to the Users tab. This is what it said:
Admin center > Agents > All agents > agent > Users
The admin can see a shared agent, but can't install it for anyone. Only the owner controls who it's shared with.
Shared agents can’t be automatically installed. And the pin picker only lists agents that are deployed. A shared agent isn’t, so you can’t pin it. You need the next step first.
Step 2: Submit it to your org catalog
Back in the same More options menu, select Edit. That opens the agent in Agent Builder. Select More (the three dots at the top), then Submit to org catalog.
Agent Builder > More > Submit to org catalog
Microsoft spells out the split here. Submitting is what lets an admin choose who gets the agent and pre-install it.
Select Continue. The next form asks for a Short description, a Display name, and three web links (creator website, privacy statement and terms of use). The links come filled with Microsoft examples. Replace them with your own pages.
Use the short description to name the team. I wrote “Sales team only: drafts sales proposal outlines.” It’s limited to 80 characters, so put the team first. Microsoft shows it in the Agent Store and in the agent’s About information.
Submit it. The agent shows as Waiting for approval.
If you build in Copilot Studio instead, the idea is the same. Microsoft’s registry page says an agent you submit for admin approval, and an admin then publishes, becomes a Published by your org entry. That’s the kind you can deploy and pin.
Step 3: Publish it to the team’s group, with pre-install on
Now switch to the admin side. In the Microsoft 365 admin center, go to Agents > All agents and open the Requests tab. Your agent is listed as Pending review. Select it, then Publish to store.
The first page of the wizard has two questions. Answer both with the team’s group.
Admin center > Agents > Requests > Publish to store
The ringed half is the one that matters. Pre-installing is what puts the agent in front of the team without a link.
- Select users or groups who can install the agent: choose Specific users/groups and add the group.
- Select users or groups who will have the agent pre-installed: choose Specific users/groups again, and add the same group.
The second question is marked optional, but it’s the one you need. Without it, the agent sits in the store and waits for people to go find it, which is the problem you started with.
Select Next through Security policy and Accept permissions. On Review and finish, check that it says “Deploy the agent to” your group, then select Publish.
Step 4: Pin it for that group
Still under Agents > All agents, select More actions (the three dots on the right of the command bar), then Manage pinned agents. Select Pin new agent.
The picker says it at the top: “You can only pin agents that have been deployed to some or all users.” Your agent is now in the list, with Some users under Installed for. Select it and select Next.
Choose Specific users or groups the agent is deployed to, add the group, and select Save.
Admin center > All agents > Manage pinned agents
The pin is saved for one group. Microsoft's own pins are listed separately and shown in addition to yours.
Read the line at the top of that panel before you pin more. Users see up to 3 agents your org pins. If someone has more than 3, they won’t see the ones lower in the list. You can move pins up and down to set the order.
Then give it time. Microsoft says it can take up to six hours before people see the pin. Staff can’t unpin an agent you pinned for them.
Step 5: Show staff how to find the rest
Three pin slots won’t cover every agent. For the others, staff need one habit.
In Copilot, select Agents, then More agents. That opens the Agent Store. It has a Search for an agent box at the top. Every agent also has a Pin button that shows when you point at it.
Copilot > Agents > More agents
Search finds an agent by name. The pin keeps it at the top of that person's Agents list.
Those pins belong to each person, and they can remove them anytime. Tell staff to pin the two or three agents they use every week. And name agents so search works: team first, then the job. “Sales Proposal Drafter” is easy to find. “Proposal Helper v2” isn’t.
What this does not fix
Deploying and pinning makes the right agent easy to find. A few gaps stay open.
- Three slots is the hard limit. If every team wants a pin, you’ll have to pick. Pin for groups, not for all users, so each team gets its own slots.
- It doesn’t clean up old shared agents. Every agent someone shared with you stays shared until the owner removes it. Nothing here hides it.
- The registry can show the same agent twice. Microsoft says a submitted agent can appear once as Shared by creator and once as Published by your org. Removing one doesn’t remove the other.
- It doesn’t grant access to the agent’s files. The agent only answers with content each person can already open. If the team can’t open the SharePoint site behind it, the agent can’t use it for them.
- It doesn’t fix licensing. If the agent uses features that need a Microsoft 365 Copilot licence, people without one may get errors. This post on SharePoint agents without Copilot licences covers that side.
The bottom line
Sharing an agent gives people access and nothing more. For an agent one team needs, share it with the team’s group. Then submit it to the org catalog, publish it to that group with pre-install on, and pin it for them. Give it six hours, then ask someone on the team if it’s at the top of their list.
If you’d like help sorting which agents deserve the three pin slots, that’s a focused job for an hour bank.