{"id":5773,"date":"2014-10-30T00:00:00","date_gmt":"2014-10-30T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/azure-load-balancer-new-distribution-mode"},"modified":"2025-09-16T08:13:19","modified_gmt":"2025-09-16T15:13:19","slug":"azure-load-balancer-new-distribution-mode","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/","title":{"rendered":"Azure Load Balancer new distribution mode"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Azure Load Balancer is a Layer-4 (TCP, UDP) type load balancer that distributes incoming traffic among healthy service instances in cloud services or virtual machines defined in a load balancer set.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The distribution algorithm used is a 5 tuple (source IP, source port, destination IP, destination port, protocol type) hash to map traffic to available servers. It provides stickiness only within a transport session. Packets in the same TCP or UDP session will be directed to the same datacenter IP (DIP) instance behind the load balanced endpoint. When the client closes and re-opens the connection or starts a new session from the same source IP, the source port changes and causes the traffic to go to a different DIP endpoint.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp\" alt=\"SLB 5 tuple\" title=\"SLB 5 tuple\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">We have introduced a new distribution mode called Source IP Affinity (also known as session affinity or client IP affinity). Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers. By using Source IP affinity, connections initiated from the same client computer goes to the same DIP endpoint.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-2-tuple_thumb.webp\" alt=\"SLB 2 tuple\" title=\"SLB 2 tuple\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Source IP affinity solves an <a href=\"https:\/\/go.microsoft.com\/fwlink\/p\/?LinkId=517389\" target=\"_blank\" rel=\"noopener\">incompatibility between the Azure Load Balancer and RD Gateway<\/a>. Now you can build a RD gateway farm in a single cloud service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Another usage scenario is media upload where the real data upload happens through UDP but wherein the control plane is achieved through TCP:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"wp-block-list-item\">A client first initiates a TCP session to the load balanced public address, gets directed to a specific DIP, this channel is left active to monitor the connection health<\/li>\n\n\n\n<li class=\"wp-block-list-item\">A new UDP session from the same client computer is initiated to the same load balanced public endpoint, the expectation here is that this connection is also directed to the same DIP endpoint as the previous TCP connection so that media upload can be executed at high throughput while also maintaining a control channel through TCP.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Note that if the load-balanced set changes (removing or adding a virtual machine), the distribution of client requests is recomputed. You cannot depend on new connections from existing client sessions ending up at the same server. Additionally, using source IP affinity distribution mode may cause an unequal distribution of traffic. Clients running behind proxies may be seen as one unique client application.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"scenarios\">Scenarios<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"wp-block-list-item\">Configure load balancer distribution to an endpoint on a <a href=\"https:\/\/azure.microsoft.com\/en-us\/documentation\/articles\/virtual-machines-set-up-endpoints\/\" target=\"_blank\" rel=\"noopener\">Virtual Machine<\/a> via PowerShell or Service Management API<\/li>\n\n\n\n<li class=\"wp-block-list-item\">Configure load balancer distribution for your Load-Balanced Endpoint Sets via PowerShell or Service Management API.<\/li>\n\n\n\n<li class=\"wp-block-list-item\">Configure load balancer distribution for your Web\/Worker roles via the <a href=\"https:\/\/msdn.microsoft.com\/en-us\/library\/windowsazure\/ee758711.aspx\" target=\"_blank\" rel=\"noopener\">service model<\/a>.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"powershell-examples\">PowerShell examples<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Make sure to Download and install the <a href=\"https:\/\/github.com\/Azure\/azure-sdk-tools\/releases\" target=\"_blank\" rel=\"noopener\">latest Azure PowerShell<\/a> (October release)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"add-an-azure-endpoint-to-a-virtual-machine-and-set-load-balancer-distribution-mode\">Add an Azure endpoint to a Virtual Machine and set load balancer distribution mode<\/h3>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nGet-AzureVM -ServiceName \"mySvc\" -Name \"MyVM1\" | Add-AzureEndpoint -Name \"HttpIn\" -Protocol \"tcp\" -PublicPort 80 -LocalPort 8080 \u2013LoadBalancerDistribution \u201csourceIP\u201d| Update-AzureVM\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">LoadBalancerDistribution can be set to <strong>sourceIP<\/strong> for 2-tuple (source IP, Destination IP) load balancing,<strong> sourceIPProtocol<\/strong> for 3-tuple (source IP, Destination IP, protocol) load balancing or <strong>none<\/strong> if you want the default behavior of 5-tuple load balancing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"retrieve-an-endpoint-load-balancer-distribution-mode-configuration\">Retrieve an endpoint load balancer distribution mode configuration<\/h3>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nPS C:> Get-AzureVM \u2013ServiceName \u201cMyService\u201d \u2013Name \u201cMyVM\u201d | Get-AzureEndpoint\n\nVERBOSE: 6:43:50 PM - Completed Operation: Get Deployment\nLBSetName : MyLoadBalancedSet\nLocalPort : 80\nName : HTTP\nPort : 80\nProtocol : tcp\nVip : 65.52.xxx.xxx\nProbePath :\nProbePort : 80\nProbeProtocol : tcp\nProbeIntervalInSeconds : 15\nProbeTimeoutInSeconds : 31\nEnableDirectServerReturn : False\nAcl : {}\nInternalLoadBalancerName :\nIdleTimeoutInMinutes : 15\nLoadBalancerDistribution : sourceIP\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">If the LoadBalancerDistribution element is not present then the Azure Load balancer uses the default 5-tuple algorithm<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"set-the-distribution-mode-on-a-load-balanced-endpoint-set\">Set the Distribution mode on a load balanced endpoint set<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If endpoints are part of a load balanced endpoint set, the distribution mode must be set on the load balanced endpoint set<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nSet-AzureLoadBalancedEndpoint -ServiceName \"MyService\" -LBSetName \"LBSet1\" -Protocol tcp -LocalPort 80 -ProbeProtocolTCP -ProbePort 8080 \u2013LoadBalancerDistribution \"sourceIP\"\n<\/pre><\/div>\n\n\n<h2 class=\"wp-block-heading\" id=\"cloud-service-example\">Cloud Service example<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You can leverage the Azure SDK for .NET 2.5 (to be released in November) to update your Cloud Service<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Endpoint settings for Cloud Services are made in the .csdef. In order to update the load balancer distribution mode for a Cloud Services deployment, a deployment upgrade is required.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here is an example of .csdef changes for endpoint settings:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n<WorkerRole name=\"worker-role-name\" vmsize=\"worker-role-size\" enableNativeCodeExecution=\"[true|false]\">\n  <Endpoints>\n    <InputEndpoint name=\"input-endpoint-name\" protocol=\"[http|https|tcp|udp]\" localPort=\"local-port-number\" port=\"port-number\" certificate=\"certificate-name\" loadBalancerProbe=\"load-balancer-probe-name\" loadBalancerDistribution=\"sourceIP\" \/>\n  <\/Endpoints>\n<\/WorkerRole>\n<NetworkConfiguration>\n  <VirtualNetworkSite name=\"VNet\"\/>\n  <AddressAssignments>\n    <InstanceAddress roleName=\"VMRolePersisted\">\n      <PublicIPs>\n        <PublicIP name=\"public-ip-name\" idleTimeoutInMinutes=\"timeout-in-minutes\"\/>\n      <\/PublicIPs>\n    <\/InstanceAddress>\n  <\/AddressAssignments>\n<\/NetworkConfiguration>\n<\/pre><\/div>\n\n\n<h2 class=\"wp-block-heading\" id=\"api-example\">API example<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You can configure the load balancer distribution using the <a href=\"https:\/\/msdn.microsoft.com\/en-us\/library\/azure\/ee460799.aspx\" target=\"_blank\" rel=\"noopener\">service management API<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Make sure to add the x-ms-version header is set to version 2014-09-01 or higher.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"update-the-configuration-of-the-specified-load-balanced-set-in-a-deployment\">Update the configuration of the specified load-balanced set in a deployment<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><b>Request example<\/b><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>Code block 5<\/strong><\/em><\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nPOST https:\/\/management.core.windows.net\/<subscription-id>\/services\/hostedservices\/<cloudservice-name>\/deployments\/<deployment-name>?comp=UpdateLbSet \n\nx-ms-version: 2014-09-01 \n\nContent-Type: application\/xml \n\n<LoadBalancedEndpointList xmlns=\"\" xmlns:i=\"https:\/\/www.w3.org\/2001\/XMLSchema-instance\"> \n\n<InputEndpoint> \n\n<LoadBalancedEndpointSetName> endpoint-set-name <\/LoadBalancedEndpointSetName> \n\n<LocalPort> local-port-number <\/LocalPort> \n\n<Port> external-port-number <\/Port> \n\n<LoadBalancerProbe> \n\n<Port> port-assigned-to-probe <\/Port> \n\n<Protocol> probe-protocol <\/Protocol> \n\n<IntervalInSeconds> interval-of-probe <\/IntervalInSeconds> \n\n<TimeoutInSeconds> timeout-for-probe <\/TimeoutInSeconds> \n\n<\/LoadBalancerProbe> \n\n<Protocol> endpoint-protocol <\/Protocol> \n\n<EnableDirectServerReturn> enable-direct-server-return <\/EnableDirectServerReturn> \n\n<IdleTimeoutInMinutes>idle-time-out<\/IdleTimeoutInMinutes> \n\n<LoadBalancerDistribution>sourceIP<\/LoadBalancerDistribution> \n\n<\/InputEndpoint> \n\n<\/LoadBalancedEndpointList>\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">The value of LoadBalancerDistribution can be <strong>sourceIP<\/strong> for 2-tuple affinity, <strong>sourceIPProtocol<\/strong> for 3-tuple affinity or <strong>none<\/strong> (for no affinity. i.e. 5-tuple)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><b>Response<\/b><\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nHTTP\/1.1 202 Accepted \n\nCache-Control: no-cache \n\nContent-Length: 0 \n\nServer: 1.0.6198.146 (rd_rdfe_stable.141015-1306) Microsoft-HTTPAPI\/2.0 \n\nx-ms-servedbyregion: ussouth2 \n\nx-ms-request-id: 9c7bda3e67c621a6b57096323069f7af \n\nDate: Thu, 16 Oct 2014 22:49:21 GMT\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>We have introduced a new distribution mode called Source IP Affinity and is also known as session affinity or client IP affinity. Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ms_queue_id":[],"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","_alt_title":"","footnotes":"","msx_community_cta_settings":[]},"categories":[1457],"tags":[],"audience":[3053,3056],"content-type":[1511],"product":[1555],"tech-community":[],"topic":[],"coauthors":[224],"class_list":["post-5773","post","type-post","status-publish","format-standard","hentry","category-networking","audience-it-decision-makers","audience-it-implementors","content-type-best-practices","product-load-balancer","review-flag-1680286580-543","review-flag-1680286581-295","review-flag-1-1680286581-825","review-flag-2-1680286581-601","review-flag-3-1680286581-173","review-flag-4-1680286581-250","review-flag-5-1680286581-950","review-flag-6-1680286581-909","review-flag-lever-1680286579-649","review-flag-new-1680286579-546"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Azure Load Balancer new distribution mode | Microsoft Azure Blog<\/title>\n<meta name=\"description\" content=\"We have introduced a new distribution mode called Source IP Affinity and is also known as session affinity or client IP affinity. Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Azure Load Balancer new distribution mode | Microsoft Azure Blog\" \/>\n<meta property=\"og:description\" content=\"We have introduced a new distribution mode called Source IP Affinity and is also known as session affinity or client IP affinity. Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/\" \/>\n<meta property=\"og:site_name\" content=\"Microsoft Azure Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/microsoftazure\" \/>\n<meta property=\"article:published_time\" content=\"2014-10-30T00:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-09-16T15:13:19+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp\" \/>\n<meta name=\"author\" content=\"Yves Pitsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@azure\" \/>\n<meta name=\"twitter:site\" content=\"@azure\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Yves Pitsch\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/\"},\"author\":[{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/author\/yves-pitsch\/\",\"@type\":\"Person\",\"@name\":\"Yves Pitsch\"}],\"headline\":\"Azure Load Balancer new distribution mode\",\"datePublished\":\"2014-10-30T00:00:00+00:00\",\"dateModified\":\"2025-09-16T15:13:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/\"},\"wordCount\":682,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp\",\"articleSection\":[\"Networking\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/\",\"url\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/\",\"name\":\"Azure Load Balancer new distribution mode | Microsoft Azure Blog\",\"isPartOf\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp\",\"datePublished\":\"2014-10-30T00:00:00+00:00\",\"dateModified\":\"2025-09-16T15:13:19+00:00\",\"description\":\"We have introduced a new distribution mode called Source IP Affinity and is also known as session affinity or client IP affinity. Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers.\",\"breadcrumb\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage\",\"url\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp\",\"contentUrl\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Blog home\",\"item\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Networking\",\"item\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/category\/networking\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Azure Load Balancer new distribution mode\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#website\",\"url\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/\",\"name\":\"Microsoft Azure Blog\",\"description\":\"Get the latest Azure news, updates, and announcements from the Azure blog. From product updates to hot topics, hear from the Azure experts.\",\"publisher\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#organization\",\"name\":\"Microsoft Azure Blog\",\"url\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2024\/06\/microsoft_logo.webp\",\"contentUrl\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2024\/06\/microsoft_logo.webp\",\"width\":512,\"height\":512,\"caption\":\"Microsoft Azure Blog\"},\"image\":{\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/microsoftazure\",\"https:\/\/x.com\/azure\",\"https:\/\/www.instagram.com\/microsoftdeveloper\/\",\"https:\/\/www.linkedin.com\/company\/16188386\",\"https:\/\/www.youtube.com\/user\/windowsazure\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/#\/schema\/person\/c702e5edd662b328b49b7e1180cab117\",\"name\":\"shakir\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/9342c7c05bb16548741bc5cd3a3e3b7ee0c8e746844ad2cc582db5beb5514c6f?s=96&d=mm&r=g7664e653ea371ce16eaf75e9fa8952c4\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/9342c7c05bb16548741bc5cd3a3e3b7ee0c8e746844ad2cc582db5beb5514c6f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/9342c7c05bb16548741bc5cd3a3e3b7ee0c8e746844ad2cc582db5beb5514c6f?s=96&d=mm&r=g\",\"caption\":\"shakir\"},\"sameAs\":[\"https:\/\/azure.microsoft.com\"],\"url\":\"https:\/\/azure.microsoft.com\/en-us\/blog\/author\/shakir\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Azure Load Balancer new distribution mode | Microsoft Azure Blog","description":"We have introduced a new distribution mode called Source IP Affinity and is also known as session affinity or client IP affinity. Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/","og_locale":"en_US","og_type":"article","og_title":"Azure Load Balancer new distribution mode | Microsoft Azure Blog","og_description":"We have introduced a new distribution mode called Source IP Affinity and is also known as session affinity or client IP affinity. Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers.","og_url":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/","og_site_name":"Microsoft Azure Blog","article_publisher":"https:\/\/www.facebook.com\/microsoftazure","article_published_time":"2014-10-30T00:00:00+00:00","article_modified_time":"2025-09-16T15:13:19+00:00","og_image":[{"url":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp","type":"","width":"","height":""}],"author":"Yves Pitsch","twitter_card":"summary_large_image","twitter_creator":"@azure","twitter_site":"@azure","twitter_misc":{"Written by":"Yves Pitsch","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#article","isPartOf":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/"},"author":[{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/author\/yves-pitsch\/","@type":"Person","@name":"Yves Pitsch"}],"headline":"Azure Load Balancer new distribution mode","datePublished":"2014-10-30T00:00:00+00:00","dateModified":"2025-09-16T15:13:19+00:00","mainEntityOfPage":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/"},"wordCount":682,"commentCount":0,"publisher":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#organization"},"image":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage"},"thumbnailUrl":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp","articleSection":["Networking"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/","url":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/","name":"Azure Load Balancer new distribution mode | Microsoft Azure Blog","isPartOf":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage"},"image":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage"},"thumbnailUrl":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp","datePublished":"2014-10-30T00:00:00+00:00","dateModified":"2025-09-16T15:13:19+00:00","description":"We have introduced a new distribution mode called Source IP Affinity and is also known as session affinity or client IP affinity. Azure Load Balancer can be configured to use a 2 tuple (Source IP, Destination IP) or 3 tuple (Source IP, Destination IP, Protocol) to map traffic to the available servers.","breadcrumb":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#primaryimage","url":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp","contentUrl":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2014\/10\/SLB-5-tuple_thumb.webp"},{"@type":"BreadcrumbList","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/azure-load-balancer-new-distribution-mode\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Blog home","item":"https:\/\/azure.microsoft.com\/en-us\/blog\/"},{"@type":"ListItem","position":2,"name":"Networking","item":"https:\/\/azure.microsoft.com\/en-us\/blog\/category\/networking\/"},{"@type":"ListItem","position":3,"name":"Azure Load Balancer new distribution mode"}]},{"@type":"WebSite","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#website","url":"https:\/\/azure.microsoft.com\/en-us\/blog\/","name":"Microsoft Azure Blog","description":"Get the latest Azure news, updates, and announcements from the Azure blog. From product updates to hot topics, hear from the Azure experts.","publisher":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/azure.microsoft.com\/en-us\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#organization","name":"Microsoft Azure Blog","url":"https:\/\/azure.microsoft.com\/en-us\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2024\/06\/microsoft_logo.webp","contentUrl":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-content\/uploads\/2024\/06\/microsoft_logo.webp","width":512,"height":512,"caption":"Microsoft Azure Blog"},"image":{"@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/microsoftazure","https:\/\/x.com\/azure","https:\/\/www.instagram.com\/microsoftdeveloper\/","https:\/\/www.linkedin.com\/company\/16188386","https:\/\/www.youtube.com\/user\/windowsazure"]},{"@type":"Person","@id":"https:\/\/azure.microsoft.com\/en-us\/blog\/#\/schema\/person\/c702e5edd662b328b49b7e1180cab117","name":"shakir","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/9342c7c05bb16548741bc5cd3a3e3b7ee0c8e746844ad2cc582db5beb5514c6f?s=96&d=mm&r=g7664e653ea371ce16eaf75e9fa8952c4","url":"https:\/\/secure.gravatar.com\/avatar\/9342c7c05bb16548741bc5cd3a3e3b7ee0c8e746844ad2cc582db5beb5514c6f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9342c7c05bb16548741bc5cd3a3e3b7ee0c8e746844ad2cc582db5beb5514c6f?s=96&d=mm&r=g","caption":"shakir"},"sameAs":["https:\/\/azure.microsoft.com"],"url":"https:\/\/azure.microsoft.com\/en-us\/blog\/author\/shakir\/"}]}},"msxcm_display_generated_audio":false,"msxcm_animated_featured_image":null,"distributor_meta":false,"distributor_terms":false,"distributor_media":false,"distributor_original_site_name":"Microsoft Azure Blog","distributor_original_site_url":"https:\/\/azure.microsoft.com\/en-us\/blog","push-errors":false,"_links":{"self":[{"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/posts\/5773","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/comments?post=5773"}],"version-history":[{"count":1,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/posts\/5773\/revisions"}],"predecessor-version":[{"id":46300,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/posts\/5773\/revisions\/46300"}],"wp:attachment":[{"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/media?parent=5773"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/categories?post=5773"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/tags?post=5773"},{"taxonomy":"audience","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/audience?post=5773"},{"taxonomy":"content-type","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/content-type?post=5773"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/product?post=5773"},{"taxonomy":"tech-community","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/tech-community?post=5773"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/topic?post=5773"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/azure.microsoft.com\/en-us\/blog\/wp-json\/wp\/v2\/coauthors?post=5773"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}