Microsoft 365 Copilot Data Governance: The Australian Business Guide to Deploying Copilot Safely

Microsoft 365 Copilot data governance is the most overlooked part of any AI deployment in Australian business right now. Organisations are licensing Copilot, training staff on prompts, and measuring productivity gains — but the more consequential question often goes unasked: what data can this AI actually see, and should it?

Copilot is a powerful AI assistant embedded across the Microsoft 365 suite. It summarises emails, drafts documents, surfaces insights from Teams conversations, and answers questions by searching across your files. That capability depends entirely on access. Copilot draws on the same data the logged-in user can reach. In a well-governed Microsoft 365 environment, that is a reasonable design. In an environment with years of accumulated file sharing, inherited permissions, and broadly accessible SharePoint libraries, the results can create serious compliance and trust problems.

This guide is for Australian businesses, not-for-profits, and mid-market organisations with 30 to 500 Microsoft 365 seats that are planning a Copilot rollout or have already enabled it and want to confirm the foundations are sound. It covers what Copilot can actually access, your Privacy Act obligations, how to prepare your environment, and how to maintain oversight once Copilot is live.

What Copilot Can Actually Access in Your Environment

Microsoft 365 Copilot does not create new access permissions. It works within the existing permission boundaries of your tenant. When a staff member uses Copilot, the AI can access anything that user has permission to view: emails in Exchange Online, files in OneDrive, documents in any SharePoint site they are a member of, Teams conversations they participate in, and calendar data.

This sounds controlled. In practice, it amplifies a problem many organisations have quietly lived with for years. SharePoint sites accumulate members who changed roles or left the organisation. Documents get shared with "everyone in the organisation" for convenience and are never restricted again. Permissions granted for a project that ended two years ago remain active today.

None of this was urgent when finding a document required knowing where it was stored or being sent a direct link. Copilot changes that. A staff member asking Copilot to summarise everything related to a client, or to surface recent salary discussions, may receive a response that pulls from files they technically had access to but were never intended to retrieve in that way.

Consider a practical example. A hospitality group with 80 staff has a SharePoint site for the payroll and finance team. Three years ago, an all-staff HR update was posted there for convenience and the site access was never narrowed back down. Today, 40 staff with no business need to access payroll records are still site members. When Copilot is enabled, those 40 staff can ask questions and receive responses drawing from payroll data they were never supposed to see. The permissions were the problem. Copilot made the problem visible.

Your Privacy Act Obligations When Using AI

The Privacy Act 1988 and the Australian Privacy Principles (APPs) govern how Australian organisations handle personal information. Using an AI tool that can access, process, and surface personal information as part of its core function adds compliance considerations that most businesses have not yet addressed in their policies or risk frameworks.

APP 1: Open and transparent management

Your organisation must have a current privacy policy that accurately describes how you collect, use, and disclose personal information. If Copilot is processing employee or client data, your privacy policy should say so. Many businesses have policies written before AI tools were part of their operations.

APP 6: Use and disclosure

Personal information should only be used or disclosed for the primary purpose for which it was collected. If client data stored in SharePoint is being surfaced by Copilot in responses to staff who have no business need for that data, there is a potential APP 6 issue that could become a notifiable data breach under the Notifiable Data Breaches scheme if it results in serious harm.

APP 11: Security

Your organisation must take reasonable steps to protect personal information from misuse, interference, loss, and unauthorised access. Deploying Copilot into an environment with poor permissions hygiene and no data classification framework may fall short of the "reasonable steps" standard, particularly as the Office of the Australian Information Commissioner has increasingly emphasised proactive governance over reactive response.

Microsoft's enterprise commitments mean your data is not used to train AI models and does not leave your Microsoft 365 tenant. These commitments address whether your data is exposed to Microsoft or third parties. They do not address whether personal information is being surfaced inappropriately within your own organisation through Copilot queries.

The Pre-Deployment Checklist: 8 Steps Before You Switch Copilot On

These eight steps are the minimum governance preparation before enabling Microsoft 365 Copilot for staff. Complete them in sequence where possible. Organisations that have already enabled Copilot without this preparation should work through them as a remediation programme.

