Annual or month-to-month: the New Commerce term is a 20 percent decision
Under Microsoft New Commerce, the same Microsoft 365 seat costs about 20 percent more on a month-to-month term than on the annual term. The term you pick is a pricing decision on its own, before any tier change.
The commitment term is the pricing lever most buyers never actively pull. Under Microsoft New Commerce, a month-to-month term costs about 20 percent more than the annual term for the same seat. That is a standing decision worth making on purpose, because the default is usually the expensive one.
Last verified: 2026-08-03.
The number
Month-to-month is about 20 percent above annual. Read the other way, moving from month-to-month to an annual commitment removes about 16.7 percent of the bill (0.20 divided by 1.20). On a right-sized estate that is the single largest procurement saving available without touching a single tier or seat.
# Decision rule
if headcount is stable for 12 months:
prefer annual commitment # ~16.7% off the month-to-month bill
else if headcount is seasonal/shrinking:
keep month-to-month on the volatile portion, annual on the stable core
Recommendation
Split the estate. Put the stable core headcount on an annual commitment and keep only the genuinely volatile portion on month-to-month. Decide the term before the tier, because the term saving is certain arithmetic while a tier downgrade needs a capability review. The ITSailor procurement service handles the split at /services/cloud-licensing-and-procurement.
Trade-offs
An annual commitment locks the seat count for the term, so it trades flexibility for the lower rate. Overcommit and you pay for seats you cannot release inside the term. Undercommit and you leave the 16.7 percent on the table. The split above is the middle path, sized to the part of the headcount you can actually forecast.
Where this does not apply
This does not apply to a tenant already fully on annual terms, where there is no premium left to remove. It also stops applying to add-ons and metered services that price differently from per-seat subscriptions. The 20 percent figure is the New Commerce structure, not a specific vendor quote, so confirm the exact rate on the CSP price list before you commit.
Tenant Monitor's monthly licence read is where this term decision gets checked against the actual seat list rather than against a renewal estimate, from Tenant Monitor.
Sources and further reading
Turn the trade-off into a scoped brief.
Share the constraints that differ in your environment. Michal will identify the next check needed before a delivery decision.
Start a scoped briefMore from Ops Log
The Azure role called Cost Management Reader is not read-only
Cost Management Reader is described as able to view cost data, yet its action list carries a Microsoft.Support wildcard that includes creating and updating support tickets. The built-in Reader role matches it on every Cost Management feature and cannot write a ticket.
A Microsoft 365 DKIM CNAME target has two documented formats: read it per domain, never build it
Microsoft documents two DKIM CNAME target formats for Microsoft 365 custom domains, one ending in onmicrosoft.com and one in dkim.mail.microsoft. The page splits them by new versus existing custom domain and never mentions tenant age. Read each domain's values with Get-DkimSigningConfig.
A CSP partner may not sell to itself or an affiliate: Microsoft names two own-use routes instead
Microsoft's CSP documentation says partners are barred by contract from selling Microsoft or third-party offers to themselves or an affiliate as end customer. The same page names two own-use routes: a Shared Services tenant for Azure, or a separate tenant bought through another CSP partner.