Share via

Permissions Segmentation in SharePoint

Jorziño Barradas 80 Reputation points
2026-05-28T19:35:06.2166667+00:00

Hi,

I am organizing the permissions in a SharePoint site.
My concern is the new features of Copilot Search and Agents where users can use to query documents or contents of a document in a SharePoint site.

Therefore, I wanted to check if users who doesn't have permission and access to the SharePoint site can create or use Copilot Agents that do have permission to the SharePoint site to access files and the data?

Further, I am planning to add permissions only to specific people by organizing permissions based on Members, Folders level, labels/metadata level.

I also want to check if this would be sufficient to keep the site safe from Copilot etc.

Any help will be much appreciated, thanks!

Microsoft 365 and Office | SharePoint | Development
0 comments

Answer accepted by question author

Ian-Ng 13,435 Reputation points Microsoft External Staff Moderator
2026-05-28T20:44:32.63+00:00

Hi @Jorziño Barradas, 

After reviewing the official article, I would like to share that users cannot use SharePoint agents or Copilot to bypass SharePoint permissions. SharePoint agents respond based on the requesting user’s own permissions to the underlying SharePoint data, and if a user does not have permission to the site, library, folder, or file, that restricted content should not be included in the agent’s response.

User's image

It is also important to distinguish between access to the agent and access to the content behind the agent. The .agent file controls who can access or edit the agent itself, but the user’s permissions to the referenced SharePoint sources still determine what information can actually be returned in chat. In other words, sharing an agent does not automatically grant access to all of its source content. 

So, in the scenario you described, if a user does not have permission to the SharePoint site or the underlying files, they should not be able to use an agent to retrieve that content.  

 

For your second concern, using site membership, folder or file permissions, and sensitivity labels / DLP is the valid direction. However, whether the site is fully protected also depends on the overall sharing model, because Copilot and agents respect the permissions and sharing settings that already exist. If content is already overshared, Copilot can also surface that content to users who already have access.  

In practice, site or group membership remains the main security boundary, folder and file permissions are valid controls, and sensitivity labels with Microsoft Purview DLP can help prevent selected files from being used in agent responses. For more sensitive scenarios, it may also be worth reviewing Restricted Access Control (RAC) and Restricted Content Discovery (RCD) as additional governance controls. 

 

Additionally, if you want more tenant-specific best-practice guidance for your environment, I would also suggest opening a support ticket from the Microsoft 365 admin center and routing it to the SharePoint support team, as they can review your scenario more closely and provide more tailored guidance for your permissions design and Copilot concerns. 

I hope the information above helps clarify your concerns. If you need any further assistance, please feel free to reply.

Wishing you a good day ahead.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-28T19:35:21.7+00:00

    Users cannot use Copilot (including SharePoint agents) to bypass SharePoint permissions.

    1. Can users without site access use agents to see that site’s content?
    • Agents in SharePoint use the same security trimming as the rest of Microsoft 365 Copilot.
    • When using an agent, a user only has access to:
      • Sites, pages, and documents that are included in the agent’s sources and
      • To which that user already has permissions.
    • If a user does not have permission to specific content, then even if that content is included in the agent’s sources, it will not appear in the agent’s responses for that user.

    This applies both to:

    • Ready‑made agents that come with every site and library, and
    • Custom agents created on a site.
    1. Can users without Copilot licenses still use agents?
    • Users can use agents if they:
      • Have a Microsoft 365 Copilot license, or
      • Are covered by a pay‑as‑you‑go billing policy that has been set up and assigned to a security group.
    • Only users in the security group assigned to the billing policy have access to agents when using pay‑as‑you‑go.
    1. Controlling who can access specific agents
    • Agents in SharePoint are stored as .agent files.
    • Permissions on the .agent file govern who can access or edit that agent.
    • Only users who can create or access files on the site can create or access agents on that site.
    1. Controlling what information users can access through agents Standard SharePoint controls continue to be the main protection:
    • Site‑level access:
      • For group‑connected team sites, set the site as private and control Microsoft 365 Group membership.
      • For non‑group‑connected sites, use site permissions.
    • Additional governance:
      • Use access governance policies in the SharePoint admin center and PowerShell.
    • With SharePoint Advanced Management (optional):
      • A SharePoint admin can configure a restricted access control policy on a site. Content from that site is then visible in Microsoft 365 Copilot only to the restricted group of users.
    1. Controlling where agents are available
    • Site owners can choose which agents are “approved” for a site so they surface in the picker.
    • SharePoint admins can:
      • Turn off all agent‑related features on specific sites by enabling restricted content discovery. This hides the Copilot icon on that site and prevents:
        • Using the ready‑made agent on that site,
        • Creating new agents on that site,
        • Adding that site’s content as a source to other agents.
      • This does not change site access; it only prevents the site’s content from being surfaced in Microsoft 365 Copilot or organization‑wide search.
    • Tenant/AI admins can also block specific agents from being used in Copilot Chat via the Copilot Control System in the Microsoft 365 admin center (this currently affects Copilot Chat, not SharePoint/OneDrive/Teams directly).
    1. Is organizing permissions by members, folders, labels/metadata sufficient?
    • Copilot surfaces only what users can already access in SharePoint.
    • Therefore, the site remains “safe from Copilot” to the extent that:
      • Site, library, folder, and item‑level permissions are correctly configured (least privilege), and
      • Oversharing (e.g., broad “Everyone” links) is avoided.
    • Recommended governance practices include:
      • Carefully governing access and sharing to prevent oversharing.
      • Applying least‑privilege principles and ensuring each site has valid owners.
      • Using SharePoint Advanced Management to audit overshared sites and apply link expiration.
      • Honoring sensitivity labels and encryption so that Copilot respects classification and protection.

    In summary, Copilot and SharePoint agents cannot grant access to content that users do not already have. Properly configured SharePoint permissions (site, library, folder, and item level), combined with good governance and optional advanced controls (restricted access control, restricted content discovery, sensitivity labels), are sufficient mechanisms to keep the site’s content protected from being exposed via Copilot.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.