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

What Is Governance?

I’m going to answer that question eventually, but not right away. Instead, I want to explore how things have evolved so that we now need a whole chapter on governance in a book that is all about infrastructure in Azure. The best way is to go back to creating services on premises.

Many eons ago (well, a few years at least), the only way to host applications was to run them in your datacenter. This required significant investment, as facilities were required to hold large, expensive servers and their supporting infrastructure components, such as storage and networking. As applications moved from running on dedicated hardware to virtual machines, a problem manifested, as it now became easier to create resources, which resulted in virtual machine sprawl. Without the right guardrails, VMs would be created. There was little control or stewardship of VMs, and there was no way to track if VMs were still needed or even being used. On the business side, there was often...