Mapping Microsoft 365 Copilot to Essential Eight ML2 (2026)

Updated 19 October 2026: Microsoft has blocked new enablement of Restricted SharePoint Search (retiring 31 January 2027), so this post now points to Restricted Content Discovery and SharePoint Advanced Management instead. Essential Eight references corrected to the November 2023 Maturity Model revision, and the threat-intelligence and operating-system currency refreshed.

The Australian question every CISO is now asking

Copilot itself is not an Essential Eight control. But the way you configure it shapes six of the eight controls at Maturity Level 2. That is the answer Australian boards, auditors, and IRAP assessors are looking for when they ask whether Microsoft 365 Copilot aligns with the Essential Eight baseline.

The decisions that determine alignment are not Copilot decisions. They are tenant configuration decisions, made before, during, and after a Copilot licence is assigned.

This article is the 2026 control-by-control mapping for Australian organisations. It draws on the ASD Essential Eight Maturity Model (November 2023 revision), the ASD Blueprint for Secure Cloud and its Microsoft 365 Copilot configuration section, and the Microsoft Copilot Control System security and governance documentation. It is written for the people who answer the board's question with evidence: CISOs, security architects, IRAP assessors preparing scope, and the Microsoft 365 administrators who carry the configuration.

What Maturity Level 2 actually demands in 2026

The November 2023 revision of the ASD Essential Eight Maturity Model (Australian Signals Directorate, published at cyber.gov.au) (cyber.gov.au — Essential Eight maturity model, accessed 19 October 2026) tightened Maturity Level 2 in two ways that affect Copilot deployments. First, the patch cadence for internet-facing applications moved to 48 hours for extreme-risk vulnerabilities. Second, application control extended to managed software-as-a-service agents, including Copilot Studio agents that can publish into the production tenant. Microsoft states that Copilot inherits your existing Essential Eight controls and posture.

Maturity Level 2 is the practical target for most Australian non-government organisations. It is also a baseline expectation for organisations preparing IRAP scope under the ASD Blueprint for Secure Cloud.

Maturity Level 1 is increasingly seen as insufficient for organisations handling personal information under the Privacy Act 1988 (Commonwealth). The Office of the Australian Information Commissioner has noted, in published determinations under the Notifiable Data Breaches scheme (oaic.gov.au — Notifiable Data Breaches scheme, accessed 19 October 2026), that failing to apply available security patches or to restrict administrative privileges is evidence of inadequate security measures under Australian Privacy Principle 11.

The 2026 control-by-control mapping

The following table is the consolidated mapping of Microsoft 365 Copilot configuration to ASD Essential Eight Maturity Level 2. Each row identifies the Essential Eight control, the relevant Copilot configuration surface, the Maturity Level 2 requirement, and the practitioner verdict on direct or indirect influence.

The rest of this article walks each row in turn, with the specific Maturity Level 2 language, the recommended Microsoft 365 setting, and the evidence an Australian IRAP assessor will expect to see at scope review.

Control 1 — Application control for Copilot Studio agents

Maturity Level 2 requires that the execution of unapproved applications and agents is prevented on workstations and internet-facing servers. The November 2023 revision extends this principle to managed agents: software-as-a-service automation that can act inside a production tenant. That is the precise category Copilot Studio agents now occupy.

The Copilot Control System (Microsoft, 2026 release waves) introduced publishing gates. These let tenant administrators approve which agents may publish into the tenant and which makers may publish them. Without those gates, any user with a Copilot Studio licence can publish a custom agent directly into production, with its own connectors, data access scope, and conversation logging. Under Maturity Level 2, this is the equivalent of letting any user install arbitrary software-as-a-service applications without approval.

Practitioner recommendation: enable Copilot Control System publishing gates with named approvers. Scope agent publishing to a designated security group, and require a documented business case and risk assessment before approval. Maintain a written register of approved agents that records agent name, publisher, business owner, data scope, approval date, and last review date. Reassess every 90 days. The full configuration walk-through is covered in the companion guide on application control for Copilot Studio agents.

