Hi @Mohneesh Soni ,
Based on the information you provided, the issue is specific to the vBond image and not related to the Azure region or image version.
To troubleshoot the issue, we need to collect the logs from the VM while it is in the "Creating" state. The logs will help us identify the root cause of the issue.
You can collect the logs using the Azure Serial Console. To do this, follow these steps:
- Go to the Azure portal and navigate to the VM that is stuck in the "Creating" state.
- Click on the "Serial Console" button in the top menu bar.
- In the Serial Console window, click on the "Send Ctrl-Alt-Del" button to reboot the VM.
- Wait for the VM to reboot and then press any key to enter the boot menu.
- Select "Boot Diagnostics" from the boot menu and press Enter.
- Wait for the VM to boot into the diagnostics console.
- In the diagnostics console, click on the "Serial log" tab to view the logs.
The logs will provide more information about what is happening during the VM creation process. Look for any error messages or warnings that might indicate the root cause of the issue.
If you are unable to identify the issue from the logs, you can try creating a new VM from the same vBond image and see if the issue persists. If the issue persists, you can contact Cisco support for further assistance.