To assist you better, could you kindly clarify what you mean by the "frontend server" in this context? Are you referring to the Azure Blob Storage service itself, or is there an additional component (such as a proxy or application gateway) in front of it?
Your clarification will help us provide more accurate guidance.
Based on your clarification,
SSL scanning tools may still show TLS 1.0/1.1 as "available" because the Azure frontend infrastructure (like CDN or public IP endpoints) still technically supports them for backward compatibility.
Disabling TLS 1.0/1.1 at the Endpoint Level: Currently, Azure does not allow disabling TLS 1.0/1.1 at the public endpoint or CDN level for Blob Storage.
Azure’s global frontend infrastructure may still respond to TLS 1.0/1.1 handshakes for compatibility, even if the storage account enforces TLS 1.2, This behavior is not configurable by customers at the IP or CDN level.