 What are Azure Blueprints? Azure Blueprints are a declarative way to enforce some structure for our subscriptions. Now if you manage subscriptions at any scale, whether it's 10 or 100 or hundreds, very often you want to define some commonalities, how we're going to manage access and things like that to those subscriptions. So in order to do that, we can apply Azure Blueprints. They're a declarative JSON document that allow me to apply versioning to four distinct artifact types. One is role-based access control. One is resource group definitions. I can also include Azure Policy, and this actually gives me a little bit tighter control over Azure Policy if I deploy it through a blueprint because it's tied to the blueprint artifact. And finally, I can deploy resource manager templates. That means I can define controls for my, through policy. I can define controls through RBAC, through role-based assignment. And I can deploy specific resources and resource groups into my subscription in a standard way across all the subscriptions I manage or across some subset because I can apply them at the subscription level or at a management group. And if you're not familiar with management groups, it's another great thing to go take a look at. But Azure Blueprints provide me a nice, versionable artifact. I can put it in source control. I can deliver it through continuous integration and delivery, and thereby include my governance and management in my DevOps process.