Home › Knowledgebase › KB-1130

Is Your Business Ready for Microsoft Copilot? A Data Security Checklist for Australian SMBs

Summary

This guide helps you troubleshoot and resolve: Is Your Business Ready for Microsoft Copilot? A Data Security Checklist for Australian SMBs. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Microsoft Copilot can transform how your organisation works by surfacing insights across Microsoft 365, but it can only access data that your users already have permission to see. For Australian small and medium businesses, enabling Copilot without first reviewing SharePoint, OneDrive, Teams, and mailbox permissions risks exposing sensitive financial records, employee details, and client information. This checklist will help you audit and secure your data governance before you roll out Copilot to your team.

Prerequisites

Before beginning the readiness checklist, confirm the following requirements are met:

Quick Fix Steps

  1. Run a permissions audit across SharePoint, OneDrive, Microsoft 365 Groups, Teams, and mailboxes.
  2. Remove broad access links and guest permissions where no longer needed.
  3. Apply sensitivity labels to confidential documents and configure Data Loss Prevention policies.
  4. Review and tighten external sharing settings.
  5. Test Copilot access with a pilot group before organisation-wide rollout.

Detailed Instructions

Step 1: Audit SharePoint, OneDrive, Groups, Teams, and Mailbox Permissions

  1. Sign in to the Microsoft 365 admin centre using your global administrator account.
  2. Navigate to SharePoint in the left-hand menu, then select Active sites and review each site collection for unique permissions.
  3. For OneDrive, select OneDrive from the admin centre menu, then review User files and individual site permissions.
  4. Review Microsoft 365 Groups and Teams membership and channel permissions, as Copilot can surface content from team sites, chats, and shared files.
  5. Review Exchange mailbox permissions and calendar sharing settings, as Copilot can access email and calendar data that users have permission to view.
  6. Identify any folders, libraries, mailboxes, or sites with Full Control or Edit permissions assigned to Everyone or All Authenticated Users.
  7. Export your findings from the SharePoint admin centre or Microsoft Purview and document them in a spreadsheet, noting site name, URL, permission level, assigned group or user, and remediation owner.

Step 2: Remove Broad Access Links

  1. In the SharePoint admin centre, go to Policies > Sharing.
  2. Review the External sharing settings for SharePoint and OneDrive.
  3. Disable Anyone links where possible, or restrict them to specific trusted domains.
  4. Search for existing Anyone links using the Sharing reports and remove those pointing to sensitive folders.
Tip: Use the SharePoint Advanced Management add-on or Microsoft Purview to generate a Data Access Governance report showing exactly which users can access which files.

Step 3: Apply Sensitivity Labels and Configure Data Loss Prevention

  1. Open the Microsoft Purview compliance portal.
  2. Go to Information protection > Labels.
  3. Create labels such as Confidential, Internal Only, and Public.
  4. Configure encryption and access restrictions for the Confidential label.
  5. Publish the labels to your users via Label policies so they can apply them in Word, Excel, PowerPoint, and Outlook.
  6. In Microsoft Purview, go to Data loss prevention > Policies and create DLP policies that match your sensitivity labels.
  7. Configure DLP rules to detect, restrict, or block sharing of confidential content, including content that Copilot might surface in responses.

Step 4: Review External Sharing and Guest Access

  1. In the Microsoft 365 admin centre, select Settings > Org settings > SharePoint.
  2. Under External sharing, ensure guest access is limited to trusted partners only.
  3. Review Microsoft Entra ID > External Identities for guest users who no longer require access.
  4. Remove guest accounts for former contractors or completed projects.

Step 5: Pilot Copilot with a Controlled Group

  1. Assign Copilot licences to a small pilot group first, such as IT and HR managers.
  2. Monitor what Copilot surfaces during the pilot period.
  3. If sensitive data appears in Copilot responses, trace the source permission and remediate it before expanding the rollout.
Caution: Enabling Copilot does not create new permissions, but it makes existing permissions much more visible. A file that was technically accessible but rarely opened can now be surfaced instantly to any user with read access.

Troubleshooting

Copilot is not appearing in Microsoft 365 apps

Copilot is not surfacing expected data

Copilot is surfacing restricted documents

Sensitivity labels are not appearing in Office apps

External users can still access shared folders

Taking the time to secure your SharePoint, OneDrive, Teams, and mailbox environment before enabling Copilot protects your business from accidental data exposure. If you need assistance auditing your permissions or configuring sensitivity labels, Open a Ticket with 220 Internet Services.

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