Azure Websites can be set up to monitor and pull GitHub changes, and this works fine.
However, if you then configure the website to then use a virtual network (so that it may connect to a VM), pulls from the repo then fail and I suspect event triggers will also fail.
Disconnection of the website from the virtual network results in GitHub source control publication working again.
The error is obscure "ssh: connect to host github.com port 22: Bad file number", but basically it seems that connecting an Azure Website to a virtual network stops the website from being connected to the outside world in the same way as when it is connected to a virtual network.
Is this a bug, or is there some extra configuration of the Virtual Network requires which is not available in to management or portal sites?