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
About the Author
End User License Agreement

Naming Conventions

Most organizations have some kind of naming convention for their operating system instances. These typically include some kind of location identifier, perhaps a company identifier (to protect against future organizational mergers), a service type identifier, and then some kind of instance number. For example, I might use the following for the first (01) domain controller (DC) in Dallas (DAL) for my SavillTech (SAV) organization:


Naming is even more important when leveraging Azure resources, which can be in many regions and of many different types. Also remember that some resources have different requirements about what is supported as part of the name. In the cloud, the resources may include the type of resource in addition to the environment plus the types of information previously covered. The organization should pick a standard set of codes for the various Azure regions. Microsoft has detailed guidance on possible naming approaches to be used at: