100 Day Cloud Azure (Day 21: Assigning Public IP to Virtual Machines) - Task Validation Issue – “SSH access failed” despite correct setup

Hello KodeKloud Support Team,

I am facing a recurring validation issue with the Azure VM task (Create VM with static public IP and SSH access).

Despite following the instructions exactly and verifying the configuration manually, the task continues to fail with the message:

“SSH access to ‘devops-vm’ failed or VM is not in the ‘running’ state.”

What I have done (and verified)

  • Created an Ubuntu VM named devops-vm in Central US
  • Used VM size Standard_B1s
  • Created a Static Public IP named devops-pip
  • Associated the static IP with the VM
  • Generated SSH key pair on the azure-client host
  • Added the public key to the VM for SSH access
  • Ensured NSG rule for SSH (port 22) is explicitly enabled
  • Confirmed VM is running
  • Confirmed SSH access works from the KodeKloud console and from external connection:
ssh -i ~/.ssh/devops_key azureuser@<public-ip>

Output of key verification commands

  • VM status: VM running
  • Disk type: Standard_LRS
  • Public IP allocation: Static
  • NSG rule: Allow TCP 22

Problem

Even after repeating the task multiple times (via Azure CLI, Azure Portal, and KodeKloud Cloud Shell), the task is still marked as failed.
I believe this is a validation issue on your side, as the VM is accessible via SSH and all required settings are correct.

Could you please review the task validation or provide guidance on any missing requirement?
I can also provide screenshots or command outputs if needed.