Building custom solutions that extend, automate, and integrate Microsoft 365 apps.
Allow it in the Microsoft 365 admin center agent controls.
Use these checks in order:
- Go to Microsoft 365 admin center → Agents → Settings → User access.
- Set access to All users or Specific users/groups.
- If No users is selected, nobody in the tenant can install or use agents.
- In Microsoft 365 admin center → Agents → Settings → Allowed agent types:
- Enable Allow apps and agents built by your organization for a tenant-created custom agent.
- If this is off, those agents do not appear for users in the Agent Store.
- If the agent was published to the organization, check Agents → All agents.
- Review the agent in inventory.
- Make sure it is not blocked.
- If needed, assign/deploy it to the required users or groups.
- If users requested the agent and it is blocked by policy:
- Go to Agents → All agents → Requests.
- Find the request with state Allow user to install.
- Unblock agent, then Approve the request.
- If the agent was shared from Agent Builder, check org sharing policy.
- In the Microsoft 365 admin center, admins can set sharing to All users, Specific users or groups, or No users.
- If org-wide sharing is disabled, Anyone in your organization is unavailable for new sharing actions.
If the agent is being deployed through Teams as a custom app, the Teams custom app setting can also affect installation. That setting applies to all custom Teams apps and custom agents available in the tenant, not only one Copilot agent. A more targeted approach is per-app assignment to specific users or groups instead of enabling tenant-wide installation.