You have an Azure subscription.

When a Windows VM ' s network adapter is disabled inside the guest operating system, standard remote-management channels such as RDP become unavailable because the adapter that would carry that traffic is itself switched off, so the Azure-recommended portal-based fix is to use the Diagnostic settings blade for VM1 to turn on boot diagnostics if it is not already enabled. Boot diagnostics is in turn a prerequisite for the Serial Console feature, found under Support + troubleshooting on the VM ' s blade, which gives an administrator a SAC or CMD session directly into the VM ' s console over the hypervisor ' s serial channel rather than over the network, so it works even without any functioning network connectivity. From that Serial Console session, commands such as netsh interface set interface admin=enabled can be run against the disabled adapter to re-enable it, after which normal network access and RDP are restored. The IP configurations blade for NI1 only manages the Azure Resource Manager representation of the network interface, such as its private IP address assignment, and has no visibility into or control over the guest operating system ' s adapter enable/disable state, while neither Configuration settings nor Reset password addresses a disabled network adapter at all, making Diagnostic settings the correct starting point in the portal for this scenario.