Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported.
Iterations can be nested in ADO, and when you try to send records from Aha! to ADO, the iteration value defaults to the root project iteration as opposed to matching the release value from Aha!
Thanks for the idea! Currently, the Azure integration does support syncing iterations.