Control 2 — Patch applications including Microsoft 365 Apps and the Copilot client

ASD's Essential Eight Maturity Model defines an "extreme risk" application vulnerability as CVSS 9.0 or above with known active exploitation. Maturity Level 2 requires that such vulnerabilities are remediated within 48 hours of vendor patch availability. For Microsoft 365 Apps, the client that hosts the in-app Copilot experience in Word, Excel, PowerPoint, Outlook, and Teams, patch cadence is governed by the update channel assignment.

Microsoft Learn documents three production-supported channels relevant here: Monthly Enterprise Channel (security and quality updates monthly, on a predictable second-Tuesday release), Current Channel (continuous feature and security updates), and Semi-Annual Enterprise Channel (every six months, with monthly security updates). For Maturity Level 2 alignment, Monthly Enterprise Channel is the minimum acceptable cadence for users with a Copilot licence. Semi-Annual Enterprise Channel falls outside the 14-day high-risk patch window for the Microsoft 365 Apps stack.

The Microsoft Edge for Business browser renders Copilot Chat and the Microsoft 365 Copilot portal, and it sits on its own update cadence. The Stable Channel matches the four-weekly Chromium release cycle. Edge for Business with policy-managed updates is the recommended browser baseline for Copilot users. According to IBM's X-Force Threat Intelligence Index 2026, exploitation of public-facing applications overtook valid-credential abuse to become the leading initial-access vector, accounting for around 40 per cent of cases against roughly 32 per cent for valid accounts. This is why the 48-hour and 14-day windows in the maturity model exist.

Control 3 — Configure Microsoft Office macro settings

This control is unchanged by Copilot. Maturity Level 2 requires that macros from the internet are blocked, that macros are checked for malicious content where allowed, and that only signed macros from trusted publishers may run. Microsoft Office Cloud Policy provides the central administration surface for these settings in the Microsoft 365 Apps admin centre.

Copilot does introduce a failure mode worth noting. A Copilot for Excel agent can be configured to operate against a user's spreadsheets, including spreadsheets containing macros. If a user opens a macro-laden spreadsheet from an unverified internet source and then invokes Copilot to process it, the macro execution path is unchanged from baseline Office macro policy. Copilot does not bypass macro policy. But it can lower a user's perception of risk by abstracting the underlying file. Reinforce macro policy in Copilot user awareness training. The EDUC4TE Copilot Security Roadmap covers this scenario in detail.

Control 4 — User application hardening

Maturity Level 2 requires that browsers, Microsoft Office, PDF readers, and other internet-facing applications are hardened against the most common exploitation vectors. For Microsoft Edge for Business and Microsoft 365 Apps, this means disabling Flash and Java content, restricting unnecessary browser extensions, blocking macros from the internet, and limiting the surface area for code execution from untrusted content.

Copilot's reach is a separate question from application hardening, and Microsoft does not map its oversharing controls to a specific Essential Eight strategy. Microsoft states that Copilot inherits your existing Essential Eight controls and posture. By default, Microsoft 365 Copilot can draw on every SharePoint site the responding user can access, so permissions are the control that matters. Use SharePoint Advanced Management data access governance reports and site access reviews to find and fix overshared sites. Where a site needs protection while that work is under way, Restricted Content Discovery keeps its content out of organisation-wide search and Copilot responses without changing permissions (Microsoft Learn — Restricted Content Discovery). Restricted Access Control then limits a site to members of a named security group or Microsoft 365 group (Microsoft Learn — Restricted Access Control).

Treat Restricted Content Discovery as temporary. Excessive use reduces the completeness of search and Copilot answers, so review it on a set cadence and remove it once access is remediated. The ASD Blueprint for Secure Cloud is explicit on minimum necessary access: access to information should be limited to what the user's role requires. Document the owner and review date for each site you protect, and keep that record in your evidence pack.

Control 5 — Restrict administrative privileges

