AVM External Community Call - 6th February 2025

[jeanchg]

The Azure Verified Modules team will host our next quarterly Community Call on February 6th, at 09:00 CET, showcasing all of the great work the community and the team have done, alongside important updates, guest speakers and a community Q&A.

To sign up for this next occurrence, please use: Teams Webinar link

Please leave comments below on topics you'd like to get covered!

High level agenda:

• ALZ TF & Bicep rebuild to AVM
• Child Modules
• Website Updates
• Guest speakers (MVPs, Partner, Customer and/or PG teams)
• Q&A / Open discussion: attendees can ask questions, share experiences/stories, provide feedback and suggestions

[PbALpi7xEX]

Topics around migrating to or refactoring existing terraform (production) to AVM modules

[PbALpi7xEX]

If we register, but cannot attend live, will a recording link be provided to view at a later time?

[jtracey93]

Hey @PbALpi7xEX,

Yes will be uploaded to YouTube and here https://azure.github.io/Azure-Verified-Modules/resources/community/

[FV1F167]

Timeline on GA availability of AVM-Terraform-Modules - most of them are not production ready in terms of maturity but other official modules have been deprecated in the meantime.

[Shiro-2000]

Differences between Azure CAF (https://github.com/Azure/terraform-azurerm-caf-enterprise-scale) and the new AVM.
Is this supposed to be a replacement for the Azure CAF? If so, are there plans to migrate away from CAF to AVM?

[jtracey93]

Timeline on GA availability of AVM-Terraform-Modules - most of them are not production ready in terms of maturity but other official modules have been deprecated in the meantime.

@FV1F167 see https://azure.github.io/Azure-Verified-Modules/resources/faq/#can-avm-module-be-used-in-production-before-it-is-marked-as-ga--v10. v0.1.0 does not mean not GA or supported or ready for production - AVM modules are all ready for prod use and are being used so already in prod 👍

Much like Terraform & Bicep neither of them were v1.0.0 for a long time but were still used in production. TF was 0.15.x for years before it went to v1.0.0 but it was still good for prod and supported. Bicep is still v0.33.x something but has been supported in prod since v0.3.0

[jtracey93]

Differences between Azure CAF (https://github.com/Azure/terraform-azurerm-caf-enterprise-scale) and the new AVM. Is this supposed to be a replacement for the Azure CAF? If so, are there plans to migrate away from CAF to AVM?

@ELoTrash we will 100% be talking about this. but you may want to checkout the blog we posted today https://techcommunity.microsoft.com/blog/azuretoolsblog/announcing-general-availability-of-terraform-azure-verified-modules-for-platform/4366027

Also join the ALZ community call https://aka.ms/alz/communitycall

[tonyskidmore]

I came across the issue [AVM Module Issue]: logAnalyticsDestinationType is not set correctly for Diagnostic settings #55 which was closed quoting the AVM specification, yet the problems persists and it looks like it might be a wider problem, based on comments from the raiser of the issue.

I guess my query would be twofold:

1. Could this issue be reviewed as an example?
2. What would be the best mechanism for further follow up by the core AVM team if it was thought that more action was needed?

I don't expect individual issues to be gone through as part a community call but it is more of a general approach to what to do if an issue has been closed but doesn't solve the underlying problem.

[Shiro-2000]

Differences between Azure CAF (https://github.com/Azure/terraform-azurerm-caf-enterprise-scale) and the new AVM. Is this supposed to be a replacement for the Azure CAF? If so, are there plans to migrate away from CAF to AVM?

@ELoTrash we will 100% be talking about this. but you may want to checkout the blog we posted today https://techcommunity.microsoft.com/blog/azuretoolsblog/announcing-general-availability-of-terraform-azure-verified-modules-for-platform/4366027

Also join the ALZ community call https://aka.ms/alz/communitycall

Thanks, I have signed up for the call. It appears from the link you posted that this is a replacement for the CAF, does Azure plan on doing a demo of how to deploy the new AVM compared to the CAF? Will there be a demo for existing enterprises to switch from CAF to AVM?
Will there be tools to migrate the CAF to AVM from a terraform perspective? State management is going to be a difficult problem when transitioning (if a transition is suggested from Microsoft).

[jtracey93]

@Shiro-2000 please join the calls and we will be covering all of this and letting you know what you need to know

[gnfsdybvik]

I'm not able to attend the CC, but I have a rather fundamental question with AVM.
Two years ago when we considered which tech stack to use when selecting an IaC tool, we considered Bicep, Pulumi and Terraform. We selected bicep because when deploying to Azure only we would not need to wait for things to be implemented in the product (like Pulumi and Terraform). Bicep was updated simultaneously as Azure itself. After a while we found that bicep was hard to work with since it was too many options to choose from and connecting the resources based on best practices was hard. So people went looking for modules which implemented best practices. Then CARML and later AVM came along. Which was great. But now we're back at the same level as the other tools like Pulumi and Terraform, aren't we? We have to wait for AVM to implement the updates in Azure. I haven't looked at Pulumi and Terraform lately and how they have evolved, but has bicep lost the advantage of being up to date with Azure? Any thoughts on this?

[jeanchg]

Recording now available here.
Huge thank you to all the speakers and for everyone joining today!

[RoyKimYYZ]

I would have liked to join but the 3am EST time doesn't work well. For the next quarterly, can there be EMEA and North America friendly community calls?

[jeanchg]

@RoyKimYYZ absolutely, we alternate each quarter to accommodate time zones, next one will be Americas friendly!

[RoyKimYYZ]

[like] Roy Kim reacted to your message:

…

________________________________