Ability to rollback sql action if anything fails

I am using version 2.3 to run entity framework migrations against env databases. I would like to know if I can rollback all of the script if any failure happens. Currently, bits and pieces of a migration will work while others fail. The end result is an insert into the ef migration history table which is not ideal for us.

Review the action's migration execution logic and how Entity Framework migration scripts are run against Azure SQL. Reproduce a migration with a deliberate failure, then verify whether partial changes and an entry in the EF migration history table remain; done means the migration is all-or-nothing and the behavior is covered by tests.

Written by the indexing model from the issue text.