·9 min read

Microsoft 365 Copilot Readiness Checklist for Australian Businesses

A 12-point checklist for Australian businesses: licensing, SharePoint oversharing, sensitivity labels, identity, a six-week pilot and an AI usage policy.

Microsoft 365 Copilot is the easiest AI tool for an Australian business to switch on and one of the easiest to get wrong. The licence takes minutes to assign. The preparation that stops it from surfacing payroll spreadsheets, board papers and HR files to the wrong people takes weeks. This checklist covers what to do before you buy licences, how to pilot, and how to tell whether it paid off. Nublock does this work as part of managed Microsoft 365, so the permission, identity and policy fixes are handled by the team that already looks after your tenant.

What Copilot Actually Does

Microsoft 365 Copilot is a large language model connected to your tenant through Microsoft Graph. It reads what the signed-in user can read across email, calendar, Teams, OneDrive and SharePoint, and writes back into the Office apps:

  • Word — Draft a document from a prompt and reference files, rewrite a section, or summarise a 40-page report into a page.
  • Outlook — Summarise a long thread, draft a reply in your voice, pull out the actions you have been asked to do.
  • Teams — Recap a meeting you missed, including what was agreed, and answer questions about the transcript.
  • Excel — Ask questions about a table in plain English, add formula columns, highlight outliers. It works best on clean data in a formatted table.
  • Copilot Chat — Works across all of your Microsoft 365 content at once. Ask what the latest version of a contract says or what was decided about a project last month.

The useful part is the last one. So is the dangerous part: it is the first time most staff have had a tool that reads every file they technically have access to and summarises it.

Licensing Prerequisites

Copilot is an add-on licence that needs an eligible base licence underneath it. For most small businesses that is Microsoft 365 Business Standard or Business Premium; for larger organisations it is Microsoft 365 E3 or E5. You do not need an enterprise plan. Under 300 seats, Business Premium is usually the better choice because it already includes Intune, Defender for Business and the Purview features used for labels and DLP.

A few points that trip people up:

  • Copilot licences are per user and usually sold on an annual commitment. Buy them for the pilot group first, not the whole company.
  • Users need the current Microsoft 365 Apps, not a perpetual Office 2019 or 2021 install.
  • Users on Exchange Online, OneDrive and SharePoint get the full experience. Mailboxes still on an on-premises Exchange server do not.
  • The free Copilot Chat that comes with a Microsoft account is a different product. It does not read tenant data and should be covered separately in your AI usage policy.

The Oversharing Problem

This is the issue that determines whether a Copilot rollout is safe. Copilot respects permissions and does not elevate access, but it makes existing over-permissioning visible, and almost every tenant has some. The usual causes:

  • A SharePoint site created years ago for a project, with the whole company as members, that now holds finance or HR files.
  • Sharing links set to Everyone except external users, which effectively means every employee.
  • OneDrive files shared with "People in your organisation" to get around a permissions problem on a deadline.
  • Public Teams, which make every file in them discoverable by every staff member.

None of this is a Copilot flaw. Before Copilot, nobody found those files because nobody went looking. With Copilot, "what is the salary range for a senior engineer" returns an answer with a citation to the spreadsheet.

How to Find It

Work through these in order:

  1. Run a SharePoint permission review. The SharePoint admin centre and Purview report on sites with many members, sites shared with everyone, and most-accessed files. Start with finance, HR, executive and legal.
  2. Search for "Everyone except external users". Any site, library or file where this group has read access should be reviewed. Most should be replaced with specific groups.
  3. Review public Teams. Decide which ones should be private and change them.
  4. Tighten the default sharing link. Change the tenant default from "People in your organisation" to "Specific people" so new oversharing stops.
  5. Use Restricted SharePoint Search as a stopgap. This limits Copilot and organisation-wide search to an approved list of sites while you fix the rest. It is a temporary control that also limits Copilot's usefulness. Use it to start a pilot safely, then switch it off once the review is complete.

Sensitivity Labels and DLP

Once permissions are reasonable, labels and data loss prevention add a second layer. Sensitivity labels classify content (Public, Internal, Confidential, Highly Confidential) and can encrypt files so only specific people can open them however widely they are shared. Copilot honours labels: if a user cannot open an encrypted file, Copilot cannot read it on their behalf, and Copilot output drawn from a labelled file inherits that label.

