hi there Saurabh Deshpande, thanks for dropping this question here, its super cool ure diving into netscaler on azure 8))
alright, lets break this down. first off, the docs u linked are solid, but sometimes azure's newer cloud control plane can be a bit... finicky with secondary ips. Go to the virtual machine in azure portal. under networking, check if the secondary ip configuration is properly assigned. sometimes the ui doesnt reflect changes immediatel, refresh or wait 5 mins. also make sure the managed identity has 'network contributor' role at subscription level (not just resource group!). https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal
aha, and here's is hit trik )))))) after assigning roles, restart both vms. yes, the old 'turn it off and on again' works here too ))
general stuff that might help, netscaler can be picky about ip assignments. Check the subnet masks match exactly between primary and secondary ips. As well try disabling then re-enabling the network interfaces through netscaler cli. hmmmm this often kicks things into gear when azure says everything looks fine but its not working.
aha and test this... can u ping the secondary ip from another vm in same vnet? if yes, then its likely netscaler config. if no, its azure networking layer. this quick test saves hours of headache :))
microsoft's cloud is awesome but sometimes needs that extra nudge.
hope this gets u unstuck! let us know if the secondary ips start behaving or if u hit another wall %))))
Best regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment