Learn Live: Automate your Azure deployments by using Bicep and GitHub

6:00 du. - 7:30 du. (UTC)

Create an automated workflow in GitHub Actions that securely deploys resources to Azure from Bicep code. Configure your workflow to run on a schedule or when your configuration changes. In this episode, you will: Automate Bicep deployments by using a workflow in GitHub Actions Set up a workload identity to authenticate a workflow to Azure Select an appropriate workflow trigger and set of tasks for a Bicep deployment

6:00 du. - 7:30 du. (UTC)

Workload identities enable your deployment workflows to authenticate securely with Azure without you managing any passwords, keys, or secrets. In this module, you'll learn what workload identities are, how they work, and how to create them. You'll also learn how to grant them permission to your Azure resources so that your workflows can deploy your Bicep files. In this episode, you will: Explain what a workload identity is and describe three types of workload identities: service principals, managed identities, and federated credentials Create a workload identity and link it to a GitHub Actions deployment workflow Configure the appropriate authorization for a workload identity to deploy Azure resources

6:00 du. - 7:30 du. (UTC)

Validate and test your Bicep code in your deployment workflow. You'll use linting, preflight validation, and the what-if operation to validate your Azure changes before you deploy, and you'll test your resources after each deployment. In this episode, you will: Add Bicep code linting during continuous integration Add preflight deployment validation during build or release jobs Add what-if checks, including manual approval steps Verify the configuration of the deployed environment

6:00 du. - 7:30 du. (UTC)

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. In this episode, you will: Deploy Bicep files to multiple Azure environments from a workflow Use reusable workflows to avoid repetition Use and secure parameters for each environment

6:00 du. - 7:30 du. (UTC)

Create a unified workflow to deploy your entire environment. You'll add build jobs to your workflow, and use workflow artifacts and Bicep outputs to publish applications, databases, and blobs. In this episode, you will: Deploy Azure infrastructure, applications, database scripts, and storage blobs from a single workflow Use workflow scripts and workflow actions to perform deployment steps Use workflow artifacts to publish compiled files for your deployment workflow jobs to use Pass data from your Bicep files to other deployment steps by using outputs

6:00 du. - 7:30 du. (UTC)

Add checks to pull requests that run automatically during your code reviews. Run the Bicep linter on your code, and deploy the resources to a temporary environment to enable further automated and manual testing. In this episode, you will: Run automatic checks during a pull request Determine how you want to create ephemeral environments in your Azure environment Create ephemeral environments within pull requests

6:00 du. - 7:30 du. (UTC)

Publish Azure template specs and Bicep modules by using a deployment workflow. Automatically validate and add versioning to your reusable Bicep code. In this episode, you will: Publish Bicep modules to a private registry from a GitHub Actions workflow Publish Bicep files to a template spec from a GitHub Actions workflow Automatically add version numbers to your modules and template specs

6:00 du. - 6:30 du. (UTC)

Plan how you'll harden and help secure your Azure environment, along with the controls to apply to your configuration changes and deployments. Require your infrastructure be defined as code, and protect your environment against manual changes. In this episode, you will: Plan an Azure deployment strategy for multiple environments Harden and help secure Azure DevOps, GitHub, and a deployment pipeline Harden and help secure an Azure environment to ensure that changes are made through a controlled process