Data loss prevention policies watch for sensitive information such as tax file numbers, bank details, Medicare numbers and card numbers, and can block or warn when it is shared outside the business. Purview also supports DLP policies for Copilot prompts and responses, so a user who pastes customer records into a prompt can be warned or blocked.

You do not need a perfect classification scheme before Copilot. You do need three or four labels that staff understand, auto-labelling for the obvious cases (finance, HR and board sites get Confidential by default), and one DLP policy covering Australian financial and identity data, run in audit mode first and then enforced.

Identity Hygiene

Copilot makes a compromised account much more valuable. An attacker in a mailbox today can read email. With Copilot they can ask it to summarise every contract and find the document with the bank account details. Identity controls that were already important become essential:

  • Multi-factor authentication enforced for every user, with no exceptions for executives or shared mailboxes.
  • Conditional Access policies that block legacy authentication, require managed devices for access to company data, and challenge sign-ins from unexpected locations.
  • Stale account cleanup. Disable accounts for people who have left, strip licences from service accounts, and review guests. A former employee's account that was never disabled is a Copilot user if it still has a licence and a valid password.
  • Privileged access review. Global Administrator should be a handful of people with separate admin accounts and no Copilot licence.

These controls line up with the ACSC Essential Eight, particularly MFA and restricting administrative privileges. If you are already working towards Essential Eight maturity through a managed security program, most of this will be done or close to it.

A Pilot Approach

Do not roll Copilot out to everyone at once. Run a pilot of 10 to 20 users for six weeks, after the permission and identity work is done.

Choosing the Group

Pick people who do a lot of reading, writing and meetings, and who will say when something does not work. Include someone from operations, sales or client-facing work, finance or admin, and at least one manager. Avoid a group made up only of IT staff or only of executives.

Measurable Tasks

Before the pilot starts, each participant writes down three to five recurring tasks and how long they take today: the weekly client update, meeting prep, summarising a tender, the monthly reporting pack. During the pilot they do those tasks with Copilot and record the time and whether the output needed rework. This gives you numbers instead of impressions.

The Six Weeks

  1. Week 1 — Licences assigned, 60-minute training session, prompts guide issued, baseline times recorded.
  2. Weeks 2 to 5 — Normal work with Copilot and a 20-minute weekly check-in on what worked, what did not, and any files Copilot surfaced that someone did not expect to see.
  3. Week 6 — Compare task times to baseline, run a short survey, review audit logs for prompt volume and DLP events, and decide whether to expand, pause or stop.

An AI Usage Policy

Copilot should be covered by a short written AI usage policy that staff have read: which AI tools are approved, what must never go into an unapproved tool, that a person checks AI output before it goes to a client or drives a decision, when AI use must be disclosed, and what happens if the policy is broken. Our guide to AI adoption and governance for Australian businesses covers the policy in more detail.

Two Copilot-specific points worth adding:

  • Participants must be told when a meeting is recorded and transcribed. Set a standard for client meetings and who can access the transcript.
  • If Copilot surfaces a file a user believes they should not see, they report it to IT rather than reading it. Treat it as a permissions bug, not a disciplinary matter.

Training and Adoption

Most unused Copilot licences are unused because nobody showed the person what to do on day one. Training should be short, practical and based on the tasks that group actually does; a prompts guide with ten examples from your own business does more than a generic video. Nominate one or two champions who collect good prompts, and run a 30-minute session each month for the first quarter to share them.

Expect a dip while staff learn what Copilot is bad at: anything not written down in the tenant, and arithmetic across several documents. Usage usually settles into a few high-value tasks per person.

Measuring Whether It Paid Off

Copilot is a per-user annual cost, so the question is whether each licensed person saves enough time or produces better work to justify it. Measure three things:

  • Time on the baseline tasks — The pilot numbers compared to the starting point.
  • Usage — The Microsoft 365 admin centre reports active Copilot users per app. A licence used less than a few times a week is a candidate to reassign.
  • Quality and risk — Rework rate on AI-drafted content, DLP events, and permissions findings.

