This guide walks you through configuring Microsoft 365 Copilot permissions and data access with a security-first approach. You’ll learn how to control which users can use Copilot, what data it can reach, and how to prevent oversharing—so your organization benefits from AI assistance without exposing sensitive information.
What You’ll Need
- Microsoft 365 admin account with Global Admin or SharePoint Admin role (or equivalent).
- Microsoft 365 E3 or E5 subscription (Copilot requires a qualifying plan).
- Licenses assigned to users you plan to enable for Copilot.
- Access to the Microsoft 365 admin center (admin.microsoft.com) and the Copilot admin pages.
Step-by-Step
- Assign Copilot licenses – In the Microsoft 365 admin center, go to Billing > Licenses, select the Copilot product, and assign licenses to the users or groups who should have access. This is the first gate—only licensed users can use Copilot.
- Review default permissions – Copilot inherits permissions from the user’s existing Microsoft 365 roles. Before enabling, check which users have broad access (e.g., Global Admin, SharePoint Admin) and consider limiting Copilot to a pilot group first.
- Create a security group for Copilot users – In the admin center, go to Teams & Groups > Active teams & groups, create a group (e.g., “Copilot Pilot Users”), and add the intended users. This allows you to manage permissions centrally.
- Enable Copilot for the group – Navigate to Settings > Microsoft 365 Copilot (or use the Copilot admin center). Under Copilot permissions, select the group you created. This restricts Copilot availability to only those members.
- Configure data access boundaries – Go to the Data access section in Copilot settings. Choose one of the following:
- All SharePoint sites – Copilot can search all sites, but only returns content the user already has permission to see (default).
- Specific sites – Restrict Copilot to only search a defined list of SharePoint sites. This is safer for sensitive environments.
- Set site-level permissions – If you chose specific sites, add the URLs of the sites Copilot may access. Use the site collection admin to ensure the Copilot service account has read access, but users’ existing permissions still apply.
- Check file and folder permissions – Copilot respects permissions. Review your SharePoint and OneDrive sharing settings: in the SharePoint admin center, go to Policies > Sharing and ensure external sharing is set to your organization’s policy (e.g., “Only people in your organization”).
- Configure sensitivity labels – In the Microsoft Purview portal, apply sensitivity labels to sensitive documents. Copilot will honor these labels and restrict access to users who lack the label permissions.
- Set up audit logging – Enable audit logs in the Purview portal to track Copilot interactions. Go to Solutions > Audit and turn on auditing if not already active. This helps you monitor for unusual access.
- Test with a pilot group – Have the pilot group use Copilot for a week. Ask them to verify they can only see content they normally have access to. Check audit logs for any unexpected queries.
- Roll out to broader users – Once the pilot is successful, expand the security group to include more users. Monitor usage and permissions regularly.
Common Mistakes
- Granting Copilot to all users at once – Without a pilot, you might discover oversharing issues after a wide rollout.
- Assuming Copilot bypasses permissions – It does not; it only surfaces data the user can already access. But if your permissions are overly broad, Copilot will surface that data.
- Ignoring external sharing – If external sharing is enabled, Copilot might include externally shared files in results for users who have access.
- Not using sensitivity labels – Labels are the most effective way to block Copilot from accessing confidential files, even for users who have edit permissions.
- Forgetting to audit – Without audit logs, you won’t know if Copilot is being used inappropriately.
Tips
- Start with a small group and expand gradually.
- Use SharePoint site permissions to restrict Copilot to specific project sites.
- Regularly review your sharing links—set default link type to “Internal” to reduce accidental external exposure.
- Educate users on what Copilot can see and remind them to use sensitivity labels for confidential files.
- Consider using Microsoft 365 Copilot’s “restricted” mode if you need to block web grounding (the ability to pull public web data).
Troubleshooting
- Copilot not appearing for users – Verify licenses are assigned and the user is in the security group. Also check that the Copilot service is enabled in the tenant (Settings > Microsoft 365 Copilot).
- Copilot returns “You don’t have access” – This is expected if the user lacks permission to the underlying file. Check the user’s SharePoint permissions.
- Copilot is missing data from a site – Ensure the site is included in your allowed sites list and that the user has at least read access to that site.
- Copilot is slow – This can happen if you have many sites indexed. Check the SharePoint admin center for indexing status.
- Copilot shows data from a site you restricted – Verify that the site is not in the allowed list, and also check if the user has access via a different path (e.g., a shared link).
Frequently Asked Questions
Q: Does Copilot see all my files?
A: No. Copilot only sees files that the user has permission to access. If you can’t see a file, Copilot won’t show it to you.
Q: Can I block Copilot from accessing a specific document?
A: Yes, by removing the user’s permission to that document or by applying a sensitivity label that restricts access.
Q: Does Copilot work with external users?
A: Copilot is available to external users only if they have a Copilot license and are in your tenant. It respects the same permissions as internal users.
Q: How do I know what Copilot is doing?
A: Enable audit logging in the Purview portal. You can search the audit log for Copilot activities.
Q: Can I set a data retention policy for Copilot interactions?
A: Yes, you can set retention policies for Copilot interactions in the Purview portal, similar to other Microsoft 365 content.
Q: What happens if I remove a user from the Copilot security group?
A: The user immediately loses access to Copilot. Their existing permissions to files remain unchanged.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- iOS 18 Safari Not Working? Fixes That Help
- How to Check Your Linux Kernel for Spectre
- iPhone Safe Mode: How to Enable or Disable It
- Fix Slow Internet Lag on Samsung Galaxy Note
- Google Play Protect: How It Secures Your Android
- Fix SFC Scannow Error in Windows: Complete Guide