Microsoft NCE Seats After a User Leaves: Who Pays for the Rest of the Term

Who pays for the seat after a user leaves

Microsoft answers the money question directly. Under the heading on cancellations due to insolvency, the cancellation policy says: “The partner is responsible for payment of any outstanding amounts regardless of whether the customer can’t pay or refuses to pay for the subscription due to dissolution of the business relationship, bankruptcy, commercial disagreement with the partner, or other reasons not directly related to Microsoft’s ability to provide the services.” For a customer at risk of default, it suggests a monthly term subscription that can be canceled at the end of any month, or not selling to that customer.

Suspending the subscription does not stop the bill. Microsoft’s page on subscription lifecycle states says that “Partners continue to be billed when a subscription is suspended,” and the subscription-management page adds that suspending a new commerce subscription turns off autorenew.

So between Microsoft and the managed IT firm, the firm pays for the full term. Between the firm and its client, the client agreement decides. If it says the client pays for licenses through the end of their committed term, the seat is a pass-through cost and only the timing hurts. If it says the client pays per active user, or says nothing, the firm keeps paying Microsoft for a seat the client has stopped paying for — a Payment → Margin leak that no invoice shows, because the missing revenue was never billed in the first place.

How to count stranded seats from last quarter’s departures

The count needs three sources the firm already has: offboarding tickets from the PSA, the Partner Center subscription export, and the client invoices for the same months. Partner Center’s Export all subscriptions download includes each subscription’s quantity, its autorenewal status and renewal date, and its billing cycle. For every user offboarded last quarter, record:

• Client, user and offboarding date, from the ticket.
• The SKU the user held and the subscription it sits on.
• The subscription’s term — monthly, annual or three-year — and its renewal date.
• Whether the license was reassigned to someone else, and on what date.
• Whether the client is still invoiced for the seat under its agreement.
• The months left until renewal, and the seat price on the firm’s distributor bill.

A seat that was reassigned, or that the client still pays for under its agreement, is not a leak. A seat that sits unassigned on an annual term while the client’s invoice dropped it is one, and its cost is the months left times the seat price. Illustrative example, with round hypothetical numbers: a client on an annual term loses two users in month three, and its agreement bills per active user. At $20 a seat a month, the firm carries 2 seats × 9 months × $20 = $360 for that client alone, and the same pattern repeats for every client with departures and the same agreement wording. Run it for one quarter before deciding whether it matters; the count either finds a number worth fixing or shows that it does not.

What the client agreement needs to say

Microsoft’s rules do not change, so the fix lives in the firm’s own paper and its offboarding routine. The specific wording is for the firm’s attorney, but the questions the agreement should answer are plain:

• Which licenses are bought on an annual or longer commitment, and that the client pays for them through the end of the committed term, even if a user leaves or the agreement ends early.
• When seats can be reduced — at the subscription’s renewal — and how much notice the firm needs before that date to schedule the reduction.
• That a monthly-term option exists for users the client expects to be short-term, at the price shown on the current price list.
• What happens to the remaining commitment if the client terminates, is sold or stops paying.
• That the client tells the firm about departures through the offboarding request, so the seat can be reassigned before anyone buys a new one.

The offboarding ticket is where the routine starts. Microsoft’s own guidance on removing a former employee notes that when a license is removed, “you can assign it to someone else.” A checklist line on every offboarding ticket — free the license, note the SKU and renewal date, offer it to the next hire — turns a stranded seat into an inventory item instead of a surprise at renewal.

The renewal calendar: when a seat can finally come off

Because the window opens once per term, the date that matters is each subscription’s renewal. Microsoft lets a partner schedule changes for the end of a term instead of making them immediately, including license reductions, through Manage Renewal on the subscription — but only while the subscription is active and autorenew is on. Renewals are processed the day after the term end date.

Two details catch firms out. First, saved scheduled changes are deleted if the partner makes certain midterm changes, and changing a quantity is one of them: adding a seat for a new hire in month eleven wipes a reduction scheduled in month nine, so the schedule has to be checked again after any midterm change. Second, a subscription that is suspended has autorenew turned off, and scheduled changes require autorenew to be on.

• List every annual and three-year subscription by client with its renewal date, from the export.
• Sixty days before each renewal, compare the seat count with active users and with what the agreement bills.
• Schedule reductions through Manage Renewal, then recheck after any midterm change on that subscription.
• In the seven days after renewal, confirm the new quantity matches what was agreed with the client.

The opposite drift, and when not to bother

Stranded seats are the mirror image of a better-known leak: seats added during the year that the client agreement never started billing. One runs the firm’s cost up, the other holds its revenue down, and both come from the same gap between Partner Center, the PSA and the invoice. Counting them together, client by client, gives the true difference between what Microsoft bills the firm and what the firm bills its clients.

It is not always worth counting. A firm that sells mostly monthly-term subscriptions has little commitment to strand. A firm whose agreements already pass annual commitments through, and whose invoices show it, has already fixed this. And a firm with a handful of clients and little staff turnover can check this in an afternoon with the export and the invoice register, with no outside help at all.

Where our Review fits

When the seat question is one of several — seats added and never billed, licenses the distributor bills that no client invoice carries, tech time never invoiced, invoices past 60 days — our Revenue Review counts them together. It works from read-only access to the firm’s PSA, a billing-level export of RMM agent counts per client, the distributors’ license bills and the books, under an NDA signed before anything opens, and it touches nothing in client environments. It takes two weeks and ends in a written report the firm keeps: each leak with a monthly dollar figure wherever the records support one, a ranked list of what to fix, and a 90-day plan. It gives no legal advice on the agreement wording, and it is not a Microsoft licensing service.

The next step is a free 20-minute call. If the only leak is stranded seats, the call will say so, and the count above is enough.