When dealing with connectivity issues on Windows Azure Site to Site it is important start by scoping the problem correctly and making sure that all the basic tests were done before move forward to a deeper troubleshooting. Here are three key questions that
you should ask even before start collecting and analyzing data:
1) Is this VM able to ping other VMs that are located on the same subnet?
2) Are they part of the same virtual network in Windows Azure?
3) Do I have another VM on the same virtual network able to communicate with on-premise resources?
If the answers for questions 1 and 2 are “no”, most likely the problem will with the new VM that you just created. Probably they are not on the same virtual network or the new VM was created using the Quick Create option. When you use this option you won’t
be able to choose the virtual network on which the VM belongs, therefore it won’t be able to communicate with other VMs that belong to a custom virtual network.
If the answer for the third question is “yes”, then the problem is related to the VM that you just created. Make sure that this VM has the correct configuration, belongs to the same virtual network and after doing that try to perform basic connectivity test
with ping, tracert and compare the results with the VM that works.
If the answer for the third question is “no”, then the problem might be related with the Site to Site connectivity itself. Review the following articles to ensure that the connectivity between Azure and On-Premise is working correctly:
In this scenario the user is trying to authenticate on Windows Azure Portal using his corporate credentials. This is a new deployment and never worked. When the user tries to logon it receives the error below:
In this scenario it is important to validate if the ADFS Server is receiving the SSL request. The following settings should be verify: