Hello @Dalbir Singh ,
Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.
The approach you have followed is often referred to as lift and shift method. For your issue, first thing to check whether the VM booted after it has been spun on azure using the uploaded VHDs? You can check that from the "Boot Diagnostics" blade on Azure VM as shown below (Assuming it is windows VM)
If you don't see the login screen, then that's a boot issue. It's not an RDP issue. If you see login screen and cannot RDP, then you need to follow the TSG available at
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-rdp-connection
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/detailed-troubleshoot-rdp
It appears to be an issue with the VHD itself. To eliminate the issue with the VHD, you can try to create a VM on Hyper-V on-premises itself and see if the VM can be booted fine.
Recommendations:
I would suggest you use Azure Migrate for this migration. It will replicate the on-prem VMs to managed disks and helps migrate the VM to azure with a lot ease. I am adding links to the Migrate document. Please refer to the how to guides:
https://learn.microsoft.com/en-us/azure/migrate/
https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix
Please "Accept as Answer" and Upvote if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.