• Run a data access review. Identify SharePoint sites, Teams, and document libraries containing sensitive data: HR files, board papers, financial records, client personal information, and anything subject to legal privilege. Document who has access and whether it is still appropriate.
• Audit SharePoint site membership. Export member lists for every SharePoint site. Remove guest accounts that are no longer active, staff who have left or changed roles, and anyone whose access cannot be linked to a current business need. Prioritise sites active for more than two years.
• Review and restrict sharing links. The Microsoft 365 admin centre produces a report of sharing links across your tenant. Identify any links set to "anyone with the link" or "people in your organisation" for documents that should have narrower access. Replace broad links with person-specific sharing.
• Deploy a sensitivity labelling framework. Define a label taxonomy in Microsoft Purview: Public, Internal, Confidential, and Highly Confidential at a minimum. Apply labels to documents containing personal information, financial data, and anything subject to regulatory obligations.
• Exclude the most sensitive sites from Copilot indexing. The SharePoint admin centre allows administrators to exclude specific sites from Copilot's search index. Even if a user has permission to access a site, Copilot will not surface content from excluded sites. Use this for HR, payroll, board, and legal sites while broader governance work is underway.
• Enable Microsoft Purview Audit before go-live. Turn on audit logging before Copilot is enabled for any user. This creates a record of interactions, including what prompts were submitted and what content was returned, which is essential for any future investigation or regulatory response.
• Review Entra ID guest access settings. Guest accounts represent external users who may have accumulated access to internal resources. Review all active guest accounts, remove those no longer current, and apply Conditional Access policies that restrict Copilot access for guests by default.
• Draft and communicate an acceptable use policy. Before any staff member uses Copilot, they should acknowledge a written acceptable use policy covering: what Copilot can access, what information should not be entered as a prompt, how to review AI-generated outputs, and how to report unexpected results.

Sensitivity Labels and Data Classification with Microsoft Purview

Sensitivity labels are the most practical tool in Microsoft 365 for controlling how data is handled, shared, and accessed by AI tools including Copilot. Labels are applied to files, emails, and Teams messages, and they carry policies with them. A document labelled Confidential can be configured to prevent external sharing, require encryption, and restrict access to specific users or groups regardless of which SharePoint site it sits in.

Microsoft Purview, included in Microsoft 365 Business Premium and the E3 and E5 plans used by most mid-market Australian businesses, provides the platform to create and deploy sensitivity labels. Setting up a working framework involves three stages.

Stage 1: Define your label taxonomy. For most Australian businesses, four levels work well. Public covers content that can be shared freely, such as marketing materials. Internal covers content for staff only. Confidential covers information that could cause harm if shared externally, including client records and commercial contracts. Highly Confidential covers information subject to legal privilege, board confidentiality, or specific regulatory requirements such as APRA obligations.

Stage 2: Configure the label policies. For each label, define the protection settings that apply automatically. Internal documents might require authentication before external sharing is permitted. Highly Confidential documents can be excluded from Copilot indexing entirely, meaning Copilot will not surface them in responses even for users who have SharePoint permission to view them.

Stage 3: Roll out labelling to existing content. New documents can be automatically labelled based on content detected by Purview's data loss prevention policies. For example, any document containing a Tax File Number can be classified as Highly Confidential automatically. Existing documents require either a manual labelling campaign or an auto-labelling run. Prioritise high-risk repositories first.

Auditing SharePoint and OneDrive Permissions

A SharePoint and OneDrive permissions audit is, for most organisations, the most time-consuming part of Copilot preparation. It is also the most important, because permissions are the primary mechanism that determines what Copilot can surface in any given user's responses.

The audit covers four areas: site-level membership review, sharing link audit, external sharing settings, and individual OneDrive review. For each SharePoint site, confirm that every current member has a current, legitimate business reason for access. For sharing links, identify any link scoped to "anyone with the link" or "people in your organisation" for documents that should have narrower access. For sites that should never be shared externally, disable external sharing in the SharePoint admin centre. For OneDrive, remind staff to revoke access for files that are no longer being actively collaborated on.

This is not a one-time exercise. Permissions drift back toward oversharing over time. A quarterly review is the practical way to keep the environment clean after the initial cleanup.

