Home › Knowledgebase › KB-1309

How to check sharepoint permissions before turning on microsoft copilot

Summary

This guide helps you troubleshoot and resolve: How to check sharepoint permissions before turning on microsoft copilot. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

How to check SharePoint permissions before turning on Microsoft Copilot

Category: Cloud Migration & Modern Workplace

Enabling Microsoft Copilot can significantly improve productivity for small businesses, but it also introduces new data security considerations. Copilot can access and surface information across your Microsoft 365 environment based on existing SharePoint and Teams permissions. If those permissions are too broad, sensitive data—such as payroll records, director-level contracts, or HR files—could become visible to staff members who should not have access.

Before activating Copilot, 220 Internet Services recommends auditing your SharePoint permissions to ensure that AI tools only surface information appropriate for each employee. This helps your business meet Australian privacy obligations and reduces the risk of accidental data exposure.

Step 1: Review your SharePoint site structure

Start by identifying which SharePoint sites contain sensitive business information. Small businesses often use a mix of team sites, communication sites, and document libraries.

  1. Sign in to the Microsoft 365 admin centre using an administrator account.
  2. In the left-hand navigation, expand Admin centres and select SharePoint.
  3. In the SharePoint admin centre, select Active sites to view all sites in your tenant.
  4. Make a list of sites that store confidential documents, such as finance, payroll, or executive folders.

Step 2: Check site-level permissions

Verify who has access to each site and at what level. Avoid using broad groups like Everyone except external users for sites containing sensitive data.

  1. From the SharePoint admin centre, select Active sites and click on the site you want to review.
  2. In the site details pane, select the Permissions tab.
  3. Click Manage permissions to open the classic SharePoint permissions page for the site.
  4. Review the list of users and groups with access.
  5. Look for roles such as Full Control, Edit, Contribute, and Read. Full Control should be limited to trusted staff.
  6. Remove any users or groups that no longer require access, such as former employees or completed project teams.

Step 3: Audit document library and folder permissions

Site-level access does not always reflect folder-level permissions. Sensitive files may be stored in libraries with unique permissions that override the site default.

  1. Open the SharePoint site in a web browser.
  2. Navigate to the document library containing sensitive files.
  3. Select a folder or file, then click the information icon (i) or select Manage access from the command bar.
  4. Review the Direct access and Links sections to see who can view or edit the content.
  5. Check for Anyone links or People in your organisation links that grant broad access. These should be removed or restricted for confidential documents.
  6. If a folder has unique permissions, confirm that only the appropriate staff members or security groups are listed.

Step 4: Review Microsoft Teams connected sites

Every standard Microsoft Teams channel has an associated SharePoint site. Files shared in Teams are stored in SharePoint, so Teams permissions directly affect what Copilot can surface.

Important: Private channels in Microsoft Teams do not share the parent team's SharePoint site. Each private channel has its own separate SharePoint site collection with its own permissions.

  1. Open Microsoft Teams.
  2. Review each team and channel, particularly those discussing payroll, strategy, or client sensitive matters.
  3. Check the Members tab in each team to confirm only relevant staff are included.
  4. For private channels, verify that membership is restricted and remember that the associated SharePoint site collection is separate from the parent team site.

Step 5: Review sharing settings and compliance reports

For a broader view, use the Microsoft 365 compliance portal and SharePoint admin centre to identify sites with open or excessive access.

  1. In the SharePoint admin centre, go to Active sites and select a site to review its sharing settings.
  2. Confirm that external sharing is disabled or restricted for sites containing sensitive internal data.
  3. Check the default sharing link type. It should be set to People in your organisation or Specific people, rather than Anyone.
  4. For detailed reporting, sign in to the Microsoft Purview compliance portal and navigate to Data lifecycle management or Information protection to review sensitivity labels and Data Loss Prevention (DLP) policies.

Step 6: Microsoft Purview, sensitivity labels, and DLP

Microsoft Purview provides tools to classify and protect sensitive information before Copilot is enabled. Sensitivity labels can be applied to documents and emails to enforce encryption and access restrictions. Data Loss Prevention policies can identify and block the sharing of sensitive content, such as tax file numbers or financial records.

For Copilot readiness, review your organisation's sensitivity labels and DLP policies in the Microsoft Purview compliance portal. Ensure that confidential documents are labelled appropriately so that Copilot does not surface restricted content to unauthorised users. This supports compliance with the Privacy Act 1988 and the Australian Privacy Principles.

Step 7: Remediate before enabling Copilot

If you find overly broad permissions, take corrective action before turning on Copilot:

  • Move sensitive documents to dedicated libraries with restricted access.
  • Replace Anyone links with Specific people links.
  • Use Microsoft 365 groups or security groups to manage access by role rather than assigning permissions to individuals.
  • Apply sensitivity labels to confidential documents.
  • Document your permission structure so future changes can be reviewed consistently.

Troubleshooting and remediation

If permissions cannot be remediated immediately, do not enable Copilot for the affected sites or users. Consider the following options:

  • Exclude specific SharePoint sites from Copilot indexing using the Microsoft 365 admin centre or SharePoint admin centre search settings.
  • Restrict Copilot access to specific security groups while broader permissions are corrected.
  • Engage 220 Internet Services to assist with permission remediation and Copilot readiness planning.
Why this matters for Australian small businesses: Under the Privacy Act 1988 and the Australian Privacy Principles, businesses must take reasonable steps to protect personal information. Enabling Copilot without auditing SharePoint permissions could result in staff accessing personal or confidential data they are not authorised to see, creating compliance and reputational risk.
Do not enable Copilot until your permission audit is complete. Once Copilot is active, it can reference content across SharePoint and Teams based on existing access rights. Fixing permissions after activation does not remove information Copilot may have already indexed.

If you need assistance reviewing your SharePoint permissions or preparing your environment for Microsoft Copilot, Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket