Book Image

Microsoft Azure Infrastructure Services for Architects

By : John Savill
Book Image

Microsoft Azure Infrastructure Services for Architects

By: John Savill

Overview of this book

With Microsoft Azure challenging Amazon Web Services (AWS) for market share, there has been no better time for IT professionals to broaden and expand their knowledge of Microsoft’s flagship virtualization and cloud computing service. Microsoft Azure Infrastructure Services for Architects: Designing Cloud Solutions helps readers develop the skills required to understand the capabilities of Microsoft Azure for Infrastructure Services and implement a public cloud to achieve full virtualization of data, both on and off premise. Microsoft Azure provides granular control in choosing core infrastructure components, enabling IT administrators to deploy new Windows Server and Linux virtual machines, adjust usage as requirements change, and scale to meet the infrastructure needs of their entire organization. This accurate, authoritative book covers topics including IaaS cost and options, customizing VM storage, enabling external connectivity to Azure virtual machines, extending Azure Active Directory, replicating and backing up to Azure, disaster recovery, and much more
Table of Contents (18 chapters)
Free Chapter
1
Cover
2
Acknowledgments
3
About the Author
4
Introduction
17
Index
18
End User License Agreement

Connectivity

When thinking about connectivity, there are two major elements: something to place resources on (i.e., a network) and how to enable communication to that network. In this section, I will explore all the key elements related to connectivity in Azure.

Virtual Networks

Much like a network in a physical location, a virtual network is utilized in Azure as a means to group and provide connectivity between services connected to the network. Virtual networks are broken up into one or more virtual subnets to which the resources are actually connected. A virtual network is bound by both subscription and region and cannot cross those boundaries—i.e., a single virtual network cannot span regions or subscriptions. If you have multiple subscriptions using multiple regions, you must have a virtual network per region, per subscription. (However, you can connect those networks, as I will discuss later.)

The IP space chosen for the virtual network should not overlap any IP space used...