Azure Bicep WHAT-IF is BROKEN!!!

EPISODE 80
In this insightful and engaging KZbin video, join me on a deep-dive journey into the world of Azure infrastructure-as-code, specifically focusing on Bicep, Azure's native Infrastructure as Code (IaC) tool. The video begins with a brief introduction to Bicep and its role in managing cloud resources in Azure.
As the main plot unfolds, I encounter a perplexing issue: Azure's What-If operation, a tool designed to preview the changes a Bicep deployment will make to Azure resources, is mysteriously ignoring a significant portion of my infrastructure. This unexpected behavior leads me into an investigative mode.
Throughout the video, I meticulously examine the Bicep files at the resource group level. I compare the files that are being acknowledged by the What-If operation with those that are inexplicably excluded. This comparison is done through a detailed walkthrough of the Bicep code, highlighting key aspects like syntax, resource declarations, and dependencies.
Despite thorough analysis and comparison, finding a definitive answer to why What-If is omitting certain resources remains elusive. I share my thought process, hypotheses, and troubleshooting steps, such as checking for syntax errors, ensuring compliance with Azure's resource management conventions, and exploring potential limitations or bugs in the What-If operation.
The video is not just about the problem but also about the approach to problem-solving in the complex world of cloud infrastructure. It offers insights into the intricacies of Bicep, the importance of understanding Azure's deployment mechanisms, and the challenges of working with declarative IaC tools.
As the video concludes, I invite viewers to join the discussion by sharing their experiences or solutions, fostering a collaborative community learning environment. The video is a must-watch for Azure enthusiasts, cloud architects, and anyone interested in Infrastructure as Code and its practical challenges.
I think this is the GitHub issue that is affecting me:
github.com/Azure/arm-template...
🔗 Important Links:
1. **Join the Azure Terraformer Community on Discord**: Stay connected, get the latest updates, and discuss with fellow Terraform and Azure enthusiasts. Click here: / discord
2. **Support My Work**: If you find this tutorial helpful and appreciate what I do, consider buying me a coffee! Your support helps me create more content like this: www.buymeacoffee.com/azterraf...
3. **Connect with Me on Social Media**: Follow me on various platforms for more tips, tricks, and Terraform insights: bento.me/markti
4. **Become an Official Azure Terraformer**: For those who want to dive deeper into the world of Terraform, join my channel for exclusive benefits. As an Azure Terraformer Code Ninja, you'll get elite access to my Terraform code reviews. For those in my inner circle, there's even a monthly virtual 1-on-1 session with me!
Join here: / @azure-terraformer
Don't forget to like, share, and subscribe for more Terraform and Azure content. Your engagement helps this channel grow and allows me to continue providing high-quality tutorials. If you have any questions or suggestions, feel free to drop them in the comments section below.
Happy Azure Terraforming! 🌍💻🚀

[@artisticcheese]

Transpile your bicep to ARM, you will probably find reference there between nested templates

[@azure-terraformer]

I think you are right!!!!

[@karlwiren7517]

Great content, would it not be possible to just create the managed identity as a resource in main and set the scope parameter directly on the resource?

[@azure-terraformer]

Sadly no because mains scope is at the subscription level

[@DrDoktor60]

Can easily get a working plan and then the deployment fails. Doh!

[@azure-terraformer]

Ikr?! When everything is ignored my plan will give me a false sense of security…then… CLANG!!!!