Page Comparison

• Abiquo never stores SSL certificates, so you cannot create a routing rule for a secure connection in an Abiquo-only load balancer that is not assigned to a network

You cannot change the following attributes in Azure:

• Name

• Azure will only accept the following characters: A-Z, a-z, 0-9 and "-". 
• You cannot change the name after Abiquo creates the load balancer in Azure (when a valid load balancer is saved with a subnet assigned to it)The load balancer name can't have white spaces

• DEFAULT
• SOURCEIP
• SOURCEIPPROTOCOL

• The load balancer must have one and only one public OR private address
• The load balancer can only be attached to one subnet. Mandatory for private addresses  

• Azure load balancers are created for virtual datacenter networks, which are cloud service networks
• Abiquo will not create a load balancer in Azure until it is assigned to at least one subnet
  
  • You can create a load balancer in Abiquo only, by not supplying a subnet
  • If you delete the load balancer directly in the provider, it will remain in Abiquo only

• You must create at least one routing rule. There must always be at least one routing rule in the load balancer
• You can only create one routing rule per incoming port and one rule per outgoing port (i.e. two rules cannot receive traffic on the same port or route it to the same port).

• The health check is optional
• Azure will only allow you to create Only one health check per load balancercan be configured for the load balancer
  • Protocols supported for healthcheck: Tcp, Http
  • Health check interval must be between 5 and 2147483646
  • Health check port must be between 1 and 65535