Copilot in 30 launched on August 1, 2026. It provides a twenty-five user, thirty-day Microsoft 365 Copilot Business trial for organizations under three hundred employees, packaged with adoption resources and partner guidance.
The design is better than most vendor trials, and the reason is arithmetic. Twenty-five users is above the threshold where individual enthusiasm dominates the result. Thirty days is longer than the honeymoon. Every Copilot deployment we have observed follows the same curve — high engagement in week one driven by novelty, a sharp decline in weeks two and three as the novelty exhausts and the genuinely useful patterns have not yet formed, and a plateau in week four that predicts long-run usage reasonably well. A fourteen-day trial measures the honeymoon. A thirty-day trial measures the plateau.
How to waste it
The default failure mode is straightforward: assign twenty-five licences to whoever asks, send an announcement, and check the usage dashboard on day thirty. This produces a number that reflects the personal curiosity of a self-selected group and tells you nothing about whether Copilot creates value in your organization's actual work.
Three things make the difference.
Choose participants by workflow, not by enthusiasm
Select users whose work you can describe as a repeated process with a measurable output. A finance analyst who produces the same monthly reporting pack. A sales lead who writes the same category of proposal. An operations manager who summarises the same weekly data. Someone in HR who handles a recurring category of query. The point is not that these roles are more deserving; it is that they produce a before-and-after you can actually compare.
Include at least a few sceptics. A trial staffed entirely by volunteers produces an unrepresentative result and, worse, an unfalsifiable one. The sceptic who finds a use case is the strongest evidence you will generate.
Define the measurement before day one
Decide what you are measuring and how, before the licences are assigned. Time to complete a specific recurring task is the strongest measure and requires a baseline captured in advance. Weekly active use per participant is the minimum. Qualitative capture matters too: a short structured check-in at the end of weeks one, two and four surfaces the specific prompts and workflows that worked, which is the material you need for a broader rollout.
Copilot Chat Analytics, which arrives in the suites during the 2026 packaging rollout, gives tenant-level visibility that makes this materially easier than it was.
Fix the data problem first, or measure it
Copilot's answers are only as good as what it can see, and in most organizations what it can see is a mixture of authoritative documents, superseded drafts, and content it should arguably not surface at all. A trial run against an unreviewed SharePoint estate will produce wrong answers, and users who receive a wrong answer in week one rarely return in week three.
You do not need to solve information architecture before a trial. You do need to know whether a bad answer was a Copilot limitation or a data limitation, because those lead to entirely different decisions. Pick the sites and libraries the trial participants actually work in, review them for currency and oversharing, and scope the trial around them.
What a good result looks like
A useful thirty-day outcome is not "everyone loved it." It is a short list of specific, named workflows where a measured time saving occurred, attached to the roles that perform them, plus an honest account of where it did not help. That artefact converts directly into a rollout plan and a business case with a denominator. "Sixty percent of participants used it weekly" without that detail converts into nothing.
If the trial converts, the commercial landing zone is now permanent rather than promotional: Microsoft 365 Business Standard with Copilot at 23.50 USD and Business Premium with Copilot at 32.00 USD, both generally available since July 1 with a three hundred licence maximum, plus FY27 promotions of fifteen to thirty percent on SMB commitments.
How Lorexus engages
We select the participant cohort against real workflows, capture baselines before the trial starts, review the data estate the trial will run against, and produce the measured result. The output is a rollout decision with evidence behind it. Book a free 15-minute call with our senior engineers.