Sql-server – Moving from Azure to Hyperscale

Check out the Docs on Hyperscale:

Hyperscale only supports non persistent In-Memory objects (table types, native SPs and functions). Persistent In-Memory tables and other objects must be dropped and recreated as non-In-Memory objects before migrating a database to the Hyperscale service tier.

As for rollback, it depends what you mean. Can it rollback an uncommitted transaction? Yes, it is a SQL Server after all. Can it restore databases to a point-in-time? Yes, see here and here. For anything else, you'd have to clarify what you mean by rollback.