I've been trying to level up my Azure architecture skills and recently came across Azure Verified Modules (AVMs). Initially, I dismissed them as just simplified bicep or terraform modules with a few less steps and predefined best-practice settings. Now, I'm worried I may have misled my clients by not utilizing AVMs sooner. In my recent projects, I have built several container app solutions from scratch in bicep, but I noticed there are AVM pattern modules available that could have saved me a lot of time and money. For example, I've worked on creating numerous supporting resources like VNETs, private links, databases, and more, and there's a specific AVM for container app jobs that could've streamlined everything. Now, I'm planning to start using AVMs in my Azure projects but feel a bit behind the curve since they were just released last year. How many of you are actively using AVMs? Have they significantly changed your workflow? Are they practical, or more of a nice-to-have? I'm curious why they aren't discussed more often considering their potential benefits, especially with the Well Adopted Framework and learning resources. What's the community take on this?
1 Answer
Overall, I think the AVMs are a great initiative, especially for quickly setting up Azure environments. They aren't without their issues, though. Some modules are still buggy or overly complex, and there are times when you might want to customize them to fit specific needs better. But in many cases, they’ve made my life easier, and they’re an excellent way to speed things up!
I've had a similar experience. The mature modules are really useful, but some are still a bit rough around the edges.