Free for PREMIUM members
Go Premium for a chance to win a PS4. Enter to Win
Can I bring my VLANs to Azure using Virtual Network?
Virtual Networks are Layer-3 overlays. We do not support any Layer – 2 semantics.
Can I specify custom routing policies on my virtual networks and subnets?
No. We do not support custom routing policies with virtual networks.
Can I use SQL DBs with virtual networks?
No. We do not support SQL DBs with virtual networks.
Can I define ACLs on my virtual networks?
No. We do not support ACLs for subnets within virtual networks. However, ACLs can be defined on input endpoints for virtual machines that have been deployed to a virtual network. Note: a virtual machine does not have to be deployed to a virtual network in order to define an ACL for the input endpoint.
To enable communication with the database, firewall rules must be defined in Windows Azure SQL Database allowing the public IP address of the VM in Windows Azure to communicate with the data source.
However, creating ACLs based on IP addresses is not ideal, since the ACLs must be updated any time the public virtual addresses change. This can result in service failures, and puts additional burden on the administrator. Public virtual IP addresses can change after compute resources are de-allocated when a virtual machine is shut down, or after a deployment is deleted. Using in-place upgrade enables administrators to deploy new versions of their service without the public IPs of the VMs changing.
• For more information on how to configure IP ACLs, see About Network Access Control Lists
We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!