Networking
The Networking forum covers all aspects of Networking in Azure, including endpoints, load-balancing, network security, DNS, Traffic Manager, virtual networks, and external connectivity.
Virtual Network:
Traffic Manager:
Network Watcher:
If you have any feedback on any aspect of Azure relating to Networking, we’d love to hear it.
-
Load Balancer and Public IP SKU.
There must be an option of Upgrading Public IP SKU from Basic to Standard without losing Static PIP as it is a creating a big road block when we do any planning like moving existing PIP behind any NVA Standard Load balancer.
If any existing Production Server are already running on Basic PIP then it is very tough to make any decisions to upgrade SKU or move it behind any Standard ELB.Need suggestion here how and till what time we can overcome here.
1,128 votesThank you for the feedback. We are working on prereqs to make this possible. Not in scope for CY2019.
— Christian -
Drain/admin endpoint control for Load Balancer
Many on-prem systems rely on an ability to gracefully drain traffic from a node before removing it from load balancing for updates or maintenance. While there are workarounds today for the Azure Load Balancing infrastructure (http://serverfault.com/questions/686095/gracefully-take-a-server-out-of-azure-load-balancer-drain-stop) it's not as flexible as existing on-prem services. Please add this feature.
592 votesWe’re working on planning this feature.
— Christian -
Active / passive load balancing without the dependency of the cluster service.
Active / passive load balancing without the dependency of the cluster service.
158 votesWe are looking at ways to support this scenario where one active instance/one or more passive instances can be supported and flows are not impacted.
— Christian -
Allow Selection of VMs within Availability set/VMSS for standard LB backend pool
It would be great if allowing Selection of VMs within availability set for standard SKU Load balancer backend pool
the feature does exist in Basic only , yet in Standard not. even though it is mentioned in the documentation it supports it.
for example I have a client that needs to add only 50 VMs within an av in a VNET that hosts over 500 VMs. Yet when going to the backend pool of the standard LB it shows all of the 500 VMs , if there is a filtering way to only shows a specific AV that would be…
38 votesThanks for the feedback. This is in backlog for portal.
— Christian -
Add the option of outbound rule on Azure portal
When we want to set the outbound rule for Azure load balancer, there are just two methods to configure that : One is Resource Explore; Another is Azure CLI. The configuration methods recorded in below document:
https://docs.microsoft.com/en-au/azure/load-balancer/load-balancer-outbound-rules-overview
But neither good enough for deployment . Please kindly add this function on portal.14 votesThis is in our near term backlog to expose in portal. You can use Azure CLI, PowerShell, SDK, or templates in the meantime.
— Christian -
Show Traffic lights on an ILB Rule showing which node traffic is being passed too
Load balance rules do not show which server(s) traffic is currently being sent to.
Within a “Load Balance Rule” simple traffic light of Green /or Red against a node would give a quick visual indication that traffic is being sent to the node.
This would help us identify if a service had/was stop on a specific node or if a node was turned off.3 votesIn portal backlog for Standard LB. Please use multi-dimensional metrics in Azure Monitor in the interim to chart the health probe status.
More details can be found here: https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-standard-diagnostics
— Christian -
On Azure portal,under Load balancer the statement of floating IP should be updated.
Recently i took a case ,customer complained this .On Azure portal,under Load balancer the statement of floating IP "says 'We recommend using this feature only when configuring a SQL Always" needs to be updated.
The statement needs to be updated as follows :
We recommend using this feature only when configuring a SQL AlwaysOn Availability Group Listener and SQL Failover Clustered Instance (FCI) IP Address.The current statement appears to be old and was true before we started supporting SQL FCI on Azure. You can see the details here
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-create-failover-cluster1 voteThank you. I agree, it needs to be updated.
— Christian
- Don't see your idea?