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

Deploying Resources with ARM JSON Templates

There are many ways to deploy resources: using the portal, PowerShell, the CLI, the REST API, third-party tools, Azure application—the list goes on. The challenge with nearly all these tools is that they are imperative—that is, you have to explicitly say how to create the resources. If you were creating a number of resources and there was a failure, you often would not be able to just restart the script, as some resources would already exist, and it would fail. Instead, you would have to check at every stage if a resource exists, use a reference to that existing resource if it’s used elsewhere in the script, etc. What if you want to make a small change to the deployment that already exists or compare what is deployed to what you defined in the script? Using the portal or applications is prone to human error and unlikely to scale well. Yes, you can create one VM, but 100? Ouch.

Everything Is JSON

Behind the scenes, everything...