AZ-900 Microsoft Azure Fundamentals Exam

Define Azure Resource Manager (ARM)

Azure Resource Manager (ARM) serves as the central deployment and management service for all of Azure. It provides a unified management layer that allows users to create, update, and delete resources securely and consistently. Through ARM, you organize resources into resource groups based on their lifecycle, apply role-based access control (RBAC) to secure operations, and use tags and policies to enforce organizational rules.

When teams want to automate their setup, they use ARM templates, which are JSON files that implement the concept of infrastructure as code. Instead of writing a step-by-step script, you use declarative syntax to describe the desired final state of your infrastructure. This approach ensures that deployments are idempotent, meaning you can run the same template multiple times and always get the exact same results without creating duplicate resources.

ARM acts as an orchestrator that automatically manages resource dependencies and spins up resources in parallel when possible to speed up the process. This system is highly extensible, allowing you to run PowerShell or Bash deployment scripts for advanced configurations or link multiple templates together. To ensure high quality, you can use validation tools like the ARM Template Test Toolkit (arm-ttk) to verify your templates before executing them.

Understand ARM Templates

To work effectively with infrastructure as code, you must understand how ARM templates are structured. These JSON files are stored in version control systems alongside application code, which guarantees that everyone on a team deploys identical environments. This consistent structure allows teams to safely modify and scale their cloud infrastructure over time.

The basic structure of a template includes several components:

• $schema and contentVersion: Define the JSON schema version and the template's own version.
• parameters: Allow you to pass in configurable values at deployment time.
• variables: Store reusable values calculated from parameters or functions to keep code clean.
• resources: Describe the actual Azure resources to deploy and their properties.
• outputs: Return information, such as resource IDs, after the deployment is complete.

Using this structure allows for modular development where you can break a massive deployment into smaller, linked files. Before making any live changes, you can use the what-if operation to preview exactly what will change. This validation step helps prevent accidental deletions or unintended modifications in your production environments.

Deploy Resources Using ARM Templates

Deploying resources with ARM templates allows you to state exactly what resources you want, such as virtual machines or storage accounts, and let Azure handle the creation details. You author these JSON files using tools like Visual Studio Code with the Azure Resource Manager Tools extension, or the custom template editor directly in the Azure portal. Once written, these templates are saved with a .json file extension and managed in your source control system.

When you are ready to initiate a deployment, you can choose from several tools depending on your preferred workflow. You can deploy directly through the graphical interface of the Azure portal by using the custom template feature, or you can use command-line tools. If you prefer scripting, you can use the Azure CLI with deployment commands or Azure PowerShell to submit your template to the Resource Manager.

Regardless of the method you choose, the Resource Manager control plane evaluates the file, handles orchestration by ordering dependencies, and provisions resources safely. Running validation checks, such as the what-if command or the ARM Template Test Toolkit, ensures that syntax errors are caught before any real infrastructure is built. This upfront validation reduces deployment failures and saves valuable time for operations teams.

Manage Resource Dependencies and Conditions

When deploying a complex environment, some resources must exist before others can be created. Azure Resource Manager orchestrates these relationships automatically, allowing independent resources to deploy in parallel while holding back dependent resources. To define these relationships explicitly, you use the dependsOn property inside your template to tell ARM exactly which resource must complete its setup first.

In many scenarios, ARM is smart enough to infer dependencies automatically when one resource references another, meaning you do not need to link every single component manually. Allowing dependencies to cascade naturally keeps templates clean and prevents unnecessary delays during deployment. This smart ordering ensures that networks are always created before the virtual machines that connect to them.

You can also control whether a resource is created at all by using conditional deployments through the condition property. By tying this property to template parameters, you can deploy certain resources, like a database, only when specific criteria are met. This capability allows you to use a single template to manage multiple environments, such as deploying a lightweight testing environment or a fully-featured production environment.

Implement Best Practices for ARM Templates

To keep your deployment pipelines efficient and maintainable, you should implement best practices when designing ARM templates. Instead of creating single, massive files, apply modularization by breaking templates into smaller, reusable modules. You can deploy these as linked templates stored in a secure location, referencing them via uniform resource identifiers (URIs) or relative paths to keep your primary template clean.

Managing your templates in a version control system like Git ensures that all changes are tracked and peer-reviewed through branching strategies. To make your code highly reusable across different environments, leverage parameters, variables, and built-in functions rather than hard-coding values. Consistent naming conventions for resources and parameters also improve readability and make it easier for teams to collaborate.

Security is a critical best practice when dealing with infrastructure deployments. You should integrate Azure Key Vault with your templates to retrieve sensitive information like passwords, rather than hard-coding credentials into the JSON files. Additionally, if your deployment relies on deployment scripts to perform custom tasks, ensure you grant those scripts only the minimum necessary permissions and clean up any temporary credentials immediately after execution.