Data loss prevention when switching to secondary during failover

During the failover test in Azure SQL Database from primary to secondary, I see that every time there is a loss of 3 seconds worth data during the switch. I want to minimise this data loss. The documentation states: >To protect critical transactions from data loss, an application developer can call the sp_wait_for_database_copy_sync stored procedure immediately after committing the transaction. How can we achieve this point? Does this statement mean we need to add a SQL script that is automatically triggered on each commit? Has anyone tried this option? Is there any other way to optimise the data loss?