In general, stretch clustering on Azure Stack HCI is an ideal DR solution for the following scenarios:

• Introducing automatic failover with orchestration for recovery of a web-based application’s front-end server tier after a disaster renders one hosting location unavailable.
• Distributing primary and secondary instances of infrastructure core services, such as Microsoft Active Directory, across two physical locations.
• Hosting applications with lower write I/O performance characteristics.
• Running file-system-based services and other business services that can tolerate being hosted on crash-consistent volumes. For database workloads such as Microsoft SQL Server, which often cannot sustain the loss of even a single transaction, using application-layer recoverability solutions such as SQL Always-On might be more appropriate.
• Stretch clusters are set up either as active/passive or active/active.