i created VM but getting error connecting.

Hi Altaf Ingar,

Thank you for reaching out Q/A. Could you please follow the steps below to troubleshoot:

1.Reset RDP configuration only: Select Reset configuration only mode to re-enable Remote Desktop services and Windows Firewall rules for port 3389. This fixes cases where RDP is disabled at the service or listener level.

Reference: https://v4.hkg1.meaqua.org/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-connection

2.Verify Network Security Group (NSG) rules: Go to Networking > Inbound port rules and ensure an Allow rule exists for TCP port 3389 (priority lower than any Deny rules).

Use Network Watcher >> IP flow verify to check if traffic is blocked.

https://v4.hkg1.meaqua.org/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-nsg-problem

3.Try connecting to the Azure Serial Console from the Azure portal. This allows you to check if the VM itself is accessible even when RDP is not working.

Reference: https://v4.hkg1.meaqua.org/en-us/troubleshoot/azure/virtual-machines/windows/serial-console-overview

4.Ensure to check the Boot Diagnostics to see if the VM has started successfully.

Reference: https://v4.hkg1.meaqua.org/en-us/azure/virtual-machines/boot-diagnostics

As mentioned in the below documentation, If the issue persists, you can restart or redeploy the VM. Redeploying moves the VM to a new Azure node while keeping most settings and data intact.

https://v4.hkg1.meaqua.org/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-connection

When you redeploy an Azure VM, it gets moved to a new node, but it keeps its settings and most of your data intact. changes happen when you re-deploy

• What remains unchanged: Your OS disk and any attached data disks will stay intact, along with all system configurations, network settings, security rules, and installed applications. You won’t lose any data stored on these persistent disks.
• What gets lost: Any data stored on the temporary disk (D: in Windows VMs) will be deleted, ephemeral disks will be wiped, and your dynamic IP address may change. If you have important files on the temporary disk, it’s best to back them up before redeploying Redeploy Windows virtual machine to new Azure node

Note: Before performing any activity, please make sure backup of your data.

Please find below reference documentations:

How to connect using Remote Desktop and sign on to an Azure virtual machine running Windows

Detailed troubleshooting steps for remote desktop connection issues to Windows VMs in Azure

If issues, persists Could you please provide the below details.

1. Is this a newly created VM, or were you able to connect previously?
2. Are you seeing any specific error messages during RDP connection pls provide screenshot?
3. What type of VM did you create (Windows/Linux)? Is VM is running from portal?
4. Have you checked the Network Security Group settings for inbound rules?
5. Is this a new VM, or was it created from an existing image?
6. Can you access the VM through the Azure Serial Console?
7. Can you please provide boot diagnostic screenshot of that VM?
8. Is this a standard Azure Virtual Machine, or is it configured as an Azure Virtual Desktop (AVD) session host VM?

Additionally, could you please check private message and provide necessary details