Azure Blueprints

I have talked about a lot about resources and the settings available to help manage your environment and ensure governance. Attempting to manually assign all these different resources in the right combinations based on the type of subscription would be very difficult, prone to error, and hard to assess actual compliance.

Azure blueprints bring together several key governance artifacts and combine them into a declarative, pro-active resource that can be applied to cloud environments—i.e., a subscription. Think of it as a foundational scaffold of (potentially) minimum governance that meets the organization’s requirements and which can be expanded and built on as required. Using a blueprint quickly brings a subscription into a governed state. The goal would be to define blueprints for your various sets of governance requirements, perhaps based on type of environment (i.e., development and production), and then apply the appropriate blueprint as new subscriptions...