Hi MR,

Thanks for posting. Personally, my experience with the Azure platform itself is quite limited and not very up to date, so I'm going to limit my advice to the software side in the hope that someone else may be able to give some insight into their experiences in hosting NCrunch on Azure (I know that a number of people posting in this forum do this).

NCrunch's distributed processing is selective with the amount of data it pushes up the wire. Your solution will be stored on the remote node, which means that it must be uploaded over your network connection, but once it's up there it usually won't need to be sent again unless it sees significant changes (i.e. VCS branch switch). The protocol is designed to be responsive on connections with high latency and limited bandwidth. Having your grid node in an Azure data centre should work well in terms of network, especially if you have a site close to you geographically.

The cost is going to depend heavily on the type of VM you allocate. Generally speaking, you're best going for a chunky, high CPU node with just enough memory to fit the number of task runners you have planned (you'll need to measure this for your solution as it depends on the behaviour of your code). Note that later versions of .NET and MSBuild will require more memory.

There is presently no option to run the NCrunch grid node on linux. I think there's a high chance that we will eventually need to support it, but optimistically we are years away from this.

I strongly recommend against opening a TCP port in your Azure firewall for an NCrunch connection. The grid protocol isn't robust enough to give strong protection when routing through the internet. Ideally, set up a VPN connection to your cloud based instance and route through that instead. This will also give better security for your other connections (i.e. remote administration etc).

Be sure to allocate a VM with adequate disk space. It can sometimes be painful to increase it and the MS tool stack grows in size every year. If you have a large number of task processors, NCrunch can also eat quite a bit of disk space with its workspaces.