Observation
Microsoft is pushing its Copilot artificial intelligence (AI) heavily into enterprise agreement (EA) renewals, in some cases offering to retain clients’ volume-level discounts if they take on a minimum Copilot commitment (generally around 200 or 300 users). However, when the organisation’s EA contract renews in three years, this discount will disappear, and the organisation will face the full price for both the 365 environment and the new Copilot licenses. Microsoft is positioning the above offering as a way for organisations to perform a PoC of the Copilot prompt-based AI assistant.
However, the way Copilot for Microsoft 365 is licensed is diametrically opposed to running a PoC. To understand why, we must:
- Understand the Product: The edition of Copilot being promoted, versus the many other Copilot-labelled products Microsoft has.
- Understand the Licensing: The inclusions and limitations of the Copilot licence.
- Map Licensing to PoC Traits: How the Copilot licensing terms impact the key traits of a PoC.
- Reframing Deployment: Reframe what we mean by a PoC if going ahead with an initial Copilot deployment program.
Understand the Product
Microsoft is using the label Copilot liberally across its product portfolio, renaming existing products, adding it to new features within existing products, and including it in genuinely new AI products and services. While this is consistent with Microsoft’s push to become the dominant AI everywhere vendor, it is creating confusion within the marketplace. For example, in January 2026, Microsoft changed the names of its personal, family, and small-business versions of its office suite from Microsoft 365 (Office) to Microsoft 365 Copilot App…, which does not include Copilot Pro, which most consumers assume is the Copilot product. The Copilot rebranding is causing a lot of confusion.
The confusion extends to people involved in licensing or deploying enterprise Copilot. In many instances, they will be working with influential internal stakeholders who have experience with one version of Copilot (for example, the free Copilot Chat version included in the Office productivity suite, or previous Copilot Pro). These users will have misconceptions and false expectations about the Copilot service being deployed at an enterprise level.
Copilot, Copilot, Copilot… Co… Confusion: Understanding Microsoft’s Rapidly Changing Copilot Products provides a full breakdown of the different Copilot offerings within the office ecosystem.
A common misconception is that the Copilot Chat services baked into Microsoft 365 (aka Office tools) are the same as the Microsoft 365 Copilot service being discussed for enterprise deployment. This misconception can be quickly resolved with a demonstration.
For enterprises with Microsoft 365 (E3, E5, A3, A5, etc.) licenses, the only practical option will be to procure Microsoft 365 Copilot licenses. The new E7 licensing bundle includes Copilot 365 and Agents. This is Microsoft’s flagship product, with deep integration with Word, Excel, PowerPoint, Outlook, Teams, OneNote, Loop, SharePoint, and, importantly, full Microsoft Graph grounding. This means that emails, meetings, files, chats, and so on are available to the Copilot AI while adhering to existing data leakage prevention and document access controls. Microsoft now also bundles Copilot for Sales, Copilot for Service, and Copilot for Finance under a single SKU, increasing functionality without raising costs, reflecting Microsoft’s late-2025 shift toward unified AI value delivery.
The commercial offer is currently priced at AU$44.90 per user/month (annual commitment) and is available for purchase through Cloud Solution Provider (CSP) partners.
However, an annual commitment is required, and licenses are associated with named users. Licenses cannot be reallocated until a 90-day grace period of non-use has expired. No trial available.
Understand the Licence
Microsoft 365 Copilot can be purchased via:
- The EA: Organisations can add it as an add-on SKU through their Microsoft account team or partner. However, EA additions require an annual commitment that aligns with your agreement’s anniversary.
- Direct Purchase (M365 Admin Centre): You can buy them directly using a credit card within your existing tenancy. While Microsoft previously offered only annual commitments, it now offers monthly billing for annual terms and, in some regions, a month-to-month monthly commitment (usually at a ~20 per cent price premium). This option is rarely used, but for a genuine trial, it is the most workable in the short term.
- Cloud Solution Provider (CSP): This is often the best route for a PoC, but creates downstream licensing complexity and remediation work prior to the next EA renewal, as well as complex user management. Organisations can work with a partner to purchase a limited number of licenses on a monthly basis. This allows you to scale down or cancel the licenses entirely at the end of the month without being locked into a full year.
Decommissioning Licenses
Decommission rights for Microsoft 365 Copilot depend on the commitment terms agreed to when licensing:
- Annual Commitment: If purchased through an EA or a standard yearly direct/CSP plan, you are financially committed to the seats for 12 months. You can unassign them from users, but you will still be billed for the seats.
- Monthly Commitment (CSP/Direct): If you specifically select the month-to-month option, you can cancel or reduce the seat count at the end of any month once the PoC is complete.
Microsoft’s standard licensing terms for user subscription licenses (including Copilot) include a 90-day reassignment rule.
- The Rule: Once you assign a Copilot license to a user, organisations are not allowed to reassign it to another user for 90 days after its last usage. While the M365 Admin Centre may technically allow you to unassign and reassign a license within 90 days, doing so for a rotation (e. g., giving it to User A for two weeks, then to User B) is a violation of the licensing terms and will be used as an out-of-compliance issue when renegotiating licensing numbers.
Map Licensing to PoC Traits
To run an effective PoC, organisations need to balance scientific rigour and measurement with operational agility. However, Microsoft’s enterprise licensing is designed for stability and scale (arguably for Microsoft), which creates friction against the natural needs of a trial.
Here are the four key traits of a successful PoC and how the licensing constraints work against them:
High Velocity & Iteration (Agility)
The Trait: A PoC should be fast. It should test a hypothesis, gather feedback, and pivot if necessary. Ideally, a limited group of users (say 20–40) would be rotated every 3–4 weeks across different departments (e. g., HR for a month, then finance, then legal) to identify where the highest return on investment (ROI) lies.
The Friction: The 90-Day Reassignment Rule. Microsoft’s terms restrict reallocation of a license more than once every 90 days after the last use. This means a PoC can iterate, at most, 2 times in a year – and in practical terms, only once. This kills the rotation strategy for a PoC. The Copilot PoCs cannot fail fast with one group and immediately swap to another cohort.
Representative Sampling (Breadth)
The Trait: To get a true proof, in a PoC, organisations must test across diverse personas: the power user, the sceptic, the nomad, and between different job functions.
The Friction: Because of the 90-day rule and the increased cost, organisations are effectively encouraged to limit the number of personas (users) Copilot will be provided to. For example, if an organisation limits Microsoft 365 Copilot to 20 users out of a workforce of 500, they are trialling just 4 per cent of their workforce. If those 20 users happen to be AI-resistant (due to natural inclination or lack of training and digital maturity, as discussed in Reframing the Copilot ROI Problem) or work in roles where Copilot’s use case may be (such as heavy Excel data modelling, which is still evolving), the PoC will fail simply due to a poor sample size and inability to pivot.
Low Financial Risk (Cost Efficiency)
The Trait: A PoC should be a sunk cost you are willing to lose. You want the ability to walk away if the value isn’t there without being tethered to a long-term bill.
The Friction: EA add-ons or standard direct-purchase seats are annual commitments. If the planned PoC concludes in 60 days and Copilot isn’t ready for your specific workflow, organisations remain legally and financially obligated to pay for these seats for the remaining 10 months of the year. This creates lock-in before the value has been proven.
Real-World Environmental Testing
The Trait: The PoC must happen in your actual production environment with real corporate data (emails, chats, and files) to see if Copilot can actually find and summarise relevant information and, most importantly, to confirm that the existing information governance confirmation of the Microsoft ecosystem is sufficiently robust to ensure safe AI usage.
The Friction: Copilot is not a sandbox tool. It requires being on in your main production tenancy to work effectively. Because it lives in your production tenant, organisations cannot segregate it from the greater environment. If a user in the PoC accidentally overshares sensitive data because Copilot found a file they shouldn’t have had access to (but technically did), it creates a security headache that can derail the PoC.
Overcoming the Copilot PoC Problem
Rather than positioning the initial Copilot deployment as a PoC, frame it as the first phase of a committed, ongoing innovation program. The essential step is to establish a formal ideation process for the use of Copilot (and other AI services) so that ideas for the application of the AI tools are formally gathered, potential benefits and ROI identified for each, the workflows and change management executives are involved, the execution and results are measured, and fed back into the ideation cycle.
This means that Copilot is implemented as a persistent technology platform on which the organisation can continually refine and reflect on digital processes and work activities. It is a locked-in, ongoing business-as-usual (BAU) cost that needs to be continually explored for new uses and value extraction.
The key difference between viewing Copilot as a platform and other core platforms, such as enterprise resource planning (ERP) solutions, is that the use cases, benefits, and ROI cannot be fully mapped in advance of the deployment, and so an ongoing program of work is put in place to find and extract the benefits. It is a leap of faith.
Another key difference is that, unlike ERP platforms, Copilot can be deployed incrementally, slowly, and carefully to different users. This is where the idea of a PoC can be collapsed into the deployment model. Reframe the PoC in each phase of the deployment. Use the ideation framework to identify the most likely areas where Copilot will have a positive impact, provide a digital and AI literacy maturity uplift for users, and deploy to that specific cohort. Measure the benefits, refine the workflows and training as needed, and only once that cohort is showing positive returns, move on to the next phase and next cohort.
Next Steps
- Review the constraints on Microsoft 365 Copilot due to licensing terms. Consider these contents when planning the Copilot deployment.
- Develop a formal ideation (a. k.a innovation) program for Copilot, Microsoft 365 features and AI in general. Use this to identify the most likely successful use cases and staff cohorts for initial deployment, then use it to guide the gradual deployment of Copilot with a phased approach.
- Communicate the notion that Copilot is a platform for continual workplace innovations, and that the product itself will see rapid changes in terms of features, power, and cost over the next few years. The only constant with Copilot is change.
