A client recently had an issue with an Azure VM where the (non-OS) 'premium' storage disks were erroneous removed without warning by Microsoft. This is the virtual equivalent to the hard drives being yanked out of a running server.
They have SQL Server 2014 running on this VM with the data and log files placed separately on the two 'failed' drives.
The live, production, non-clustered databases are being used fairly heavily via various services and applications - with the high probability of commands and transactions having bin in-progress or mid-commit when the issue occurred.
After the issue, the VM was forcibly powered-off, and only became 'operational' after a couple of reboots.
While seemingly no issues have thus far been identified, my question is what are the possible SQL failure modes this could present? Does the transaction log / SQL server architecture account for this type of whole disk failure? Is it possible to have data loss in this situation (without considering corruption of the disk itself). And what checks should/can be performed after such an event?