bicep-iac-azd

To scaffold Bicep templates, describe your target Azure deployment like Container Apps or App Service, and the skill generates modular Bicep infrastructure files with best practices for naming and security applied automatically.

Configuring azure.yaml for an azd project involves defining your target Azure services, and this skill generates the required configuration file alongside Bicep modules to enable end-to-end deployments.

Yes, you can use azd to deploy to Azure Container Apps and Functions by generating the necessary Bicep templates and azd configurations, which include guidance for service-specific setup and security.

Generated Bicep infrastructure includes RBAC and security best practices, ensuring that naming conventions and access controls are properly configured within the templates for secure Azure deployments.

The best way to create modular Bicep infrastructure for Static Web Apps is to use azd configurations that scaffold reusable Bicep modules, enforcing consistent naming and security practices across your deployment.