Azure Enterprise Policy as Code – A New Approach

I'm the co-author and wrote the (now removed) sentence about Terraform. It is my opinion that EPAC has a more sophisticated understanding of the Policy internals and therefore applies a more granular/scalable desired state and deployment sequencing. Jono-W is correct that one could say the same about using ARM or Bicep. As stated Microsoft will continue to support ARM, Bicep and Terraform, allowing you to pick your preferred approach.

I invite you to compare the solutions available for Policy as Code and pick the one which best suits you. As Anthony already mentioned, it is foremost important that you use Azure Policy and apply it with an Infrastructure/Policy as Code approach following accepted source code control (Git) and CI/CD practices. Independent of the tool you decide on, you should be able to use the DevOps flow diagrams from EPAC.