Building and customizing solutions using Microsoft 365 Copilot APIs and tools
The most likely cause is the Allowed agent types setting.
For Agent Builder agents, users can install agents that are available in the Agent Store based on tenant admin policies, and admins can govern those agents in the Microsoft 365 admin center. The Allowed agent types setting controls which types of agents users can view and install from the agent catalog. One of those options is Allow apps and agents built by your organization, which enables users to install custom agents developed within the tenant.
With Allowed agent types = None selected, custom agents built in the tenant are effectively not installable for users. That matches the error shown when the recipient opens the shared link: the agent is shared, but installation is blocked by org policy.
The Sharing = No users setting does not block the scenario described. That setting disables org-level broad sharing, but users can still share directly with specific individuals. So the sharing action itself can succeed while installation still fails because install/governance policy blocks the agent type.
Why Copilot Studio agents can still work for the same user:
- The sharing control in the Microsoft 365 admin center explicitly says it applies only to agents built with Microsoft Copilot Agent Builder.
- Copilot Studio publishing and sharing follow a different path.
Recommended checks:
- In Microsoft 365 admin center > Agents > Agent settings, enable Allow apps and agents built by your organization under Allowed agent types.
- Keep User access scoped to the specific users/groups as needed.
- Keep Sharing as No users if only direct person/group sharing is desired; that setting still allows direct sharing to individuals.
- Retest with the same shared link.
If the agent is intended to be discoverable more broadly, org-wide sharing can make it visible in the Agent Store, but that is separate from the install block caused by agent-type policy.
References: