The Microsoft Azure Traffic Manager provides global DNS load balancing methods of distributing internet traffic among two or more endpoints (for example: Virtual Machines or WebApps ) on a different cloud services that could be located on a different regions, all accessible with the same URL, in one or more Microsoft Azure datacenters around the world. In this session I will explain about the different methods, I will show you how to configure the Traffic Manager and I will present a little demo. At the end of this session you'll be able to provide better Performance, Redundancy and HA to your servers and/or web applications by using the Microsoft Azure Traffic Manager.

1. © Copyright SELA Software & Education Labs Ltd. | 14-18 Baruch Hirsch St Bnei Brak, 51202 Israel | www.selagroup.com
SELA DEVELOPER PRACTICE
DECEMBER 20-24, 2015
Ido Katz, Microsoft Azure MVP
Senior Cloud Infrastructure Consultant
Sela Group
Azure Traffic Manager
Mail: idok@sela.co.il
Blog: blogs.microsoft.co.il/idokatz
Twitter: @send2katz

2. Agenda
Moving to the cloud
Some basics
Why do we need Load Balancer
What is Azure Traffic Manger
Round Robin Profile
Failover Clustering Profile
Demo
Performance Profile
Demo
Other Cloud Solutions
Cloud-based CDN/ADCs

3. Moving to the cloud:

4. Some Basics:
Cloud Service:
• Grants a public IP and DNS per CS.
• Contains your Virtual Machines(VMs)
Virtual Machine:
• Hosts your service/application
• Multiple VMs can be under one cloud service.

5. Why do we need Load Balancer
Load balancing, by its very nature, is the solution
for more than one problem such as:
1. Traffic Redundancy
2. BCP Failover
3. User Experience

6. What is Azure Traffic Manager
Three Load Balancing Algorithms
Performance, Round Robin, Fail Over
Map your domain name to yourservice.trafficmanager.net with CNAME
contoso.com -> contosotm.trafficmanager.net
Map cloud service URLs in global data centers to Traffic Manager Profile.
contosoeast.cloudapp.net
contosowest.cloudapp.net
Built in HTTP Health Probes for High Availability
Can be used outside Azure (For example: Your “On Premise”)

7. Round Robin Profile
Traffic Manager returns IPs in a round robin fashion regardless of client location.

8. Failover Clustering Profile
X
Traffic Manager always returns the IP address of the primary cloud service
unless it fails a health check.

9. Demo
Failover Clustering

10. Performance Profile
Traffic Manager determines fastest route for the client and returns IP for the
appropriate cloud service.

11. Demo
Performance

12. PowerShell Demo
Add the azure account to PowerShell
Add-azureaccount
Choose the correct subscription
Select-AzureSubscription

13. PowerShell Demo
Create a new azure traffic manager with the following
properties:
Name: SDP-TM-Performance
Domain Name: SDP-TM-Performance.trafficmanager.net
Load Balancing method: Performance
Monitor Protocol: Http
Monitor Port: 80
Relative path to monitor: /iis85.jpg
TTL: 30 Seconds

14. PowerShell Demo
New-AzureTrafficManagerProfile -Name "SDP-TM-
Performance" -DomainName "SDP-TM-
Performance.trafficmanager.net" -
LoadBalancingMethod "Performance" -
MonitorProtocol "Http" -MonitorPort 80 -
MonitorRelativePath "/iis85.jpg" -Ttl 30

15. PowerShell Demo
Create a variable named "TMProfile" to contain the information
about the Traffic manager profile we created.
$TMProfile = Get-AzureTrafficManagerProfile -
name "SDP-TM-Performance"

16. PowerShell Demo
Use the variable in order to add our first and second endpoints to
the traffic manager, plus saving them using the "Set-
AzureTrafficManagerProfile" cmdlet
Add-AzureTrafficManagerEndpoint -
TrafficManagerProfile $TMProfile -DomainName "SDP-
EUS-CS01.cloudapp.net" -Status "Enabled" -Type
"CloudService" | Set-AzureTrafficManagerProfile
Add-AzureTrafficManagerEndpoint -
TrafficManagerProfile $TMProfile -DomainName "SDP-
WE-CS01.cloudapp.net" -Status "Enabled" -Type
"CloudService" | Set-AzureTrafficManagerProfile

17. PowerShell Demo
How it all looks:
New-AzureTrafficManagerProfile -Name "SDP-TM-Performance" -
DomainName "SDP-TM-Performance.trafficmanager.net" -
LoadBalancingMethod "Performance" -MonitorProtocol "Http" -
MonitorPort 80 -MonitorRelativePath "/iis85.jpg" -Ttl 30
$TMProfile = Get-AzureTrafficManagerProfile -name "SDP-TM-
Performance"
Add-AzureTrafficManagerEndpoint -TrafficManagerProfile $TMProfile
-DomainName "SDP-EUS-CS01.cloudapp.net" -Status "Enabled" -Type
"CloudService" | Set-AzureTrafficManagerProfile
Add-AzureTrafficManagerEndpoint -TrafficManagerProfile $TMProfile
-DomainName "SDP-WE-CS01.cloudapp.net" -Status "Enabled" -Type
"CloudService" | Set-AzureTrafficManagerProfile

18. Other Clouds Solution:
AWS
• No single solution – combination of Route 53(DNS) and Elastic load balancing.
• Cannot be used for services not covered by AWS
Google Cloud
• No actual solution: Http(s) Load Balancing or Region Load balancing.
• Cannot be used for services not covered by Google
Cloud-based CDNs/ADCs:
• Cloudflare – Performance based only. No actual load balancing
• Incapsula – Failover, performance, Round-robin
• Akamai – Failover, performance, weighted

19. In this session we learned:
1. You learned the basics of the cloud.
2. What is Load Balancer
3. What is Azure Traffic Manager
4. What kind of profiles I can use with Traffic
Manager.
5. What is the differences between other cloud
service providers in terms of load balancing.

20. Online documentation
Channel 9 -
https://channel9.msdn.com/Blogs/Windows-
Azure/How-Azure-Traffic-Manager-WorksMSDN
Demos -
https://channel9.msdn.com/Shows/Edge/Edge-
Show-86-Windows-Azure-Traffic-Manager-Demos
Microsoft Azure -
https://azure.microsoft.com/en-
us/documentation/articles/traffic-manager-
overview/

21. Questions