How can you connect on-premise server and an application via IPSec with Azure?
A.
Configure Windows Azure Connect.
B.
Configure Windows Azure AppFabric Access Control.
C.
Use the Windows Azure AppFabric Service Bus.
D.
Use the Windows Azure Content Delivery Network (CDN).
Explanation:
http://msdn.microsoft.com/en-us/library/windowsazure/hh697512.aspxWindows Azure Connect (previously known as codename Sydney) enables Windows Azure users to set up secure, IP-level network connectivity between their Windows Azure hosted services and local (on-premises) resources.
Connected machines can communicate bi-directionally over an IPv6 address that Connect provides. This connection is secured with IPsec and will work through firewalls, network address translation (NAT), and so on. You can view the assigned IPv6 addresses in the Virtual Network section of the Management Portal (note a machine will only acquire an address when its policy is configured to allow it to connect to other machines).
A common use case for Connect is having your Windows Azure web role communicate back to an on-premises SQL Server database. Or you may want to join your Windows Azure role instances to on-premises Active Directory domain (see details in the next section). Or you can use Connect to remotely administer your Windows Azure role instances, such as using the remote event viewer or remote service manager. Or you can remote access your Windows Azure role instance and copy files from an SMB share on a local machine. Since Connect provides low-level network connectivity, you can use it in basically any way you choose.
Note that application connectivity in Connect is governed by Windows firewall policy, just as within a normal network. If your application requires specific firewall settings to work, you will need to set appropriate firewall rules manually.