Book Image

Azure Architecture Explained

By : David Rendón, Brett Hargreaves
Book Image

Azure Architecture Explained

By: David Rendón, Brett Hargreaves

Overview of this book

Azure is a sophisticated technology that requires a detailed understanding to reap its full potential and employ its advanced features. This book provides you with a clear path to designing optimal cloud-based solutions in Azure, by delving into the platform's intricacies. You’ll begin by understanding the effective and efficient security management and operation techniques in Azure to implement the appropriate configurations in Microsoft Entra ID. Next, you’ll explore how to modernize your applications for the cloud, examining the different computation and storage options, as well as using Azure data solutions to help migrate and monitor workloads. You’ll also find out how to build your solutions, including containers, networking components, security principles, governance, and advanced observability. With practical examples and step-by-step instructions, you’ll be empowered to work on infrastructure-as-code to effectively deploy and manage resources in your environment. By the end of this book, you’ll be well-equipped to navigate the world of cloud computing confidently.
Table of Contents (20 chapters)
1
Part 1 – Effective and Efficient Security Management and Operations in Azure
5
Part 2 – Architecting Compute and Network Solutions
12
Part 3 – Making the Most of Infrastructure-as-Code for Azure

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

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...