Product guides

How to manage Microsoft 365 subscriptions in Contractpedia

Contractpedia Team

⏱ 4 min read • Updated 2026

Ask most IT managers how many Microsoft 365 licences their company is actually paying for, and the answer often starts with “let me check.” The subscription gets set up once, IT adds and removes users as the team changes, finance pays whatever the invoice says, and nobody circles back to confirm the two still match.

This guide covers why Microsoft 365 costs tend to creep up on their own, and walks through how to set the subscription up in Contractpedia so licence counts, pricing, and renewal dates live in one place instead of being split across IT, finance, and an admin portal nobody checks.

IN THIS ARTICLE:

Why Microsoft 365 costs creep up without anyone changing anything

A subscription that started with 22 people still gets billed for 22 seats after the team shrinks to 17 — nobody has to make a mistake for that to happen, it’s just what happens by default when no one’s job is to check.

Licences that outlive the person who needed them

Someone leaves, changes role, or switches tools, and their seat doesn’t get removed — it just keeps renewing. One unused licence looks trivial. A dozen of them, sitting there for a year, isn’t.

Auto-renewal locking in whatever’s current, not what you agreed to

If nobody owns the subscription, it renews on autopilot at today’s terms and today’s pricing — which may not be the terms you signed up for.

Price increases that land on the invoice first

Microsoft adjusts per-user pricing from time to time. Without anything tracking the subscription between renewals, the invoice is usually the first place you find out.

The cost living in three different places

IT has the licence count, finance has the invoice, and the signed agreement is filed somewhere neither of them can quickly find. Add it up and “what do we actually pay for M365 a year?” takes longer to answer than it should.

The licence check worth doing before your next renewal

  • How many licences are we paying for, and how many are actually assigned to active users?

  • When does the subscription renew, and what’s the notice period if we want to change or cancel?

  • Has the per-user price changed since we last checked?

  • Who is responsible for reviewing licence counts before the next renewal?

  • Could we produce the full annual Microsoft 365 cost right now, without pulling in IT and finance separately?


If any of these takes more than a minute to answer, that’s the gap to close before renewal — not after.

INSIGHT

Licence drift isn’t a planning failure — it’s what happens when reviewing licence counts isn’t anyone’s explicit job. The subscription doesn’t need to break for the cost to grow; it just needs nobody checking.

Setting up a Microsoft 365 subscription in Contractpedia

Here’s how to structure a Microsoft 365 subscription as a managed contract, so licence and price changes surface before renewal instead of on the invoice.

1. General information

Give the contract a clear name — “Microsoft 365 Subscription” is enough if it’s your only one. Select or add Microsoft as the counterparty, set the status to Active, and assign the category Software.

2. Assign a responsible person

This is the field that makes the reminders useful. Assign whoever actually manages the Microsoft relationship — usually IT or administration — and make sure their person record is linked to a Contractpedia user account so renewal to-dos reach them. Add the department and location while you’re there.

3. Dates and renewal settings

Set the start date, choose Fixed period as the expiration type, and enter the contract period (typically 12 months). Set the automatic renewal period to match your subscription, and enter the termination notice period from your agreement — the window before renewal in which you’d need to notify Microsoft to cancel or change it. This is what turns “we should check this sometime” into a reminder on an actual date.

4. Financial information

Select Expense as the contract type, then add a fee — something like “Subscription licences” — with the amount and how often it recurs. Update this figure whenever your licence count changes, and next year’s cost comparison becomes a real number instead of a guess. Tick Estimated value only if the amount genuinely fluctuates month to month.

5. Attach documents

Upload the subscription agreement and any related SLA documents, or link to where they’re stored. When a question comes up about what’s included, it’s one click away instead of a search through someone’s inbox.

6. Save and let the system run

Keep automatic to-do reminders enabled. Contractpedia generates renewal tasks and assigns them to the responsible person ahead of the renewal date — the nudge that catches unused licences and price changes before another year gets billed on autopilot.

What this gives you

Once your Microsoft 365 subscription is set up this way, one place shows the licence count, the real cost, the renewal date, and the agreement itself — instead of IT, finance, and a filed PDF each holding a piece of the picture separately.

For a full walkthrough with screenshots, the step-by-step guide is in the Contractpedia Support Center: 👉 Create a Microsoft 365 subscription in Contractpedia

Key takeaways

Contractpedia is a contract management platform that helps teams track contracts, catch renewals, and eliminate unnecessary spend.

Experience Contractpedia for yourself

Join teams who never miss a renewal again. No credit card required.