Book Image

Hands-On Networking with Azure

By : Mohamed Waly
Book Image

Hands-On Networking with Azure

By: Mohamed Waly

Overview of this book

Microsoft Azure networking is one of the most valuable and important offerings in Azure. No matter what solution you are building for the cloud, you'll fi nd a compelling use for it. This book will get you up to speed quickly on Microsoft Azure Networking by teaching you how to use different networking services. By reading this book, you will develop a strong networking foundation for Azure virtual machines and for expanding your on-premise environment to Azure. Hands-On Networking with Azure starts with an introduction to Microsoft Azure networking and creating Azure Virtual Networks with subnets of different types within them. The book helps you understand the architecture of Azure networks. You will then learn the best practices for designing both Windows- and Linux-based Azure VM networks. You will also learn to expand your networks into Azure and how to use Azure DNS. Moreover, you will master best practices for dealing with Azure Load Balancer and the solutions they offer in different scenarios. Finally, we will demonstrate how the Azure Application Gateway works, offering various layer-7 load balancing capabilities for applications. By the end of this book, you will be able to architect your networking solutions for Azure.
Table of Contents (15 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Automating the tasks


Let's automate the manual tasks that have been implemented so far. All the automated tasks will be done for performance Traffic Manager; try to figure out how to use the other types.

Creating a Traffic Manager profile using Azure PowerShell

Creating the Traffic Manager profile using PowerShell is slightly different than the portal, because with PowerShell you need to specify some additional configurations. You can do so by running the following cmdlet:

New-AzureRmTrafficManagerProfile -Name PacktProfile -ResourceGroupName PacktPub -TrafficRoutingMethod Performance -RelativeDnsName Packt -Ttl 30 -MonitorProtocol HTTP -MonitorPort 80 -MonitorPath "/"

You can see that there is Name and RelativeDnsName. The difference between them is that the Name is the displayed name for the Traffic Manager, but RelatvieDnsName is the portion of the hostname that makes the following FQDN: http://packt.trafficmanager.net

With respect to the other parameters, you saw them earlier in the Traffic...