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.
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:
- Users must have a valid Copilot for Microsoft 365 licence assigned in the Microsoft 365 admin centre. Copilot for Microsoft 365 requires a base licence such as Microsoft 365 E3, E5, Business Premium, or the Copilot add-on for eligible plans.
- OneDrive for Business must be provisioned for every user who will use Copilot. Copilot requires a OneDrive location to store and surface personal file data.
- Review data residency requirements under the Australian Privacy Act and the Australian Privacy Principles (APPs). Confirm where your Microsoft 365 tenant data is stored and whether Copilot processing meets your organisation's obligations for handling personal information.
Quick Fix Steps
- Run a permissions audit across SharePoint, OneDrive, Microsoft 365 Groups, Teams, and mailboxes.
- Remove broad access links and guest permissions where no longer needed.
- Apply sensitivity labels to confidential documents and configure Data Loss Prevention policies.
- Review and tighten external sharing settings.
- Test Copilot access with a pilot group before organisation-wide rollout.
Detailed Instructions
Step 1: Audit SharePoint, OneDrive, Groups, Teams, and Mailbox Permissions
- Sign in to the Microsoft 365 admin centre using your global administrator account.
- Navigate to SharePoint in the left-hand menu, then select Active sites and review each site collection for unique permissions.
- For OneDrive, select OneDrive from the admin centre menu, then review User files and individual site permissions.
- Review Microsoft 365 Groups and Teams membership and channel permissions, as Copilot can surface content from team sites, chats, and shared files.
- Review Exchange mailbox permissions and calendar sharing settings, as Copilot can access email and calendar data that users have permission to view.
- Identify any folders, libraries, mailboxes, or sites with Full Control or Edit permissions assigned to Everyone or All Authenticated Users.
- 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
- In the SharePoint admin centre, go to Policies > Sharing.
- Review the External sharing settings for SharePoint and OneDrive.
- Disable Anyone links where possible, or restrict them to specific trusted domains.
- Search for existing Anyone links using the Sharing reports and remove those pointing to sensitive folders.
Data Access Governance report showing exactly which users can access which files.Step 3: Apply Sensitivity Labels and Configure Data Loss Prevention
- Open the Microsoft Purview compliance portal.
- Go to Information protection > Labels.
- Create labels such as Confidential, Internal Only, and Public.
- Configure encryption and access restrictions for the Confidential label.
- Publish the labels to your users via Label policies so they can apply them in Word, Excel, PowerPoint, and Outlook.
- In Microsoft Purview, go to Data loss prevention > Policies and create DLP policies that match your sensitivity labels.
- 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
- In the Microsoft 365 admin centre, select Settings > Org settings > SharePoint.
- Under External sharing, ensure guest access is limited to trusted partners only.
- Review Microsoft Entra ID > External Identities for guest users who no longer require access.
- Remove guest accounts for former contractors or completed projects.
Step 5: Pilot Copilot with a Controlled Group
- Assign Copilot licences to a small pilot group first, such as IT and HR managers.
- Monitor what Copilot surfaces during the pilot period.
- If sensitive data appears in Copilot responses, trace the source permission and remediate it before expanding the rollout.
Troubleshooting
Copilot is not appearing in Microsoft 365 apps
- Confirm the user has a valid Copilot for Microsoft 365 licence assigned in the Microsoft 365 admin centre.
- Ensure the user has OneDrive for Business provisioned; Copilot requires a OneDrive location to function.
- Check that the user is on the Current Channel or Monthly Enterprise Channel for Microsoft 365 Apps.
Copilot is not surfacing expected data
- Verify that the user has the necessary permissions to access the source file, email, or Teams message.
- Check that the data resides in a location Copilot can index, such as SharePoint, OneDrive, Exchange, or Teams.
- Confirm the content has been indexed by Microsoft Search; newly created or modified files may take time to appear.
- Review whether overly restrictive permissions or DLP policies are blocking Copilot from accessing the content.
Copilot is surfacing restricted documents
- Review the document's permissions in SharePoint or OneDrive.
- Check for inherited permissions from a parent folder or site.
- Apply a sensitivity label with encryption to restrict access further.
- Use Microsoft Purview Data Lifecycle Management to review retention and access policies.
Sensitivity labels are not appearing in Office apps
- Confirm the label has been published to a Label policy that includes the affected users or groups.
- Check that the user's Office apps are updated to a version that supports sensitivity labels.
- Ask the user to sign out and sign back into their Office apps to refresh the label list.
- Verify that the Unified labelling client is installed and enabled if required for older Office versions.
External users can still access shared folders
- Run a Sharing report in the SharePoint admin centre to identify active Anyone links.
- Revoke the links or change them to People in your organisation only.
- Audit guest users in Microsoft Entra ID and remove those without a current business need.
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?
💻 Open a Ticket