While the introduction of RBAC roles for key vaults is already written in history the support of this from the terraform module azurerm_key_vault has been lacking...
ALM by Erick Segaar
During the community call in September, #Bicep introduced the local registry to share your modules internally. This is a really important feature but where does it differ from existing Template Specs and how can you leverage this in an Enterprise to support your teams into easily adopting your latest changes with just a PR. Combining different tools and principles in enabling an important shift left from deployment to compile time.
Within software development, it is common practice to create shared-code libraries. This helps you maintain your code better and reuse it in other places without the nasty copy-paste pattern. This can be done by simply adding a project reference or an artifact repository like NuGet. However, with Azure functions, this is a bit cumbersome and not well documented on how to achieve this.
When using #Azure #functions you need an underlying storage account to accommodate for a storage blob for the storage of your code files and storage tables for your durable functions. However, when you use #Terraform to deploy your infrastructure there is a strange default behavior you need to be aware of.
When you need to gather data from an Azure Storage account like the Exported Application Insights data. Then you need an addon for it, such as...
When a preview feature goes into General Availability some functionality will change. This is my research of the Azure activity-logs and where to find the settings