Ten Lines to Read Twice Before Your Next UK Cloud Renewal

November 2026 is renewal season for plenty of UK cloud deals. The original business case has been overtaken by new services, new data rules and a finance director who wants fewer surprises. The contract is where those surprises live. This is not legal advice, but it is a practical reading list for busy UK teams.

1. Exit and transition assistance

Ask what data you can export, in what format, over what period and at what cost. Who helps with the migration? Is deletion certified? A vendor that offers only ‘best endeavours’ exit help and no standard export format is making departure hard before you have even arrived. Walk if there is no transition period and no deletion evidence.

2. Egress and exit fees

Egress is data leaving the provider. It is also a line item that can quietly decide whether you stay. Ask for per-GB rates, any waived exit window, backup restore charges and cross-region replication costs. Walk if exit fees are uncapped and there is no negotiated waiver for a planned move.

3. UK data residency commitments

‘UK region’ is a technical location, not a full residency promise. Ask where data at rest, backups, support copies, telemetry and subprocessors sit. Get it in the contract, not just a trust page. Ask for notification when subprocessors change. For sensitive data, walk if there is no enforceable UK residency commitment.

4. Support credits and SLA definitions

Read the exclusions. ‘Available’ may exclude maintenance, third-party failures and force majeure. Ask whether credits are based on monthly fees or a tiny proportion of them. Ask for response times, resolution targets and root-cause reports. Walk if service credits are the only remedy and the numbers are trivial.

5. Suspension rights

Vendors often reserve the right to suspend service for late payment, security risk or unlawful use. Ask for notice, a cure period, data preservation and restoration terms. Walk if the vendor can suspend immediately over a disputed invoice without a short grace period.

6. Price review and uplift

Check the index. Is it CPI, RPI or something vaguer? Is there a cap? How much notice? Can the price rise mid-term? Ask for a fixed cap or a right to terminate if an increase exceeds an agreed level. Walk if uncapped annual uplift comes with no exit route.

7. Auto-renewal and notice windows

A 90-day notice window can catch out a team that only starts thinking about renewal in month eleven. Put the date in the diary now. Ask for a shorter notice period or a renewal reminder. Walk if the deal auto-renews for another 12 months because an email went to a former employee.

8. Committed spend and true-up

Minimum commitments are fine if they match reality. Ask what happens to unused commitment, whether it rolls over and how overage is priced. Ask for a tolerance band around forecasts. Walk if unused commitment vanishes and overage rates punish success.

9. Security, breach notification and liability

Get the shared responsibility matrix. Ask how quickly the vendor will notify you of a breach, and compare that with your UK GDPR obligations to the ICO. Check liability caps and data protection indemnities. Walk if the liability cap is smaller than the likely cost of a data incident.

10. Audit, benchmarking and exit plan

Ask for audit rights, a security questionnaire process and benchmarking or most-favoured-customer language where available. A yearly review keeps the deal honest. Walk if there is no audit right and no sensible way to compare price at renewal.

The walk-away list

Not every clause is a deal-breaker. But if two or three of these are hostile, renewing is a choice rather than a formality. Keep a clause log, involve procurement and legal early, and do not accept ‘standard terms’ as a law of nature. The best time to fix a contract is before the renewal date, not after the first invoice.