Maturity Level 2 requires that privileged access is restricted to those who need it, that privileged accounts are separated from standard user accounts, that privileged access is time-bound where possible, and that privileged activity is logged. For Microsoft 365 Copilot, the relevant administrative scopes are Global Administrator, Privileged Role Administrator, Copilot Administrator, SharePoint Administrator, Power Platform Administrator, and the new Copilot Studio Administrator role introduced with the Copilot Control System (Microsoft, 2026 release waves).

Privileged Identity Management (Microsoft Entra Privileged Identity Management) is the practical tooling for time-bound activation. The recommended Maturity Level 2 configuration makes every Copilot-related administrator role eligible by default rather than permanent. Activation requires multi-factor authentication and a documented justification, activation duration is capped at eight hours, and approval is required for the highest-risk roles. Customer Lockbox (Microsoft Purview Customer Lockbox) extends this principle to Microsoft engineer access during support cases. Every Copilot tenant should have Customer Lockbox enabled.

A common gap in Australian Maturity Level 2 assessments is the absence of a separate admin account for the person doing Copilot administration. The ASD Information Security Manual is explicit: privileged accounts must not be used for routine email, browsing, or productivity tasks. (cyber.gov.au — Information Security Manual (ISM), accessed 19 October 2026). A Copilot Administrator using a daily-driver account with email access and a Copilot licence is an Essential Eight finding.

Control 6 — Patch operating systems

Copilot does not directly alter this control, but it remains a Maturity Level 2 prerequisite. Detailed implementation guidance for Control 6, covering Windows Update for Business, Intune update rings, Expedited Updates, Linux unattended-upgrades, and audit evidence, is in the EDUC4TE technical guide for Essential Eight Control 6.

The Copilot-specific consideration at Control 6 is the Windows version requirement. Windows 10 reached end of support on 14 October 2025, so Windows 11 is now the supported baseline for Microsoft 365 Copilot devices, and the maturity model is explicit that unsupported operating systems are a Maturity Level 2 finding. Any device still running an unsupported Windows build with a Copilot licence assigned is a compound Essential Eight finding. It fails Control 6, and it raises questions over Control 7 (multi-factor authentication on an unpatched authentication stack).

Control 7 — Multi-factor authentication for Copilot endpoints

Maturity Level 2 requires multi-factor authentication for all users accessing internet-facing services that store sensitive customer or organisational data, and phishing-resistant multi-factor authentication for privileged users. Microsoft 365 Copilot is, by definition, an internet-facing service that accesses sensitive organisational data. Every Copilot user is therefore in scope.

The recommended Conditional Access policy set, drawn from the Microsoft Learn Conditional Access recommended policies (current revision) (learn.microsoft.com — Conditional Access overview, accessed 19 October 2026) and adapted for Copilot, has four parts. Require multi-factor authentication for all Copilot users. Require phishing-resistant methods (passkey, Windows Hello for Business, or FIDO2 security key) for the Copilot Administrator, SharePoint Administrator, and Global Administrator roles. Block legacy authentication. Require compliant or hybrid-joined devices for Copilot endpoints. The ASD Blueprint for Secure Cloud guidance on phishing-resistant authentication aligns directly with this set.

Credential compromise is routinely followed by rapid data exfiltration in cloud-tenant incidents, so password-only Copilot access in 2026 sits well outside the maturity model expectation.

Control 8 — Regular backups including Microsoft 365 Backup

Maturity Level 2 requires that backups of important information, software, and configuration settings are performed daily, retained for a defined period, and tested for restoration. Microsoft 365 has had granular point-in-time recovery for SharePoint, OneDrive, and Exchange for several years. Microsoft 365 Backup (Microsoft, general availability September 2024) added a first-party backup service for SharePoint sites, OneDrive accounts, and Exchange mailboxes, with administrator-defined retention policies and tested restoration paths.

For Copilot, the grounding data is also the data that needs to be recoverable: every SharePoint document, Teams message, and OneDrive file Copilot might surface. A ransomware encryption event that traverses SharePoint document libraries removes both the production content and the Copilot grounding corpus. Microsoft 365 Backup with daily retention and a documented restoration runbook is the Maturity Level 2 expectation for any Copilot deployment of consequence.

