Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Azure Infrastructure Services for Architects

You're reading from   Microsoft Azure Infrastructure Services for Architects Designing Cloud Solutions

Arrow left icon
Product type Paperback
Published in Oct 2019
Publisher Wiley
ISBN-13 9781119596578
Length 448 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
John Savill John Savill
Author Profile Icon John Savill
John Savill
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

1. Cover FREE CHAPTER
2. Acknowledgments
3. About the Author
4. Introduction
5. Chapter 1 The Cloud and Microsoft Azure Fundamentals 6. Chapter 2 Governance 7. Chapter 3 Identity 8. Chapter 4 Identity Security and Extended Identity Services 9. Chapter 5 Networking 10. Chapter 6 Storage 11. Chapter 7 Azure Compute 12. Chapter 8 Azure Stack 13. Chapter 9 Backup, High Availability, Disaster Recovery, and Migration 14. Chapter 10 Monitoring and Security 15. Chapter 11 Managing Azure 16. Chapter 12 What to Do Next 17. Index
18. 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime