A credit-union auditor reports that outdated TLS 1.0 clients can still negotiate to the municipal dispute portal hosted on App Service. Which App Service setting should the developer raise to block those clients?
Select an answer to reveal the explanation.
Short Explanation
Think of minimum TLS version as the velvet rope at the door—only modern handshakes get in. Bumping it to TLS 1.2 (or higher) stops those dusty 1.0 clients cold. Always On and ARR affinity are useful knobs, but they do not police cipher negotiation.
Full Explanation
App Service exposes a Minimum TLS version setting that rejects connections below the chosen protocol. Microsoft guidance for App Service is TLS 1.2 or later. Always On keeps the site loaded, ARR affinity pins sessions, and remote debugging is for development—not TLS policy.