Practitioner note: third-party backup vendors (Veeam, AvePoint, Rubrik, Commvault) remain valid for Australian organisations under Maturity Level 2. The requirement is daily, retained, restorable backups, not specifically Microsoft 365 Backup. The choice between first-party and third-party is a procurement and recoverability-testing decision, not an Essential Eight one.

Where the ASD Blueprint for Secure Cloud sits in this mapping

The ASD Blueprint for Secure Cloud (Australian Signals Directorate, current revision, available at blueprint.asd.gov.au) is a configuration-pattern guide for Australian Government organisations operating Microsoft 365 workloads. It is not the Essential Eight Maturity Model, and it is not the Information Security Manual. It is a set of opinionated configurations that align with both. For Copilot, the relevant patterns are the Conditional Access policy set, the Privileged Identity Management configuration, the Purview Information Protection labels schema, and the Defender for Cloud Apps configuration.

Australian Government and Government-aligned organisations should treat the Blueprint as the recommended configuration baseline, the Essential Eight Maturity Model as the assessable control set, and the Information Security Manual as the authoritative control statement. Non-Government Australian organisations without an IRAP scope obligation can still use the Blueprint productively. It is the most concrete published configuration guide currently available.

The evidence pack — what an IRAP assessor will ask for

A common failure in Australian Maturity Level 2 self-assessments is the absence of consolidated evidence. The controls are in place; the documentation is not. When a qualified IRAP assessor reviews a Copilot deployment under the ASD Blueprint for Secure Cloud, the expected artefact is an IRAP-format evidence pack: one folder per Essential Eight control, each holding the policy document, a current configuration screenshot, the attestation date, the named control owner, and the next review date.

The EDUC4TE companion guide on the Essential Eight evidence pack IRAP-format checklist for Copilot scope walks through every folder, artefact, and attestation field. It is the operational complement to this mapping. Run the free EDUC4TE Copilot and Essential Eight Alignment audit to identify the highest-priority gaps, then assemble the evidence pack against the checklist. Across Australian tenants, an organisation already at Maturity Level 1 can typically reach a defensible Maturity Level 2 alignment for the Copilot scope in about four weeks.

Related guides

This mapping anchors the Copilot and Essential Eight cluster. Three companion guides take each strand further:

• Application control for Copilot Studio agents — the step-by-step configuration path for Control 1.
• Essential Eight evidence pack IRAP-format checklist for Copilot scope — the folder structure and artefacts an IRAP assessor expects.
• APP 8 Anthropic subprocessor disclosure template — the cross-border disclosure record required under the Privacy Act 1988 when Copilot routes to Anthropic.

Summary

Microsoft 365 Copilot does not move your Essential Eight maturity score on its own. But the configuration choices around it move six of the eight controls. Application control (Copilot Control System publishing gates), patch applications (Monthly Enterprise Channel and Edge), user application hardening (Office cloud policy and Edge for Business policies), restrict administrative privileges (Privileged Identity Management for Copilot scopes), multi-factor authentication (Conditional Access for Copilot endpoints), and regular backups (Microsoft 365 Backup coverage) are the levers Australian CISOs and IRAP assessors should focus on first.

The November 2023 ACSC Essential Eight Maturity Model revision, the ASD Blueprint for Secure Cloud and its Microsoft 365 Copilot configuration section, and the Microsoft Copilot Control System documentation together provide enough material to build a defensible Maturity Level 2 baseline. The remaining work is operational: the configuration, the documentation, the attestation, and the evidence pack. Run the audit, build the pack, and reassess every quarter.

Sources referenced in this article: ASD Essential Eight Maturity Model and Information Security Manual (cyber.gov.au); OAIC Notifiable Data Breaches scheme (oaic.gov.au); Microsoft Learn — Restricted Content Discovery, Restricted Access Control and Conditional Access overview; ASD Blueprint for Secure Cloud and its Microsoft 365 Copilot configuration section; Microsoft Copilot Control System documentation; IBM X-Force Threat Intelligence Index 2026.