regarding copilot studio agent sharing

These are security warnings rather than sharing errors: before publishing, restrict the audience if organization-wide access is unnecessary and change the four listed tools from Maker-provided credentials to End-user credentials unless using the author’s identity is intentional.

What each message means

1. “Your agent is shared with all users in the organization”
   • Everyone in organization currently has End user access.
   • Any eligible user in the organization can chat with the agent and potentially access content exposed through its knowledge sources and tools.
   • Copilot Studio displays this warning whenever an agent is shared organization-wide because that changes the secure default of sharing with nobody.^1^
   Action: If that audience is too broad, remove Everyone in organization and share only with the required individual users or security groups. If everyone genuinely needs the agent, the warning can remain after permissions and data access have been reviewed.^2^
2. “Your agent runs tools that use the author’s credentials”
   • The four tools shown by View 4 tools are configured with Maker-provided credentials.
   • Shared users might therefore run those tools with the original author’s access, potentially retrieving information or performing tasks that the users could not perform under their own identities.
   • Copilot Studio intentionally warns whenever maker-provided credentials replace the default end-user credentials.^1^
   Recommended action:
   1. Select View 4 tools.
   2. Open each listed connector or flow.
   3. Locate Credentials to use in the tool’s configuration.
   4. Select End-user credentials.
   5. Save, test as a normal user, and republish.
   With end-user credentials, users are prompted to authenticate when required, and each operation runs with that user’s permissions. If the user lacks access to the underlying service or resource, the operation fails by design.^3^ Keep Maker-provided credentials only when the agent is deliberately designed to use a controlled shared identity and its permissions expose no more data or actions than every shared user should have. If that option is unavailable, an environment or environment-group governance policy might be enforcing end-user credentials; an administrator must review Power Platform admin center → Manage → Environments/Environment groups → Settings → Product → Features → Copilot Studio agents → Control maker credential options.^3^
3. Power Platform connector knowledge-source notice
   • Every shared user needs an appropriate Dataverse security role, such as Basic User, in the agent’s Power Platform environment.
   • Connector-based knowledge also performs live authorization checks against the source. Users without permission to the relevant content receive no results rather than inheriting the maker’s content permissions.^4^
   Ask the Power Platform administrator to assign the required role only to intended users, then test the agent using a non-owner account.
4. Teams and Microsoft 365 Copilot notice
   • Sharing the Copilot Studio agent does not override Teams app-access policies.
   • Ensure the intended users belong to security groups allowed to access the agent in Teams.
   • Also verify that users have the required Copilot Studio license. The standard sharing documentation states that shared users need a Copilot Studio per-user license.^2^

After those checks, publish and test with an ordinary end-user account—not the owner account—to verify the effective knowledge, connector, and tool permissions.

References

1. Automatic security scan in Copilot Studio
2. Share agents with other users
3. Control maker-provided credentials for authentication
4. Unstructured data as a knowledge source