You're reading from Azure Architecture Explained A comprehensive guide to building effective cloud solutions

Product type Paperback

Published in Sep 2023

Publisher Packt

ISBN-13 9781837634811

Length 446 pages

Edition 1st Edition

Tools

Azure

Concepts

Cloud Computing

Authors (3):

Brett Hargreaves

David Rendón

MJ Parker

View More author details

Table of Contents (20) Chapters

Preface

1. Part 1 – Effective and Efficient Security Management and Operations in Azure

2. Chapter 1: Identity Foundations with Azure Active Directory and Microsoft Entra FREE CHAPTER

3. Chapter 2: Managing Access to Resources Using Azure Active Directory

4. Chapter 3: Using Microsoft Sentinel to Mitigate Lateral Movement Paths

5. Part 2 – Architecting Compute and Network Solutions

6. Chapter 4: Understanding Azure Data Solutions

7. Chapter 5: Migrating to the Cloud

8. Chapter 6: End-to-End Observability in Your Cloud and Hybrid Environments

9. Chapter 7: Working with Containers in Azure

10. Chapter 8: Understanding Networking in Azure

11. Chapter 9: Securing Access to Your Applications

12. Part 3 – Making the Most of Infrastructure-as-Code for Azure

13. Chapter 10: Governance in Azure – Components and Services

14. Chapter 11: Building Solutions in Azure Using the Bicep Language

15. Chapter 12: Using Azure Pipelines to Build Your Infrastructure in Azure

16. Chapter 13: Continuous Integration and Deployment in Azure DevOps

17. Chapter 14: Tips from the Field

18. Index

Why subscribe?

19. Other Books You May Enjoy

Bicep file structure

Bicep has its own syntax and structure for defining Azure resources in a simple and readable manner. The basic structure of an Azure Bicep file consists of the following:

Metadata: A JSON object that defines the version of the Bicep language and any other metadata
Variables: A section where you can declare variables to be used in the deployment
Parameters: A section where you can define the input parameters required to deploy the resources
Resources: A section where you can define the Azure resources you want to deploy
Outputs: A section where you can define outputs that can be used to refer to the values of resources created during deployment

Figure 11.2 – A Bicep file that creates a storage account

Similar to ARM templates, you can define parameters, variables, resources, child resources, extensions, and even dependencies in your Bicep file. More advanced functionality, such as loops, conditions...