Windows Vm not showing in tenant, can no longer RDP into it

Question

Windows Vm not showing in tenant, can no longer RDP into it

Dwayne Cunningham 0

Hemalatha 14,195 Reputation points Microsoft External Staff Moderator

2026-06-08T05:44:32.4633333+00:00

Hello Dwayne,

Just checking if provided information was helpful! Please let me know if you have any queries
Nikhil Duserla 9,940 Reputation points Microsoft External Staff Moderator

2026-06-11T10:02:27.0366667+00:00
Hey Dwayne — sorry you’re dealing with that. Based on the info you shared (“Windows VM not showing in tenant” and “can no longer RDP into it”), this usually points to either (1) the VM isn’t actually running anymore / is stuck during boot, or (2) the VM is running but something changed in connectivity or the VM/RDP configuration.

Here are the most relevant Azure VM troubleshooting steps you can start with (in the order Microsoft recommends):

1) Check whether the VM is running in Azure

In the VM resource in the Azure portal, verify the VM is started.

If it recently had Windows Updates, follow the guidance for VMs that are stuck updating at boot.

2) Use the built-in diagnostics to see what’s failing

The “CannotRdpAzurePortalInsight” diagnostic is meant to check common causes of boot/connectivity issues. Review its results in the troubleshooting experience (it can indicate whether it detected a problem or not).

3) If you can’t reach the VM, check Boot Diagnostics to confirm boot state

Use Boot Diagnostics (Boot Diagnostics / serial console logs) to determine if the VM is hitting a boot error and whether it even progresses far enough to accept RDP.

If the VM isn’t at the Ctrl+Alt+Del screen, it may be experiencing a boot error.

4) Try a restart (boot-error scenario)

If the VM may be in a boot error state:

From the VM resource blade, select Restart.

Also review common boot error guides (examples include Windows Update boot issues, disk/check filesystem issues, BitLocker boot issues, reboot loops, etc.).

5) If the VM is running but RDP still fails: validate network security for port 3389

Connectivity failures can also come from issues external to the VM such as NSGs.

Ensure there’s an NSG inbound Allow rule for TCP 3389 (RDP), and that it’s prioritized correctly.

If you use other network paths (like VPN/forced tunneling), double-check routing behavior because it can break RDP even if NSG rules look correct.

6) If nothing obvious is found: consider redeploying the VM

If the diagnostics don’t detect an issue, the guidance recommends redeploying the VM (often resolves RDP/connection failures by correcting host-level/platform issues).

Quick follow-up questions (so we can narrow it down fast)

In the Azure portal, does the VM show as running or stopped/deallocated?

When you say “not showing in tenant,” do you mean:

it doesn’t appear in the portal UI at all, or

it appears but RDP connectivity fails?

What’s the exact RDP error message you get (if any)?

Are there recent changes, like Windows Updates, feature installs/removals, or any network/NSG changes?

In Boot Diagnostics, does the VM show signs of boot progress, or is it stuck/erroring?

If you can share the answers (and the VM boot diagnostic screenshot/state), it’ll be much easier to pinpoint whether this is a boot/update issue vs. an NSG/RDP configuration issue.

References (relevant documentation)

My Windows VM is not starting: https://supportabilityhub.microsoft.com/solutions/apollosolutions/95bc1151-aabb-e35b-f91a-1b699d0bfa9a/apollo-36f6066e-7571-4597-a637-94f532c6c498

My Windows VM is not booting: https://supportabilityhub.microsoft.com/solutions/apollosolutions/95bc1151-aabb-e35b-f91a-1b699d0bfa9a/apollo-ec711657-87b8-4556-8a17-bd8172ef7921

Resolve connectivity issues with your Windows VM: https://supportabilityhub.microsoft.com/solutions/apollosolutions/95bc1151-aabb-e35b-f91a-1b699d0bfa9a/1eee39b5-9658-4d27-bae9-131ce7cd47b0

Troubleshoot Remote Desktop connections to an Azure VM (PowerShell + NSG/3389 + restart/redeploy guidance): https://learn.microsoft.com/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-connection

Azure VM can’t RDP – “Working on features” (if this matches what the VM shows): https://learn.microsoft.com/troubleshoot/azure/virtual-machines/windows/azure-vm-cannot-rdp-working-features?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider

Troubleshoot deployment/allocation failures when creating/restarting VMs (allocation failure troubleshooting pointers): (referenced from “My Windows VM is not starting” page) https://docs.microsoft.com/azure/virtual-machines/windows/allocation-failure

Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.

2 answers

Your answer

Hemalatha 14,195 Reputation points Microsoft External Staff Moderator

2026-06-08T05:44:32.4633333+00:00

Hello Dwayne,

Just checking if provided information was helpful! Please let me know if you have any queries

Answer 1

Hello Dwagyne,

Thank you for reaching out.

I understand that your Windows VM is no longer visible in the tenant portal and that you are unable to connect to it through RDP.

