Hello Sudipta Patnaik,
Thank you for posting your question in the Microsoft Q&A forum.
When RDP fails to a VMSS instance after removing the VMAccess Agent extension despite correct NSG rules, several other factors should be verified.
- Ensure the Windows Firewall on the VM allows RDP traffic, as it may block connections even with open NSG rules.
- Check that the VM's operating system has the RDP service enabled and running, as the VMAccess extension typically manages this configuration.
- Validate that the VMSS instance has a valid network interface with proper IP configuration and that the instance itself is in a healthy, running state.
- Confirm the VM's local administrator account credentials are correct, as password resets often rely on the VMAccess extension. If using Azure Bastion or just-in-time access, ensure those services are properly configured.
Finally, consider redeploying the instance or re-adding the VMAccess extension if all else fails, as some VMSS configurations may depend on it for proper RDP setup.
If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.