Improve your security with Dynamic Provider Credentials for Terraform Cloud and Azure

Terraform Cloud and Azure | Hands-on Tutorial | Terraform
Dynamic provider credentials in Terraform Cloud automates the creation of short-lived credentials for access to Azure. This eliminates the risk and effort involved in handling and rotating static credentials for Terraform runs.
Using static credentials in your workspaces to authenticate providers presents a security risk, even if you rotate your credentials regularly. Dynamic provider credentials improve your security posture by letting you provision new, temporary credentials for each run. This capability is available for all tiers of Terraform Cloud and it's also available now in Terraform Enterprise.
▬▬▬▬▬▬ TIMESTAMPS ⌚ ▬▬▬▬▬▬
0:52 - Challenges with static credentials
3:06 - What are dynamic provider credentials?
4:23 - Demo: bootstrap the trust relationship
6:48 - Demo: workspace configuration
8:14 - How the process works
9:04 - End result and summary
▬▬▬▬▬▬ WANT TO LEARN MORE? 🚀 ▬▬▬▬▬▬
🔗Sign up for Terraform Cloud for free: app.terraform.io/public/signu...
🔗Dynamic provider credentials now generally available for Terraform Cloud: www.hashicorp.com/blog/dynami...
🔗Terraform Provider Documentation: developer.hashicorp.com/terra...
🔗Free Hands-on tutorial: Authenticate Providers with Dynamic Credentials: developer.hashicorp.com/terra...
🔗Setup examples for Azure: github.com/hashicorp/terrafor...
👋Connect with April on Twitter - / theapriledwards
👋Connect with April on LinkedIn - / azureapril
👋 Connect with Dan on Twitter: / vdanbarr
👋Connect with Dan on LinkedIn: / vdanbarr
👋Connect with HashiCorp on Twitter: / hashicorp
👋Connect with HashiCorp on LinkedIn: / hashicorp
👋Connect with HashiCorp on RUclips: / @hashicorp
🙏Please like and subscribe ✔️ aka.ms/DevOpsLab
#IaC #infrastructureascode #DevOps #Azure #Learning #Cloud #devopstutorial @MicrosoftDeveloper @MicrosoftReactor ​

[@acodersjourney]

Thanks for being a reliable source of knowledge.

[@koodauskanava9096]

Do you need to specify claim so exact, or can you just define terraform cloud organization and maybe project? So all workspaces in certain project can use the client id/app reg? How does this scale if one have 1000 workspaces? Do you need to create 1000 app regs with claims to each workspace?