Understanding Azure policies
Your IT strategy and governance rules will define ways of working and what should and should not be allowed in your solutions.
An example may be for all resources to be tagged with a cost center so that the associated costs can be billed back to a product owner. Another example could be a requirement to send all diagnostics logs to a centralized management workspace for use by monitoring and security teams.
Whatever the rule, you need some way to either enforce it or report that a component does not implement it – that is, that it is non-compliant. This could be performed manually, and in a traditional on-premise environment, this might be the only option. But when building enterprise-wide systems, manual checks and balances do not scale easily; therefore, an automated method is preferable.
With Azure Policy, we can define and codify the rules of the system in JSON policy definitions. In contrast, authentication and authorization controls such...