Microsoft Entra ID and Conditional Access for Copilot

Microsoft Entra ID is the identity and access management layer that underpins all Microsoft 365 services. Getting it configured correctly before Copilot deployment matters as much as cleaning up SharePoint permissions, because Entra ID controls who can access the tenant, from which devices, and under what conditions. A compromised user account means a compromised Copilot session with AI-assisted access to everything that user can see.

Multi-factor authentication as a baseline. MFA must be enforced for every user before Copilot is licensed. A Copilot-licensed account compromised through a phishing attack gives the attacker AI-assisted access to all the data that user can reach, which significantly amplifies the potential impact of the breach. If MFA is not yet fully enforced across your organisation, that work must happen first.

Conditional Access policies. Conditional Access allows administrators to define conditions before a user can access Microsoft 365 applications including Copilot: requiring device compliance through Microsoft Intune, blocking access from unmanaged devices, restricting access to verified geographic locations, and requiring re-authentication after inactivity. These controls ensure Copilot is only accessible from endpoints that meet your security baseline.

Guest account governance. Review all guest accounts in Entra ID. Determine whether each still requires active access, remove accounts that are no longer current, and apply a policy that Copilot is not enabled for guest users by default. In most cases, there is no business justification for a guest user to access your Copilot deployment.

Staff Training and Acceptable Use Policies

Technical controls are necessary but not sufficient. The human layer of Copilot governance matters equally. Staff who do not understand how Copilot works, what it can access, or what responsible use looks like will create risk regardless of how well the technical environment is configured.

An acceptable use policy for Microsoft 365 Copilot should cover four things in plain language. First, what Copilot can access: any file, email, or Teams message the user has permission to view. Copilot queries are effectively searches across their accessible data. Second, what not to enter as a prompt: client personal information, sensitive commercial data, or anything classified as Confidential or Highly Confidential. The practical guideline is that anything you would not type into a web search engine should not be typed into Copilot. Third, reviewing AI-generated outputs: Copilot outputs should be reviewed before they are sent, saved, or acted on. AI tools can produce confidently stated responses that are factually incorrect, misattribute data, or draw on outdated information. Fourth, reporting unexpected outputs: provide a clear channel for staff to report if Copilot surfaces data they believe they should not have seen. This serves as both a governance control and a permissions hygiene tool.

Training should be practical and concise. A 30-minute session with real prompt examples is more effective than a lengthy policy document that staff acknowledge without reading. Refresher training every six months, and whenever Copilot's capabilities are significantly updated, keeps the human layer current.

Ongoing Governance: Monitoring and Review

Deploying Copilot is the beginning of a governance programme. The controls put in place before launch require ongoing maintenance, and Copilot's capabilities continue to expand with each Microsoft update cycle. The following practices constitute a minimum ongoing governance programme.

Quarterly permissions review. Review SharePoint site membership and sharing links every quarter. For most organisations with 50 to 200 seats, this takes two to four hours and can be completed using SharePoint admin centre reports. Build it into the IT calendar as a standing item.

Monthly audit log review. Review Copilot interaction logs in Microsoft Purview each month. Look for repeated queries targeting restricted repositories, access from unexpected locations or unmanaged devices, or use patterns that suggest staff are inputting information that should not be in a prompt. Most months, this review will produce nothing of concern. The value is in catching the exception early and maintaining a clear record that monitoring was taking place.

Annual Privacy Act compliance check. Each year, confirm that your privacy policy accurately describes how AI tools are used in handling personal information. Organisations covered by APRA, ASIC, or sector-specific privacy obligations should align this review with their broader compliance calendar and document the outcome. If the Office of the Australian Information Commissioner publishes updated guidance on AI and privacy, incorporate any relevant changes.

Policy review after significant Copilot updates. When Microsoft adds a significant new Copilot capability, review your acceptable use policy and technical controls to confirm they still address the updated scope. Your managed service provider should be flagging these updates as part of their standard advisory relationship.

Written by the All IT Services team. All IT is a Sydney-based managed IT provider supporting businesses, hospitality groups, not-for-profits, and financial services organisations across Australia.