In the evolving landscape of cloud governance and infrastructure as code, Azure offers several tools to streamline and standardize deployments.

Historically, there were Azure Blueprints - a promising way to declare and deploy a standard set of resources across various scopes and ensure compliance and consistency - that never reached GA status. Blueprint successors are Template Specs and Deployment Stacks, both Generally Available and supported.

In this blog post, we will do both conceptual and practical comparison of these tools with the goal to answer the following questions:
- Is there a feature parity between Blueprints and Specks & Stacks? And if not, what is the delta?
- What steps do I need to take to migrate away from Blueprints by leveraging the new tools?
- Can I combine Template Specs with Bicep modules?
- Bonus: Is there any correlation between Azure Deployment Stacks and newly announced Terraform Stacks?