In the past, reliability has not been great. Deployment has not been simple. Getting it to run is a difficult process.

With one being the easiest experience and five being the most difficult, I would give the deployment process a three and a half out of five.

Make it completely routable, for example, if I have a gateway, I should be able to connect to whatever network I want on either side of the gateway, and the gateway should figure out which packet goes where. 

This is a traditional firewall or network gateway administration that has been removed from the Azure VPN and Gateway functionality, which should just put it back where it belongs, because as it is now if you have three networks, three different networks on either side of Azure, you have to configure one gateway per network.

The stability could be improved. The setup is a little bit complex. In the next release, I would like to see a new setup process.

I would like the solution to be more simple. If it were simple, we could remove other solutions, like tiering, and move to VPN for all of our requirements. VPN is much better to use because tiering is non-reciprocal, so we have to make a connection between the two endpoints.

Their technical support could be better. If you don't have a support contract, it takes longer.

Microsoft Azure VPN Gateway could improve by providing IPS zero-day threat protection. For example, the IPS zero-day threat protection can monitor the user behavior to protect the infrastructure. The solution can only be used as a VPN, it is lacking features. 

The cost could be lower. In the next release, Microsoft should add an option to schedule upgrades.