After the pilot, extend licences to roles like the pilot users who saw the strongest results, and hold off where the pilot showed little change. Many businesses end up licensing only the roles where the gain was clear.

The Copilot Readiness Checklist

Tick each item before you buy licences for the full company.

  1. Every intended user has an eligible base licence (Business Standard, Business Premium, E3 or E5) and the current Microsoft 365 Apps installed.
  2. Mailboxes and files for pilot users are in Exchange Online, OneDrive and SharePoint, not on-premises.
  3. Finance, HR, executive and legal SharePoint sites have had a permission review and the findings fixed.
  4. "Everyone except external users" has been removed from any site or library holding sensitive content.
  5. Public Teams have been reviewed and the sensitive ones made private.
  6. The tenant default sharing link has been changed to "Specific people".
  7. Sensitivity labels exist, staff have been told when to use them, and auto-labelling covers the obvious sites.
  8. At least one DLP policy covers Australian financial and identity data and has been tested in audit mode.
  9. MFA is enforced for every user and Conditional Access blocks legacy authentication.
  10. Stale user, guest and service accounts have been disabled and admin accounts are separate from daily accounts.
  11. An AI usage policy has been published and acknowledged, including meeting recording and the "report, don't read" rule for unexpected files.
  12. A six-week pilot with 10 to 20 users, written baseline tasks and a go or no-go decision at the end has been planned.

Where Nublock Fits

Most of this checklist is Microsoft 365 administration, identity and security configuration rather than AI work, which is what a managed service provider does every day. Nublock is an MSP that also runs AI, so permissions, labels, DLP, Conditional Access and Copilot governance are handled inside the managed IT agreement rather than by a separate consultancy that hands you a report and leaves. To plan a pilot, talk to an AI consultant in Melbourne at Nublock; we scope a fixed fee after a short discovery call.

What do I need before rolling out Microsoft 365 Copilot?

You need an eligible Microsoft 365 base licence plus the Copilot add-on licence for each user, a SharePoint and OneDrive permission review so Copilot cannot surface files that were shared too widely, sensitivity labels and data loss prevention policies on your most sensitive content, multi-factor authentication and Conditional Access enforced for every account, a written AI usage policy, and a small pilot group with measurable tasks. Most Australian small and mid-sized businesses can get through this in four to eight weeks if the Microsoft 365 tenant is already reasonably well managed.

Can Copilot see files it should not?

Copilot does not bypass permissions. It can only surface content the signed-in user already has permission to open. The problem is that most tenants have far more oversharing than anyone realises: files shared with Everyone except external users, old Teams sites that were never locked down, and OneDrive links shared with the whole company. Before Copilot, nobody found those files because nobody searched for them. Copilot finds them in seconds. Fixing the permissions before rollout is the single most important readiness task.

Do we need Microsoft 365 E3 or E5 for Copilot?

No. Microsoft 365 Copilot is an add-on licence that sits on top of an eligible base licence. For small businesses that base is usually Microsoft 365 Business Standard or Business Premium. For larger organisations it is E3 or E5. You do not need to move from Business Premium to E3 just for Copilot. Business Premium is often the better fit for businesses under 300 users because it already includes Intune, Defender for Business and the Purview features you need for labels and DLP.

How long does a Copilot pilot take?

Plan for six weeks with 10 to 20 users. Week one is onboarding and training, weeks two to five are normal work with Copilot plus a short weekly check-in, and week six is measurement and a go or no-go decision. Shorter pilots do not give people enough time to build habits, and pilots without defined tasks produce opinions rather than evidence. The pilot should start after the permission review and identity fixes are done, not before.

Is Microsoft 365 Copilot safe for Australian businesses under the Privacy Act?

Copilot can be used in a way that is consistent with the Privacy Act 1988, but the licence alone does not make you compliant. Your prompts and the content Copilot retrieves stay within your Microsoft 365 tenant and are not used to train the foundation models. What matters is how your business handles personal information inside the tenant: who can access it, whether it is labelled, whether DLP stops it leaving, and whether staff know what they are allowed to do. The 2024 Privacy Act reforms raised expectations around transparency and automated decision-making, so document how Copilot is used and keep a human responsible for any decision that affects an individual.