Hello @marczinser
Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.
I have dealt with a similar issue recently with a user on Microsoft Q&A on this thread https://learn.microsoft.com/en-us/answers/questions/1160767/unable-to-access-original-or-migrated-vm-after-att where technical support investigated the issue and walked through the corrective actions.
I see you are in a situation, where both the VMs original and migrated are inaccessible. We won't be able to abort this migration as rollback is not supported after the resources have been successfully migrated through the commit operation but stuck somewhere.
Right thing to do at this point is to contact Azure VM technical support team and have this issue debugged at the deeper level. If you don't have an active support plan or do not have the ability to open a technical support ticket, please let me know I can help you further on this.
Ref: https://learn.microsoft.com/en-us/azure/virtual-machines/migration-classic-resource-manager-ps
Hope this helps!
If you have any further questions at all, please let me know in the comments.