To help us determine whether this is a visibility issue, access issue, or if the VM has been moved or deleted, could you please provide the following details:

1.Confirm that you are signed in to the correct Azure Directory (Tenant) and Subscription. You can verify this from the Directory + Subscription selector in the Azure portal.

2.Check whether the VM is visible through Azure CLI or PowerShell:

az vm list -o table
az vm show --name <VMName> --resource-group <ResourceGroupName>

PowerShell

Get-AzVM -Name <VMName> -ResourceGroupName <ResourceGroupName>

Please let us know the results of the above commands:
- If the VM is returned by the commands but not visible in the portal, this may indicate a portal, filtering, or permissions-related issue.
- If the VM is not returned, we will need to investigate whether the VM was deleted, moved, or is outside the current subscription scope.

Once we receive the requested information and command outputs, we will continue our investigation and assist you with the next steps.

Answer 2

Start with basic connectivity checks, then move to VM-side recovery, since the VM is no longer visible in the tenant view and RDP is failing.

Verify VM existence and state
- In the Azure portal, confirm the correct directory/tenant and subscription are selected.
- Check whether the VM resource still exists and what state it is in (Running/Stopped/Deallocated/Failed). If the VM was deleted, only dependent resources (NIC, disks, public IP) may remain.
Use built-in RDP troubleshooting if the VM exists
- If the VM is present but RDP fails, follow the standard RDP troubleshooting sequence:
  1. Reset Remote Desktop configuration using the VMAccess extension.
  2. Verify NSG rules allow inbound TCP 3389 and no higher-priority deny rules block it.
  3. Check VM boot diagnostics for OS-level issues.
  4. Reset NIC, restart the VM, and if needed, redeploy the VM.
- From PowerShell, reset RDP on the VM:
```
     Set-AzVMAccessExtension -ResourceGroupName "myResourceGroup" `
         -VMName "myVM" -Location Westus -Name "myVMAccessExtension"
```
  Replace names and location with the actual resource group, VM name, and region.
Check for common RDP causes on a running VM
- If the VM is running but RDP shows the generic error “Remote Desktop can’t connect to the remote computer,” check:
  - Remote Desktop is enabled on the VM.
  - Remote Desktop Services (TermService) is running.
  - RDP listener is correctly configured and listening on TCP 3389.
  - Windows Firewall allows RDP (Remote Desktop rule enabled) and no local firewall/IDS is blocking it.
- If needed, use Serial Console or Remote PowerShell (if configured) to:
  - Enable the Remote Desktop firewall rule.
  - Set HKLM\System\CurrentControlSet\Control\Terminal Server\fDenyTSConnections to 0.
Handle Safe Mode or OS boot issues
- If boot diagnostics show the VM stuck in Safe Mode, RDP will fail. In that case:
  1. Stop the VM and detach the OS disk.
  2. Attach the OS disk to a healthy repair VM.
  3. On the repair VM, open an elevated command prompt and identify the attached OS disk drive letter (for example, F:).
  4. Check boot configuration:
```
        bcdedit /store F:\boot\bcd /enum
```
    Confirm the entry with the \Windows folder and note its Identifier (typically {default}). If safeboot is present under Windows Boot Loader, Safe Mode is enabled.
  5. Remove the safeboot flag:
```
        bcdedit /store F:\boot\bcd /deletevalue {Default} safeboot
```
  6. Verify the flag is removed:
```
        bcdedit /store F:\boot\bcd /enum
```
  7. Detach the OS disk from the repair VM, reattach it to the original VM, and recreate/restart the VM, then test RDP.
Consider brute-force or attack-related symptoms
- If RDP intermittently fails and security logs show many 4625 events (bad username or password), the public RDP endpoint may be under brute-force attack. In that case:
  - Use Serial Console or Remote PowerShell to review Security logs.
  - Restrict RDP exposure (for example, NSG source IP filters, just-in-time access, or private access via VPN/ExpressRoute).
If the VM truly does not appear
- If the VM resource no longer appears in any subscription/tenant that should contain it, treat it as deleted:
  - Confirm whether managed disks, NICs, and public IPs still exist.
  - If only dependent resources remain, create a new VM from the existing OS disk (if present) and reconfigure NSG and RDP as above.

If none of these steps restore visibility or connectivity, open a support case from the Azure portal (Help icon → New support request) so platform-level issues with the tenant or subscription can be investigated.

References:

Share via

Windows Vm not showing in tenant, can no longer RDP into it

1) Check whether the VM is running in Azure

2) Use the built-in diagnostics to see what’s failing

3) If you can’t reach the VM, check Boot Diagnostics to confirm boot state

4) Try a restart (boot-error scenario)

5) If the VM is running but RDP still fails: validate network security for port 3389

6) If nothing obvious is found: consider redeploying the VM

Quick follow-up questions (so we can narrow it down fast)

References (relevant documentation)

2 answers

Your answer