Before rollout
Licences, prerequisites and the oversharing check
Three things to settle before you train anyone: whether your plan qualifies, whether the technical basics are in place, and whether people can open files they should not. Each claim about Microsoft’s requirements below links to Microsoft’s own page, because these details change.
1. Does your Microsoft 365 plan qualify?
Copilot is sold as an add-on to an eligible base licence; Microsoft lists the eligible plans on its licensing page (License options for Microsoft Copilot). At the time of writing, that list includes the Microsoft 365 Business Basic, Business Standard and Business Premium plans that most small and medium Australian businesses use, along with the enterprise E3 and E5 plans, Office 365 E1, E3 and E5, and several frontline and single-app plans.
For smaller organisations, Microsoft describes a Copilot Business add-on for organisations with up to 300 users on eligible Business licences, sold with an annual commitment (source). Larger organisations use the enterprise options. We do not quote Microsoft’s prices here because they vary by plan, term and reseller and they change; check with your licensing provider or Microsoft’s own pricing page on the day you buy.
Two practical points. First, you do not need to license everyone at once; a pilot group is normal and sensible. Second, Copilot Chat is available to users with an eligible subscription without the paid licence (source), so staff who are not in the pilot can still learn the habits.
2. The technical basics
Microsoft’s requirements page sets out what needs to be in place (Microsoft Copilot requirements). The ones that most often trip up smaller businesses:
- Work accounts in Microsoft Entra ID. Each user needs a proper work account, not a shared login.
- Exchange Online mailboxes for anything that uses email, calendar or meeting data. Copilot isn’t available in group mailboxes.
- OneDrive set up for users, because some features depend on it.
- Current Microsoft 365 desktop apps for the in-app features, plus supported versions of Outlook.
- Transcription or recording in Teams if you want meeting recaps after the meeting ends.
- Network access to Microsoft’s Copilot endpoints, including the cloud.microsoft domain. Firewalls or web filters that block it cause confusing failures.
Microsoft also offers a diagnostic that checks whether a particular user meets the licensing requirements (source). If you have an IT provider, these are usually quick for them to confirm.
3. The oversharing check
This is the step that matters most and is skipped most often. Copilot only shows people organisational data they already have at least view permission to (Microsoft, data and privacy). Microsoft itself recommends a secure and governed foundation before deployment and points to tools for finding and fixing oversharing (source). In plain terms: Copilot does not create new access, but it makes existing access far easier to use.
Where oversharing usually hides
Company-wide sharing
Files or folders shared with everyone in the organisation, often years ago, to save time. HR, finance and board material turns up here more often than anyone expects.
Old Teams and SharePoint sites
Sites created for a project, a merger or a restructure, set to public within the organisation, and never closed. Nobody remembers what was uploaded.
Sharing links
“Anyone with the link” and organisation-wide links in OneDrive that were sent once and never expire.
Personal folders used as shared drives
A manager’s OneDrive holding the team’s salary spreadsheet, shared widely because it was easier than setting up a proper site.
Guests and shared channels
External people added to Teams for a project. Microsoft notes that permissions given to people outside your organisation through shared channels matter too (source).
Unlabelled sensitive files
If you use sensitivity labels, Copilot honours the usage rights on encrypted content (source). If you don’t, the only protection is permissions.
A sensible order of work
- List the places that hold genuinely sensitive material: payroll, HR, board papers, client health or financial information, legal files.
- Check who can open each of those places today, and tighten anything broader than it needs to be.
- Run the oversharing test from the home page with a pilot user who has ordinary access, with their agreement.
- Decide what staff may and may not put into prompts, and write it down in a paragraph, not a policy manual.
- Only then switch on licences for the pilot group and run the training.
Larger organisations can use Microsoft Purview and SharePoint Advanced Management for this work; Microsoft describes both on its requirements page. A business with twenty staff can usually do it by hand with its administrator in an afternoon.
4. Privacy obligations don’t pause for AI
If your organisation is covered by the Privacy Act, the Office of the Australian Information Commissioner has published guidance on using commercially available AI products (OAIC guidance). It recommends, as best practice, not entering personal information, and particularly sensitive information, into publicly available generative AI tools, and it warns against a “set and forget” approach. That is a good reason to make sure staff use the work version of Copilot under your organisation’s account rather than a consumer chatbot on a personal login, and to include that distinction in training.
Microsoft states that prompts, responses and data accessed through Microsoft Graph aren’t used to train the foundation models used by Copilot (source). That is a statement about Microsoft’s service; it does not replace your own obligations about what your staff do with the output.