You need to implement a disaster recovery solution that meets the technical requirements. The solution must NOT require customers to modify their connection strings. Which disaster recovery solution…

Azure SQL Database's active geo-replication and failover groups utilize a read-write listener endpoint that automatically redirects client connections to the new primary database after a failover, ensuring no changes are needed in customer connection strings.

AlwaysOn Availability Groups, while providing a listener for connection string abstraction, are an on-premises or IaaS SQL Server feature, whereas the choice specifies "to Azure" and implies an Azure-native DR approach.

Transaction Log Shipping typically requires manual failover and an update to connection strings to point to the new primary server, as it lacks a transparent listener mechanism.

Failover Cluster Instances are an on-premises or IaaS SQL Server solution that provides high availability and connection string abstraction via a virtual network name, but this option does not directly involve replication "to Azure" for disaster recovery.