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

Azure Templates

Azure Resource Manager is built on JSON (JavaScript Object Notation). All of the metadata about ARM resources is stored as JSON and while we talk about the portal for resource creation, as we will learn, all of the REST APIs ultimately result in resources defined via JSON, even when provisioning using PowerShell or the CLI. If you navigate to https://resources.azure.com, you can directly view the JSON for all your resources. As you may expect, you can deploy resources by creating a JSON file and deploying that directly to Azure. In fact, this is the preferred way to create resources, as using a template brings a number of key benefits:

  • The deployment is prescriptive, in that it will always deploy the same way.
  • It is declarative, meaning the end desired state is documented rather than the actual steps to perform the deployment (which would be imperative—e.g., PowerShell deployments are imperative).
  • The deployment is idempotent, which means the template can be run...
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 $19.99/month. Cancel anytime