You can follow the below approach for the below offerings:
- Synapse dedicated pool : Create a Server in a geo redundant location as to the original server and create a restore point in the original pool and then restore it as a new database pool in the Geo redundant server and then pause the pool (to preserve the cost)
This logic can be scheduled daily/weekly based on your DR frequency and on every run post successful creation of the new database, delete all prev version of database from the DR server
This would ensure DR for the data and the code aspect.
automation : https://learn.microsoft.com/en-us/azure/synapse-analytics/backuprestore/restore-sql-pool
AS ADF is code only, you can export the ARM template and/or git integrate it as the best form of DR
- Azure Key vault : https://learn.microsoft.com/en-us/azure/key-vault/general/disaster-recovery-guidance
4.ADLS Gen 2 : while creating , you can create a Geo redundant storage :
https://learn.microsoft.com/en-us/azure/storage/common/storage-disaster-recovery-guidance