How to prepare my business data for Microsoft Copilot Australia
Category: AI & Automation
Understanding the risk
Microsoft Copilot respects existing permissions within your Microsoft 365 tenant. If an employee can access a file in SharePoint or OneDrive, Copilot can surface information from that file in response to a prompt. For an Australian small business, this means payroll records, client contracts, salary details, and strategic plans could appear in AI-generated responses if permissions are too broad.
Prerequisites and licensing requirements
Before beginning the preparation steps, confirm that your organisation meets the licensing and readiness requirements for Microsoft 365 Copilot.
- License requirements: Users must be assigned a Microsoft 365 E3 or E5 license, or a Microsoft 365 Business Premium license with the Copilot for Microsoft 365 add-on license.
- Licensing costs: Copilot for Microsoft 365 is sold as a per-user, per-month add-on. Confirm current pricing with your MSP or via the Microsoft 365 admin center before committing to a rollout.
- Business readiness: Complete a business readiness assessment to identify which departments will benefit most from Copilot and which data stores require the strictest permission reviews.
- Tenant requirements: Your organisation must use Microsoft Entra ID (formerly Azure Active Directory) and have OneDrive for Business and SharePoint Online enabled for users.
Australian data residency and sovereignty considerations
Microsoft 365 Copilot processes data through Microsoft's global AI infrastructure. Australian businesses should consider the following before enabling the service:
- Data residency: Confirm with Microsoft whether Copilot processing for your tenant occurs within Australian data regions or if prompts and responses may be processed in other regions.
- Data sovereignty: If your business is subject to Australian government or industry data sovereignty requirements, review Microsoft's data processing terms to determine if Copilot meets your compliance obligations.
- Client confidentiality: For legal, accounting, or health-related businesses, check whether client contracts restrict the use of generative AI tools that may process data outside Australia.
Step 1: Audit your SharePoint permissions
Before enabling Copilot, review who has access to what across your SharePoint sites and document libraries.
- Sign in to the Microsoft 365 admin center using an administrator account.
- In the left navigation menu, select Admin centers, then choose SharePoint.
- In the SharePoint admin center, select Active sites from the left-hand menu.
- Click on a site name to open its details, then select the Permissions tab.
- Review the site members and groups. Identify any groups with "Full Control" or "Edit" access that include general staff members.
- Select the group or user, click Edit permissions, and remove access for libraries containing confidential information such as payroll, HR files, or executive documents.
- To export a record, select Reports from the SharePoint admin center menu, choose Site usage or Permission report, and click Export.
Step 2: Restructure folders for security
A flat folder structure with open access makes it difficult to control what Copilot can see. Organise your data so sensitive information is isolated.
- Create dedicated document libraries for HR, finance, and executive management with restricted membership.
- Avoid storing confidential spreadsheets in general team folders used by all employees.
- Use unique permissions sparingly; instead, assign access through Microsoft 365 groups tied to job roles.
- Rename folders clearly so staff understand which areas contain restricted material.
Step 3: Review OneDrive and personal storage
Copilot can index OneDrive files belonging to users in your organisation. Small business owners should ensure employees are not storing sensitive client records in personal OneDrive folders with overly permissive sharing links.
- Sign in to the Microsoft 365 admin center.
- In the left navigation menu, select Admin centers, then choose OneDrive.
- In the OneDrive admin center, select Sharing from the left-hand menu.
- Review external sharing settings and disable "Anyone" links where possible.
- Select Active sharing links to view links currently granting access to files.
- Revoke "Anyone with the link" access for files containing client or financial data by selecting the link and clicking Remove access.
- Encourage staff to move business-critical documents into team SharePoint libraries rather than personal drives.
Step 4: Apply sensitivity labels and configure Copilot policies
Microsoft Purview sensitivity labels allow you to classify documents and apply protection rules. Labels such as "Confidential" or "Internal Only" can restrict copying, printing, and external sharing.
- Sign in to the Microsoft Purview compliance portal.
- In the left navigation pane, select Solutions, then choose Information protection.
- Click Create a label to create a new sensitivity label (for example, "Confidential" or "Internal Only").
- Configure the label settings to define encryption, content marking, and automatic labeling rules as required.
- Select Label policies from the Information protection menu, then click Publish to publish the labels to relevant users or groups.
- Train staff to apply labels when saving new documents in SharePoint and OneDrive.
- To configure Copilot label policies, remain in the Microsoft Purview compliance portal, select Data lifecycle management from the left navigation, then choose Microsoft 365 Copilot.
- Review the available Copilot data governance options and configure policies to restrict Copilot from surfacing content protected by specific sensitivity labels where supported.
Step 5: Test Copilot in a controlled group
Do not enable Copilot for the entire business at once. Start with a pilot group of trusted users.
- Sign in to the Microsoft 365 admin center.
- In the left navigation menu, select Users, then choose Active users.
- Select the users in your pilot group, click Licenses and apps, and assign the appropriate Copilot licenses.
- Ask pilot users to run sample queries related to payroll, client lists, and business strategy.
- Review the responses to confirm no restricted data is being surfaced inappropriately.
- Adjust permissions and labels based on findings before a wider rollout.
Step 6: Train your staff
Technology alone cannot prevent data exposure. Employees need to understand how Copilot works and what information is safe to query.
- Explain that Copilot can see files they have permission to access.
- Advise staff not to paste confidential client information into prompts unless it is already protected by appropriate permissions.
- Establish a simple policy for handling AI-generated output that contains personal or financial data.
Troubleshooting common issues
Copilot is not surfacing expected data
- Verify that the content is stored in SharePoint Online or OneDrive for Business. Copilot does not index data stored on local file servers or third-party cloud storage unless it has been migrated.
- Confirm the user has the required permissions to access the source document. Copilot cannot surface content the user cannot already open.
- Check that the content has been indexed. Newly uploaded or permission-changed files may take several hours to become searchable by Copilot.
Permission changes are not taking effect
- Allow up to 24 hours for permission changes to propagate across the Microsoft 365 tenant and be reflected in Copilot's search index.
- If you removed a user from a SharePoint group, ask them to sign out and sign back in to refresh their access token.
- Review whether the user still has access through a different group or direct sharing link. Remove all indirect paths to the confidential content.
Sensitivity labels are not restricting Copilot responses
- Confirm the label was published to the user or group via the Microsoft Purview compliance portal under Information protection > Label policies.
- Verify the document has the label applied. Labels do not apply retroactively to existing content unless auto-labeling policies are configured.
- Check that your Copilot license and tenant configuration support label-based restrictions, as this feature may depend on your subscription level.