Manage multiple environments by using Bicep and GitHub Actions
Deploy your Bicep code to multiple environments to improve the quality of your deployments. Use reusable workflows to reduce code duplication, and set parameter values for each environment.
Learning objectives
After completing this module, you'll be able to:
- Deploy Bicep files to multiple Azure environments from a workflow
- Use reusable workflows to avoid repetition
- Use and secure parameters for each environment
Prerequisites
You should be familiar with using:
- Bicep, including creating and deploying basic files, parameter files, preflight validation, and the what-if operation.
- Azure, including the Azure portal, subscriptions, resource groups, and resources.
- Basic Git commands, including cloning, committing files, and pushing changes to GitHub.
- Workflows through GitHub Actions, including jobs and secrets.
To work through the exercises in the module, you'll need:
- An Azure account that can create resource groups, Microsoft Entra applications, and service principals.
- A GitHub account.
You'll also need the following installed locally:
- Visual Studio Code
- The Bicep extension for Visual Studio Code
- The latest Azure CLI tools or the latest Azure PowerShell version
- Git