Microsoft Identity | Secure DevOps with ARM and Bicep

Whether you use ARM templates or Bicep, part four of our #MicrosoftIdentity series is for you. We'll walk through how to secure your infrastructure deployments with Azure Active Directory and Key Vault. MSIdentity Series playlist: aka.ms/DevOpsLab/MSIdentitySe...
Jump to:
00:00 Welcome to the DevOps Lab
00:22 Secure DevOps with ARM and Bicep with Christos
01:23 ARM v. Bicep
03:23 Demo
Learn more:
Azure Bicep aka.ms/DevOpsLab/MicrosoftID/...
Securing sensitive values in Bicep with KeyVault aka.ms/DevOpsLab/MicrosoftID/...
ARM Templates aka.ms/DevOpsLab/MicrosoftID/...
Securing senstive values in ARM templates with Keyvault aka.ms/DevOpsLab/MicrosoftID/...
DevOps Blogs aka.ms/devopsblog
Connect:
April / theapriledwards
Christos / christosmatskas
Check out new episodes every week at aka.ms/DevOpsIsForEveryone

[@kj2w]

This is neat, but what benefit does ARM or Bicep provide if your infrastructure never gets modified after initial creation? I haven't yet encountered a program where resources are spun up every time a deployment takes place. Instead its usually been the situation of 'Well all we need is these n# of resources for this environment. once we get them created one time, were good to go.'

[@markcuello5]

HELP