Problem connecting to Azure VM via RDP and Bastion

Hitesh raut 40 Reputation points
2026-09-06T06:15:37.03+00:00

Hello

I was practicing on Azure using free credits and created a VM. When I tried to connect with RDP, I faced issues:

I enabled RDP services, but later realized my local PC is running Windows 11 Home, which does not support Remote Desktop (RDP). Upgrading to Windows 11 Pro costs around ₹6000 INR.

Is it true that Windows 11 Home does not support RDP, and are there any alternative ways to connect via RDP without upgrading?

Since RDP was not working, I tried connecting through Azure Bastion:

I created a Bastion host in the same VNet and region as the VM.

I was able to connect, but instead of the Windows desktop interface, I only saw a command prompt with options like:

Add admin, Date and time, Log off / Restart / Exit ,PowerShell

I could not reach the normal Windows interface. Later, the VM started showing “failed to connect.”

For reference, the VM image I used was Windows Server 2025 Core Gen2 x64.

My questions are:

Is RDP truly unsupported on Windows 11 Home, and what alternatives exist?

Why does Bastion only show command prompt options instead of the Windows desktop?

Is this behavior expected when using Windows Server Core images?

What is the recommended way to connect and manage such VMs?

Azure Bastion
Azure Bastion

An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.

0 comments
Answer accepted by question author
Andrew Taylor - COREZENN 1,390 Reputation points Volunteer Moderator
2026-09-06T23:59:37.2833333+00:00

Hi @Hitesh raut

Thank you for reaching out to Microsoft Q&A. Windows 11 Home cannot act as an incoming Remote Desktop host, but it can be an RDP client. You can use Remote Desktop Connection or the Windows App from your PC to connect to the Azure VM, so an upgrade to Windows Pro is not required for this scenario.

See Enable Remote Desktop on your PC.

Also, the command prompt/SConfig screen through Bastion is expected because Windows Server 2025 Core does not include Desktop Experience. It is intended to be managed with PowerShell, SConfig, or remote-management tools. To use a normal Windows desktop, deploy a Windows Server image labelled with Desktop Experience; Server Core cannot be converted in place.

See Server Core vs Server with Desktop Experience.

For the Bastion “failed to connect” message, check that the VM is running, the RDP service and Windows Firewall allow RDP, and the NIC/subnet NSG permits TCP 3389 from AzureBastionSubnet.

The detailed diagnostic steps are in Troubleshoot Azure Bastion session failures.

Please 'Upvote' (Thumbs-up) and 'Accept' as answer if the response was helpful. This will help other community members facing the same issue.

Best regards, Andrew S Taylor

Was this answer helpful?

1 person found this answer helpful.
Answer accepted by question author
kagiyama yutaka 5,410 Reputation points
2026-09-06T06:57:36.6+00:00

I think Windows 11 Home doesn’t block you from connecting to Azure VMs — it only lacks the RDP host, not the client. Windows Server 2025 Core has no GUI by design, so Bastion will always show cmd/PowerShell only. If you need a desktop, use a Desktop Experience image. If you stay on Core, manage it via Windows Admin Center or PowerShell instead of expecting a GUI.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-09-06T06:15:57.7133333+00:00

    Yes. A local RDP client on the computer is not required when connecting through Azure Bastion, because Bastion supports browser-based access from the Azure portal and does not require an RDP or SSH client installed locally.

    What happened with Bastion is consistent with the VM image that was deployed:

    1. Windows Server 2025 Core Gen2 x64 is a Server Core image.
    2. Server Core does not provide the full Windows desktop GUI.
    3. When connecting, it is expected to see a command prompt or limited management shell experience instead of the normal desktop interface.

    So the Bastion behavior is expected for that image type, not a Bastion failure by itself.

    For Azure Bastion access, these points apply:

    • The VM does not need a public IP.
    • Bastion connects to the VM over its private IP in the virtual network.
    • No agent is required on the VM.
    • Bastion can be used either from the browser in Azure portal or with a native client.

    If Bastion later changed to failed to connect, use this troubleshooting path:

    1. In the Azure portal, open the Azure Bastion resource.
    2. Go to the Help section.
    3. Open Connection Troubleshoot.
    4. Run a connectivity check from the selected source to the target VM.
    5. If Just-in-time (JIT) is enabled, add the required role assignments and try again.

    If connecting by standard RDP instead of Bastion, the documented checks for a Windows VM are:

    1. Reset Remote Desktop configuration in the VM from Help > Reset password and choose Reset configuration only.
    2. Verify NSG rules and confirm an inbound Allow rule exists for RDP on port 3389 with correct priority.
    3. Review boot diagnostics for startup issues.
    4. Reset the NIC.
    5. Check Resource Health.
    6. If needed, reset the VM password, restart the VM, or redeploy the VM.

    Recommended way to manage this VM:

    • If a full graphical desktop is required, use a Windows image that includes the desktop experience rather than a Server Core image.
    • If continuing with Windows Server Core, manage it through command line / PowerShell and use Bastion as a secure access path.
    • If direct RDP is used instead of Bastion, the VM typically needs reachable RDP access and the usual RDP troubleshooting checks above.

    Also, for Bastion access, ensure the required Azure roles are present:

    • Reader on the VM
    • Reader on the VM NIC with the private IP
    • Reader on the Azure Bastion resource
    • Reader on the target virtual network if Bastion is deployed in a peered virtual network

    For Windows sign-in rights, the account must also have rights on the VM. For RDP to a Windows VM, if the account is not a local administrator, it must be in Remote Desktop Users.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.