Summary
Your website's development team wanted to deploy its changes within a non-production environment. The team wanted to remove the risk of its changes accidentally affecting the customers who access the production website.
In this module, you learned how to work with multiple environments in a deployment workflow. You generalized your deployment process into a reusable workflow, and you used the file as a called workflow for both your test and production environments. You also handled the differences between your environments by storing Bicep parameter values in parameter files, inputs, and secrets.
Now that your workflow deploys to multiple environments, you have higher confidence that the changes you make to your Bicep files will deploy successfully to a non-production environment. And will be tested before they progress to your production environment.