Get the latest updates on Azure products and features to meet your cloud investment needs. Subscribe to notifications to stay informed.RSS feed
Azure public IPs now support the ability to be upgraded from Basic to Standard SKU, enabling customers to retain the same IP address for services that require Standard IP frontends.
Standard Load Balancers and Standard Public IP addresses support cross resource group moves enabling easy management of resources at the resource group level.
Azure Load Balancer now supports load balancing across regions based on health and latency.
The zone related behavior in Standard Public IP address and Standard Load Balancer is being changed.
Azure Load Balancer customers now have instant access to a preconfigured solution for health monitoring and configuration analysis enabling rapid fault localization and informed design decisions.
Azure Load Balancer now supports adding and removing resources from a backend pool via an IPv4 or IPv6 addresses and virtual network ID. This will enable you to easily manage the containers, virtual machines, and virtual machine scale sets associated with their load balancer. It will also allow IP addresses to be reserved as part of a backend pool before the associated resources are created.
Azure Load Balancer TCP resets on idle timeout is now generally available in all Azure regions.
Global VNet Peering now supports Standard Load Balancer in all Azure regions, including Azure China and Azure Government regions.
Azure Standard Load Balancer and Standard Public IP are now generally available in Azure Government cloud regions.
Azure Standard Load Balancer is now generally available in Azure China cloud regions.
Outbound Rules for Standard Load Balancer is now generally available. This new ability allows you to declare which public IP or public IP prefix should be used for outbound connectivity from your virtual network, and how outbound network address translations should be scaled and tuned.
Now in preview, Azure Load Balancer supports sending of bidirectional TCP resets on idle timeout for load balancing rules, inbound NAT rules, and outbound rules.
The Azure portal has built-in support to add HTTPS probes to standard load balancers.
Azure Standard Load Balancer is now generally available in all regions.
Azure Networking features will be available only in the Azure portal from October 4th, 2017. Networking related feature support from the classic Portal will be deprecated starting October 4th.
HA Ports, a premium offering of the Azure Standard Load Balancer, is now generally available. This will enable customers to configure a single load balancing rule to process traffic from all the protocols and ports, thus enabling deployment of services or appliances in high availability mode.
Load Balancer Standard is in preview. You can use it to create load-balanced deployments with greater scale, resiliency, and ease of use for virtual machine instances inside a virtual network.
Azure Load Balancer introduces a HA Ports, a capability that enables you to load balance internal virtual network traffic on all ports for all supported protocols.
Multiple IP addresses per network interface is generally available.
Multiple IP addresses per NIC is in public preview.
Azure at Microsoft Ignite
Read the Azure blog for latest news and announcements.Blog
Tell us what you think of Azure and what you want to see in the future.Provide feedback
Azure is available in more regions than any other cloud provider.Check product availability in your region