Share via

Had VM in Azure. can no longer see it

Dwayne Cunningham 0 Reputation points
2026-06-04T18:08:47.1+00:00

Had a windows vm in azure. can no longer see it in tenant. Even when first notice it couldn't be seen, it was still accessible via rdp. Can no longer connect to it via rdp and since i cannot see it in azure, i cannot troubleshoot

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-06-04T18:09:01.6133333+00:00

    The behavior described (VM was still reachable by RDP for a while but no longer appears in the tenant/portal and now is unreachable) indicates that the VM resource is no longer present or addressable in the current subscription/tenant, so Azure-side RDP troubleshooting steps cannot be applied until the VM object is located and confirmed to exist.

    From the provided context, only RDP/connectivity troubleshooting is covered, and all of it assumes that the VM is visible and manageable in the Azure portal or via Azure PowerShell/CLI. The documented steps include:

    1. Verify the VM exists and is running in the Azure portal and check its health/boot state.
    2. If the VM is present, use the standard RDP troubleshooting flow:
      • Use the built-in troubleshooting steps: reset RDP configuration and credentials using Set-AzVMAccessExtension.
      • Verify Network Security Group (NSG) rules allow inbound TCP 3389 and that no higher-priority deny rules block it.
      • Ensure the VM has a reachable public IP or private connectivity (VPN/ExpressRoute) and that the Connect button is not grayed out.
      • Check VM Resource Health and Boot Diagnostics.
      • Use Serial Console to fix OS-level issues (firewall, NIC disabled, RDP service, registry fDenyTSConnections, etc.).
      • As needed, reset NIC, restart, or redeploy the VM.

    However, none of the referenced documentation covers the case where the VM no longer appears at all in the tenant/subscription (for example, if it was deleted, moved to another subscription/tenant, or the current identity no longer has access). In that situation, the documented RDP and NIC/NSG repair procedures cannot be executed because they all require an existing VM resource.

    Because of this, the context does not provide supported steps to recover or troubleshoot a VM that is no longer visible in the tenant.

    References:

    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.