Legally binding api deprecation policy
I'm setting up an API deprecation policy for a B2B SaaS company (~500 employees, 1,000+ customers across the EU and US, many with deep API integrations). I need to decide where the deprecation commitment should live contractually.
Our legal team's position is to keep it in the Terms and Conditions rather than surface it in enterprise contracts, primarily to avoid friction in sales conversations with prospects. My concern is that this leaves us without negotiated customer consent to our deprecation rights - so when we eventually need to retire a version a major account depends on, we'd be relying on a clickwrap term the customers may argue was never part of the deal.
I want to propose incorporate the deprecation policy (notice periods, sunset mechanism, migration windows, etc) on it on the enterprise contract itself (MSA - Master Service Agreement), but not sure how much I can/should push.
How do mature business es actually structure this? What approach is the right way to balance sales friction against enforceability?
Ps. I'm coming from a Engineering background. So I'm a bit outside of my legue here.