What this plan is for, and what it assumes
Microsoft has renamed the product to Microsoft Copilot, with Copilot Chat now called Microsoft Copilot Chat, and this plan applies under either name4. This plan suits a New Zealand business that has decided to license Microsoft 365 Copilot for a first group of people and wants a structured first week rather than a licence email and a hope. Microsoft's setup guidance recommends the same shape: run a pilot with a small group of users to test the deployment and gather feedback, then assign licences to a larger group and monitor usage1.
It assumes three things are already settled. You know which Copilot your organisation is buying; for businesses on Microsoft 365 Business Basic, Standard or Premium, that is often Microsoft 365 Copilot Business, which has the same capabilities as Microsoft 365 Copilot and supports up to 300 seats per tenant6. You have looked at who can open what in SharePoint and Teams, because Copilot only surfaces content each user already has permission to see7. And you have at least a draft AI usage policy. Your administrator or IT provider should finish the permissions clean-up and the policy draft first, so this plan starts the week after those are done.
Choosing the pilot group
Pick people, not job titles. The best first users have plenty of email, meetings and documents, are willing to try something and report honestly, and will be asked by colleagues how it went.
Aim for a mix. In a small business, five to ten people across two or three teams is enough to learn from. Include at least one manager, because Copilot's meeting and email features save the most effort for people who spend the day in Outlook and Teams, and because a manager who uses it signals that it is allowed.
- One or two heavy Outlook users, such as an office manager or account manager.
- Someone who runs or attends many Teams meetings.
- Someone who writes long documents: proposals, reports or procedures.
- Someone who lives in Excel.
- One sceptic. Their questions will improve your training.
The week before: admin checklist
Your IT provider or administrator should finish these before Monday. Most are in Microsoft's setup guidance, and none should surprise a competent Microsoft 365 partner1,4.
- Confirm each pilot user has an eligible Microsoft 365 licence, an Entra ID account, and a primary mailbox in Exchange Online. Copilot can also use content a user is permitted to access in archive, shared and delegate mailboxes, but it is not available in group mailboxes4.
- Make sure Microsoft 365 Apps are deployed and up to date, that each user has OneDrive, and that the Office Feature Updates task is allowed to run4.
- Turn on transcription or recording for Teams meetings if you want Copilot to work with meeting content after the meeting ends4.
- Check multifactor authentication is on for everyone and that unified audit logging is enabled in Microsoft Purview1.
- Assign the AI administrator role to the person who will manage Copilot, rather than using a global administrator account for routine settings2.
- Record your decisions on web search, file upload and AI model providers in the AI usage policy.
- Book a short session for the pilot group on Monday morning and a review meeting on Friday afternoon.
Monday: switch on and set expectations
Assign licences early in the day. Microsoft sends each user a welcome email when a Microsoft 365 Copilot licence is assigned, with a link to Copilot help and learning3. Administrators can also schedule an organisational message from the Set up Microsoft 365 Copilot page in the Microsoft 365 admin center, which appears inside Teams3. Some app features can take a while to appear after assignment, so do not schedule the kickoff for five minutes after the licences go on.
Run a kickoff of about an hour. Show where Copilot lives in Outlook, Teams, Word, Excel and PowerPoint, and in the Microsoft 365 Copilot app. Walk through the AI usage policy in plain words, especially what information people should not enter. Then have each person ask Copilot one question about their own work, such as what they missed in a particular Teams channel last week, and read the answer and its citations together.
Finish by agreeing the rules for the week: everyone tries the daily task, everyone keeps a short note of what worked and what did not, and nobody sends Copilot output to a customer without reading it first. Microsoft states plainly that generated responses are not guaranteed to be 100% factual7.
Tuesday: Outlook and Teams
Start with the apps where people spend most of their time. The goal for the day is two small wins per person.
- Summarise the longest email thread in your inbox, then ask Copilot what is still unanswered.
- Draft a reply to a routine request and adjust the tone before sending.
- In a Teams meeting with transcription on, ask Copilot for the decisions and actions at the end, and check them against your own notes.
- Ask Copilot in Teams to catch you up on a busy chat you have muted.
Wednesday: Word and PowerPoint from your own files
This is the day people see the difference between Copilot and a generic chatbot, because the licensed product can draw on the documents they already have access to7.
Ask each person to take a real document due this month. In Word, they reference an existing file and ask for a first draft of a new one: a client proposal built from last year's proposal and this year's brief, or a procedure rewritten from meeting notes. In PowerPoint, they create a short deck from a Word document and then fix the structure themselves. Ask them to note how much of the draft they kept, because that is a more honest measure than any feeling of speed.
Thursday: Excel and the shared prompt list
Excel work needs the most checking, so give it a full day. Have people work on a copy of a real table, ask Copilot to explain a formula, add a calculated column, or build a PivotTable and chart, and then verify one result by hand.
In the afternoon, start a shared prompt list. Prompt Gallery, inside Microsoft 365 Copilot and Copilot Chat, lets users save prompts and share them with their team11. Ask each pilot user to save the two prompts that worked best for them this week and share them with the group. This list becomes the core of training for the next group.
Friday: review and decide
Hold the review meeting with the whole pilot group. Go around the room: one task where Copilot clearly helped, one where it failed or needed heavy correction, and one question about the policy. Write the answers down.
Do not expect the usage report to tell the story yet. The Microsoft 365 Copilot usage report, under Reports then Usage in the Microsoft 365 admin center, typically shows a day's activity within 48 hours of that day ending5. Use it the following week to compare enabled users with active users, alongside what people told you on Friday.
Close with three decisions: which scenarios to standardise and teach, whether any settings or policy wording need changing, and who joins the next group. Microsoft's setup guidance treats the pilot as the step where you test the deployment and gather feedback before assigning licences to a larger group1.
Looking after people during the change
A Copilot rollout changes how people do parts of their job. WorkSafe lists poorly managed organisational change among the psychosocial hazards a business should manage8. The fix is ordinary good management: tell people what is happening and why, give them time to practise, and make it safe to say the tool is not helping.
If the rollout will change roles or workloads, good faith means giving staff relevant information about proposals for change and a chance to comment before final decisions, and where a decision is likely to adversely affect someone's continued employment, you must give them information and a chance to comment before you decide9. Be explicit that the pilot is about learning the tool, not measuring individuals. The Privacy Commissioner also expects a human to review AI outputs before acting on them, which is one more reason to keep people firmly in charge of what gets sent10.
A worked example: a Palmerston North freight company
Picture a generic freight and logistics company in Palmerston North with an office team, dispatchers and a few account managers. The owner licenses Copilot Business for eight people: two dispatchers, three account managers, the office manager, the operations manager and the owner.
On Tuesday the dispatchers find their best use straight away: summarising long email chains about delayed consignments and drafting customer updates. On Wednesday the account managers build a tender response from previous responses stored in SharePoint, but discover two old tender files in a site the whole company can open; the office manager fixes the permissions that afternoon. Thursday's Excel session shows that Copilot can explain the fuel surcharge spreadsheet, but one generated formula is wrong, which becomes the week's most useful lesson on checking.
At Friday's review the group keeps six shared prompts, asks for a clearer policy line on customer addresses, and agrees the warehouse supervisors join next. The operations manager books a follow-up session two weeks later to look at the usage report alongside the team's notes.