Azure options and best practice Answered


We're just starting to use Azure for a number of services and I'm not clear on the best option to connect up with Cato and any best practice around it too.

Looking at what material is around, there are Youtube videos about setting up IKE tunnels (these are a couple of years old) but then there are also some help pages about virtual sockets and I see a 'not ready for production' Cato socket in the Azure marketplace too.

We are likely to have resources in the US, UK, India and Australia. It seems to me like the current recommended method would be to have virtual sockets hosted in each of those Azure locations, does that sounds correct? Is it the same licensing for a virtual socket as if it were a physical location?

Any guides or recommendations welcome.





  • Comment author

    We are running HA pairs of vSockets on Standard_D2s_v4 VMs in three Azure regions across the globe, it works very well. Licensing is as for a normal site, but instead of the monthly charge for the physical sockets you will have to cover the compute/networking costs for the Linux VMs.

    I would strongly recommend to get deployment assistance from Cato engineers, the configuration is not trivial. As soon as the vSockets are up and running it's zero-maintenance and rock-solid, though.

    Also, I would advise to review the distance from your Azure regions to the nearest Cato PoPs before deploying, and hold Cato accountable for maintaining a healthy RTT. After all, they claim ExpressRoute like performance in the marketing material.




  • Comment author
    Phillip Crocker

    Thanks for that, it confirms what I thought, I'll start my planning based on that.

  • Comment author
    Community Manager The chief of community conversations. Community manager

    Hello JM!

    Thanks for sharing your knowledge and expertise!  We appreciate it a lot!

    Kind Regards,

    Dermot Doran


Please sign in to leave a comment.