Fentner

Companies · Opinion

Your Microsoft 365 renewal should price the outage you just had

The 12 November Microsoft 365 outage showed that buyers who consolidated never priced downtime. Every renewal should now carry real outage credits and a tested exit plan.

Somewhere in your finance team there is a spreadsheet that justified moving everything to Microsoft 365. It has licence costs, a line for saved server hardware, probably a saving on integration work. I would bet money it has no line for the day Exchange Online goes down and stays down.

That day started at 1826 GMT on 12 November, by Microsoft's own timing. Exchange Online fell over, Teams was iffy, Copilot misbehaved and Microsoft 365 Education was caught in it too. At 1401 GMT on 13 November Microsoft was still only saying it was "continuing to see improvements". That is a working day lost for any organisation whose staff start early, and Microsoft's name for it was a "Service Degradation".

I expected the usual round of sympathy and a few vendor press releases, and that is what came. Jos Poortvliet of Nextcloud and Mark Boost of Civo both told The Register that concentration is the real risk. Boost put it plainly: "Every technology provider will experience failures." He is right, and I would still discount both of them heavily. Nextcloud and Civo sell the alternative, and an outage is the best sales call they will get all year. The argument they make is correct, but the people making it are paid to make it, so buyers should not wait for them to do the sums.

The sums are the buyer's job, and most buyers skipped them. Consolidation was sold on price: one bill, one admin console, one vendor to shout at. The vendor, in return, got the whole account. Email, chat, files and now Copilot all renew on one date, so the buyer negotiates once and the seller prices accordingly. When that one supplier fails, the customer carries the whole loss. Whatever Microsoft owes for the outage is set by the contract you signed, and I would guess it comes nowhere near what your own people cost you while idle.

So the renewal is where this gets fixed, and I would ask for three things. First, outage credits that scale with the hours lost and are written against your payroll for those hours, rather than a token rebate on the licence line. Second, a named fallback for the narrow functions that stop the business: a second mail path and a second way for staff to reach each other. Third, a tested exit plan with a date on it, showing how long it would take to move mail and files elsewhere. Untested plans are worth nothing, and Poortvliet's list of what single-vendor customers lose is a fair template: switching quickly, a backup setup, working air-gapped.

The obvious objection is that this costs money and adds complexity, and that Microsoft probably keeps Exchange running better than your own team would. I agree on the second point, and nobody should rebuild a rack of mail servers in a cupboard. Microsoft told users this week to treat unsupported Exchange Server 2016 and 2019 as "permanently vulnerable", so going back is not on offer. But that same warning is the reason to push harder at renewal. Microsoft is steering customers towards the hosted product and has made staying put unsafe, which means it expects you to renew. A seller that expects you to renew will give away very little unless asked, and a customer with no exit plan has nothing to ask with.

The fallback I am describing is cheap next to a second full suite. A secondary mail route and a separate messaging tool for incident use cost a fraction of the licences, and they need to be set up and tested before the next outage.

Before your next renewal call, take the hourly cost of your payroll, multiply it by the hours your people could not work between the evening of 12 November and the afternoon of 13 November, and put that figure next to the credit your agreement would pay. Bring both numbers to the meeting. If the second one is a rounding error, ask for the credit terms to be rewritten before you sign.

Prompted by Microsoft outage gives customers a crash course in dependence on Redmond, theregister.