---
title: "Comment by Ash Roberts on \"Traffic Manager vs Load Balancer in Azure\" | Hashnode"
description: "Love your analogy distinguishing the two. To also note, Traffic manager is a solution for inter-regional connectivity. Where as the load balancer is specific to"
url: "https://hashnode.com/posts/traffic-manager-vs-load-balancer-in-azure/63fd9b234b02ec04b4dbf39d/comment/6402866b6cc7b7a22094a794"
---

[Discussion](https://hashnode.com/posts/traffic-manager-vs-load-balancer-in-azure/63fd9b234b02ec04b4dbf39d)

Comment [Traffic Manager vs Load Balancer in Azure](https://hashnode.com/posts/traffic-manager-vs-load-balancer-in-azure/63fd9b234b02ec04b4dbf39d)

[Ash Roberts](https://hashnode.com/@SwitchITUp)

[Mar 3, 2023](https://hashnode.com/posts/traffic-manager-vs-load-balancer-in-azure/63fd9b234b02ec04b4dbf39d/comment/6402866b6cc7b7a22094a794)

Love your analogy distinguishing the two.

To also note, Traffic manager is a solution for inter-regional connectivity. Where as the load balancer is specific to one region.

In your example you could just have front end public IP or IP prefix on the LB.

But I understand this is an example to clarify between the two. In real world context your traffic manager would punt traffic between multiple load balancers across Azure or even on-prem regions (banking branches)

Nice article!
