From 1 December, Microsoft plans to sell new Microsoft 365 Copilot and Microsoft 365 Copilot Business offers without a qualifying Microsoft 365 base subscription, at the same prices as the current offers. Until now, Copilot has been an add-on that needs an eligible base plan underneath it.
For buyers, this removes one of the main constraints on how Copilot is purchased. It also creates a new set of questions about what a user actually needs in order to use it. This article explains what is changing and what to check.
What is changing and when
Microsoft has been moving in stages. From 16 October, existing offers that require a base subscription were renamed with add-on in their names, and from 1 December the add-on offers reach end of sale in the CSP channel. The new standalone offers arrive on the same date.
There is also a change to billing. Microsoft had set 1 December for usage-based billing to become the default on new Copilot Business purchases through CSP, after an earlier date of 2 November. A partner reported on 5 November that Microsoft has since moved the default start to the period from January to March 2027. Dates have shifted more than once, so check the current position in Partner Center or with your reseller before you rely on any of them.
A standalone licence is not a standalone product
The key point is that the licence changes but the dependencies do not. Copilot features still depend on the Microsoft 365 apps and services each user is licensed for, so licence mapping still matters. A user who holds Copilot but not the services it draws on, such as mail, files or meetings, will not get the full experience.
That means the practical question changes from whether you can buy Copilot to whether each person has the right combination. It is worth mapping, user by user or role by role, which base services they hold today and which Copilot features depend on them.
What it means for how you buy
A standalone offer can simplify purchasing for organisations that hold a mixture of Microsoft and non-Microsoft productivity tools, or that want to give a few users Copilot without moving them to a different base plan. It may also change who you buy from and how it is billed, particularly if you move between direct and partner channels.
It should not change the discipline around adoption. Assigned and active are still different numbers, and the cost of an idle seat is the same whichever way the licence is bought. Start with the roles most likely to benefit, track use and reassign unused licences.
The metered side of Copilot
Copilot is increasingly a licence plus a meter. Microsoft said on 28 October that the number of Copilot customers consuming credits through usage-based billing grew more than 75 percent in the quarter. The default limit for Copilot Business usage billing is 4,000 credits per user per month, which at one cent a credit is up to 40 dollars per user per month before the limit stops further use. Administrators can change the limit down to a minimum of 2,000.
If you set a limit that is higher than you need, you have created an open-ended cost. Decide who needs the usage-based features, set limits before the billing starts and review consumption monthly.
Promotions and timing
Pricing offers add to the confusion. A Copilot Business promotion for organisations with 1 to 300 users, at 18 dollars rather than 21 dollars per user per month, runs to 31 December. If you are deciding between buying now and waiting for the new offers, compare the total cost over the term, not just the first price, and ask what happens to a promotional rate when the new offers replace the old.
What to ask your reseller or Microsoft
Ask whether the standalone offers apply to your agreement type, because the announcements are described mainly for the partner channel. Ask whether existing add-on seats can be converted, and at what price. Ask what the usage-based billing default will be for your purchases and from when. Ask how to set limits and who can change them. Ask what each user needs besides Copilot to use the features you are paying for.
Write down the answers and keep them with the order. With dates moving, a record of what you were told and when is useful at renewal.
An illustration of the metering risk
To see why limits matter, take an invented example. An organisation buys 150 Copilot Business seats at the list price of 21 dollars a month, which is 3,150 dollars. If usage-based billing is on with the default limit of 4,000 credits per user, the most those users could draw is 150 times 40 dollars, or 6,000 dollars a month. The cap is a ceiling, not a forecast, and most users will use far less. But it shows that the metered side can in theory exceed the licence cost, which is why the limit is worth setting deliberately.
A simple mapping exercise
Make a table with one row per role. For each, list the base services they use now, whether they need Copilot, and which Copilot features they would use. Mark where a user would hold Copilot without the services behind it. That table tells you whether the new standalone option fits your estate, and it becomes the basis for adoption tracking.
Conclusion
Microsoft is planning to sell Copilot without a base licence from 1 December, which loosens how it can be bought but does not remove the dependencies behind it. Billing dates have shifted and may shift again.
Map what each user needs, set usage limits before metering starts, check the current dates and keep your adoption review going. The licence is only part of the cost.
