Ten years of notes, in reverse. The early entries are error messages I hit and fixed; the recent ones are research I couldn't find written down anywhere else.
I went looking for the capabilities only EPAC has, against the current ALZ Accelerator generation rather than the one that motivated the original comparison. The list got shorter as I looked, and what survived is not about deploying Policy resources at all.
Both routes can now draw policy content from the same ALZ Library, so the content argument is largely over. What is left is lifecycle, and the two native paths solve it by completely different mechanisms.
On 4 August I published two public repositories about the same problem: a general-purpose model knows Azure well and knows your Azure Landing Zone not at all. One is an Agent Skill that produces a workload integration assessment, the other is a repository-native set of GitHub Copilot instructions. Both hang off a machine-readable platform contract, and what they share matters more than what separates them.
The strongest argument against EPAC is that it isn’t supported. I traced the support statements in both chains: the boundary cuts through the native stack.
There are genuinely different views on how to manage Azure Policy at enterprise scale, and both approaches live under the same Azure GitHub organisation. This first part of a research series sets out why the usual tool-versus-tool comparison fails, reframes the question, and shows the Microsoft decision guidance almost nobody quotes.
For the 2025 Dutch general election I built VerkiezingsAssistent.nl, an AI assistant that let voters ask their own questions about party manifestos. The story of how the idea started, how I built it on Azure, what it cost, what I would architect differently, and why a purpose-built assistant is not the same thing as a public chatbot.
I use Google Analytics to see which posts get read. It sets cookies and sends your visit to Google, and none of it loads unless you accept. The site works the same either way, and you can change your answer from the footer of any page. The privacy statement has the detail.