Governing Microsoft 365 Copilot & SharePoint Permissions Under the ACSC Essential Eight

Microsoft 365 Copilot is the fastest-adopted generative AI productivity tool in Australian corporate and public sector history. However, Copilot introduces a major security reality: it does not bypass permissions; it ruthlessly exposes existing permission sprawl.

If an employee had inadvertent "Everyone except external users" read access to a board minutes folder created in 2021, they probably never stumbled upon it. But when that employee asks Copilot: "What were our executive salary discussions last quarter?", Copilot will summarize the unredacted documents in seconds.

1. The Four Primary AI Exposure Vectors in Microsoft 365

Microsoft 365 Copilot does not create new permissions; rather, it relentlessly exploits existing permission sprawl. Because Copilot utilizes the Microsoft Graph to surface information with natural language fluency, any document a user has technically been granted access to—even if buried deep within an archived 2017 folder—is instantly indexed and synthesized.

Before deploying Copilot licenses across your Australian workforce, enterprise security teams and CISOs must audit four critical threat vectors:

1. Legacy "Everyone Except External Users" (EEEU) Permissive Sharing: Historic SharePoint sites and root libraries frequently granted organization-wide read access. While humans rarely discovered these files via manual browsing, Copilot semantic search indexes them in milliseconds, answering prompt queries with confidential executive remuneration tables or merger communications.
2. Orphaned Teams & Decommissioned SharePoint Sites: Abandoned project teams, departed staff sites, and unmonitored committee workspaces that contain sensitive financial, medical, or tender data without active site owners or retention policies.
3. Over-Permissive Copilot Studio Custom Agents: Custom AI agents connected to REST APIs or Power Automate flows executing with elevated service principal credentials rather than user-delegated context, inadvertently bypassing backend record-level security.
4. Non-Sovereign API Connectors: Third-party AI plugins and Graph connectors sending unstructured prompts to unverified foreign endpoints outside Australian geographic boundaries.

2. Mapping Microsoft Purview & Entra Controls to Essential Eight Maturity Levels

The ACSC Essential Eight Maturity Model provides a baseline of cyber mitigation strategies. Below is Ultron's architectural blueprint mapping Microsoft 365 and Purview governance controls against each maturity level:

3. Mitigating Oversharing: Restricted Site Access (RSA) Policies

When preparing for an enterprise rollout, organizations cannot afford to halt projects for months while manual file re-permissioning takes place. Microsoft provides two vital interim containment mechanisms:

Restricted SharePoint Search (RSS)

Restricted SharePoint Search allows administrators to configure an allow-list of up to 100 enterprise-approved, curated SharePoint sites. When a user queries Copilot, the AI engine limits its background semantic search exclusively to those verified sites (in addition to the user's personal OneDrive and recent files). This immediately prevents Copilot from traversing ungoverned legacy departmental sites while permission remediation proceeds in parallel.

Site-Level Restricted Access Control (RSA) via PowerShell

For sites containing strictly confidential IP, executive salaries, or board papers, site collection administrators can enforce Restricted Site Access (RSA). Unlike traditional SharePoint groups, RSA enforces access boundaries based on a designated Entra ID security group. Even if a user receives a direct sharing link to a document inside the site, Entra rejects the access request unless the user is explicitly in the designated security group:

4. Australian Data Sovereignty and Privacy Act 1988 Alignment

Under Australian Privacy Principle 11 (APP 11) and the Australian Government Information Security Manual (ISM), handling protected citizen, tax, or health records requires verifiable data sovereignty. Microsoft guarantees that for commercial tenants provisioned within the Australian geographical boundary:

• Data at Rest & in Transit: Prompts, grounded retrieval chunks, and generated responses remain encrypted at rest and in transit within Australian data center regions (Sydney / Canberra / Melbourne).
• Zero LLM Retraining: Customer prompts, proprietary data, and synthesized answers are never utilized to train the foundational OpenAI base models.
• Purview Customer Lockbox: If Microsoft support engineers ever require access to diagnose tenant issues, access requires explicit, cryptographically logged customer approval.

5. Australian Enterprise Case Study: National Superannuation Fund

An Australian industry superannuation fund managing over \$45 billion in assets for 380,000 members planned to roll out Microsoft 365 Copilot to 650 investment analysts and member service managers. However, internal risk committees raised red flags regarding the accidental disclosure of member tax file numbers, private equity deal memos, and executive board papers.

Ultron Developments conducted a comprehensive Essential Eight readiness engagement:

• Automated DLP & SIT Scanning: Deployed automated Purview Data Loss Prevention rules configured with Australian Sensitive Information Types (SITs) for TFNs, Medicare cards, and passport numbers, automatically blocking these strings from AI prompt inclusion.
• PIM & Phishing-Resistant MFA: Implemented FIDO2 hardware tokens and Entra Privileged Identity Management for all administrators managing Copilot Studio agent connectors.
• RSA Isolation of Deal Memos: Enforced Restricted Access Control across 48 sensitive investment committee SharePoint sites, restricting access to verified Entra security groups.
• Business Outcome: The fund passed independent IRAP and Essential Eight Maturity Level 2 audits with zero non-conformances, enabling a rapid, confident enterprise rollout that saved analysts an average of 4.5 hours per week in research synthesis.

To build an auditable AI security posture, read our comprehensive companion guides on preventing Copilot data oversharing and our 6-phase Australian Copilot rollout methodology, or consult our dedicated Microsoft Copilot consulting team.