How Can We Simplify Bicep File Creation for Azure?

Our software development team is trying to streamline the process of creating Bicep files for Azure deployments. We're currently dealing with several challenges like manually adhering to Azure policies, following strict naming conventions that often lead to errors, and relying heavily on Azure Verified Modules and internal templates. These manual processes are cumbersome and hinder our efficiency. We're looking for ways to automate the generation of Bicep files that can conform to our Azure policies and naming conventions based on simple high-level requests (like "create a key vault"). We're particularly interested in solutions like Azure AI Studio, GitHub Copilot, or any other alternative approaches that could help us tackle this issue. Any suggestions would be greatly appreciated!