Infrastructure As Code with Azure Bicep (Nwodo, Adora)（Z-Library）

【One-Line Pitch】 A hands-on guide to writing, deploying, and troubleshooting Azure infrastructure with Bicep, Microsoft's domain-specific language for Infrastructure as Code. Best for cloud engineers, DevOps practitioners, and developers who already know Azure basics and want to move beyond hand-clicked portals or unwieldy ARM JSON. 【Book Arc】 - **Opening (~0%–10%)**: Frames why Infrastructure as Code matters — automation, idempotency, consistency — and positions Bicep against ARM templates as a cleaner, more readable alternative. - **Early (~10%–32%)**: Gets you running: installing the Bicep CLI and VS Code extension across platforms, then the core building blocks of a Bicep file — resources, scopes, dependencies, and reusable modules. - **Middle (~32%–48%)**: Moves into real deployment work: defining resources (CMS-style examples), the `existing` keyword, incremental vs. complete modes, previewing with `what-if`, and debugging failures via CLI, PowerShell, and the portal. - **Late (~48%–70%)**: Parameterizes templates — `param` declarations, defaults, `@secure()` decorators, variables for dynamic config, and `.bicepparam` files for environment-specific values. - **Ending (~70%+)**: Extends into Bicep's expression surface — operators, conditions, loops, and the function library (string, array, CIDR, date, lambda, scope, and more) — plus best practices for variables and parameters. 【Key Takeaways】 - **Idempotency is the conceptual backbone of IaC** (Opening): Bicep reconciles desired vs. actual state, so re-applying a template is safe and predictable rather than duplicative. - **Bicep compiles to ARM JSON** (Early): You author in a concise DSL, but the generated template is standard ARM — meaning existing tooling and knowledge still apply. - **Modules are the reuse mechanism** (Early): Encapsulate common patterns (e.g., app service plan + storage + function app) into parameterized modules and compose them across projects. - **Dependencies are mostly implicit** (Early): Bicep infers ordering from property references; `dependsOn` is the explicit escape hatch when you need control. - **Four deployment scopes structure everything** (Early): resourceGroup, subscription, managementGroup, and tenant — each with its own `az deployment …` command form. - **Preview before you deploy** (Middle): `what-if` plus incremental vs. complete modes let you see what will change or be deleted before committing. - **Parameters and parameter files scale configuration** (Late): `.bicepparam` files replace sprawling if-statements for per-environment values, with `@secure()` protecting secrets. - **The function library is where Bicep gets expressive** (Ending): Operators, loops, and categorized functions (string, array, CIDR, lambda, scope) turn templates into real logic. 【Reading Tips】 - **Skim the install chapter** (Early) if your environment is already set up — it's step-by-step CLI/VS Code setup you can return to as reference. - **Deep-read the scopes, dependencies, and modules sections** (Early): these are the concepts that trip up newcomers and cause most deployment confusion. - **Treat the function reference** (Ending) as a lookup, not a linear read — bookmark the categories and return when you need a specific function. - **Type along with the CMS and serverless examples** (Middle): the deployment and troubleshooting workflow is best learned by running `what-if` and reading real errors. - **Carry forward the idempotency mental model** (Opening): it explains why Bicep behaves the way it does in every later chapter. 【Coverage Limits】 This guide is synthesized from stratified excerpts covering roughly the first half to two-thirds of the book; later chapters on advanced functions and best practices are only partially represented, and specific chapter titles beyond those shown are not covered.