Search Azure terms

Management and Governance premium Bicep Bicep is a domain-specific language for declaratively deploying Azure resources through Azure Resource Manager. Infrastructure as code fundamentals 5 commands Aliases: Azure Bicep Quick peek Open full term page

Management and Governance premium Bicep private registry A Bicep private registry is an Azure Container Registry used to publish and share organization-owned Bicep modules. Bicep fundamentals 6 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep build Bicep build is the Bicep CLI command that compiles a Bicep file into an Azure Resource Manager JSON template, optionally writing output to a file or stdout. Bicep intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep config Bicep config is the optional bicepconfig.json file that customizes Bicep behavior such as analyzers, linter rules, module aliases, and registry credentials. Bicep fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep decompile Bicep decompile converts Azure Resource Manager JSON templates into Bicep files that can be reviewed, refactored, and redeployed. Bicep intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep existing resource A Bicep existing resource declaration references a resource that already exists instead of deploying it again. Bicep fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep output A Bicep output returns values from a deployment so other deployments, scripts, pipelines, or operators can use them. Bicep fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep public registry The Bicep public registry provides publicly available Bicep modules that can be referenced from Bicep files, including Azure Verified Modules through the br/public alias. Bicep fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep conditional resource A Bicep conditional resource is a resource or module declaration that deploys only when its if expression evaluates to true. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep decorator A Bicep decorator adds metadata, validation, constraints, or deployment behavior to a declaration such as a parameter, resource, module, output, type, variable, or function. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep linter The Bicep linter checks Bicep files for syntax errors and best-practice rule violations during development and CI. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep loop A Bicep loop uses for syntax to create multiple resources, modules, variables, properties, or outputs from a collection or range. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep module A Bicep module is a reusable building block for deployments. Put a common pattern, such as a storage account, network, or policy setup, in its own file, then call it from another Bicep file with parameters and outputs instead of copying code everywhere. Bicep intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep parameter file A Bicep parameter file is where you put values that change by environment, such as names, SKUs, regions, and flags. The main Bicep file stays reusable, while each parameter file tells Azure what values to use for dev, test, or production. Bicep fundamentals 4 commands Aliases: bicepparam Quick peek Open full term page

Management and Governance premium Bicep registry A Bicep registry is a module source that lets Bicep files reference reusable modules by registry path and version tag. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep resource declaration A Bicep resource declaration uses the resource keyword, a symbolic name, a resource type and API version, and resource properties. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep restore Bicep restore downloads external modules referenced by a Bicep file into the local module cache before build or deployment. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep symbolic name A Bicep symbolic name is the identifier used in source code to reference a resource, module, variable, parameter, or output. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep target scope Bicep targetScope sets the deployment scope for a file, such as resource group, subscription, management group, or tenant. Bicep intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep user-defined type A Bicep user-defined type uses the type statement to define custom data shapes for parameters, variables, or other expressions. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Bicep variable A Bicep variable stores an expression value that can be reused in a Bicep file to simplify authoring. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance learning-path-anchor Template expression A template expression computes values during ARM template deployment. ARM deployments fundamentals 5 commands Aliases: Template expression, template expression, Azure Template expression, ARM Template expression, ARM expressions, deployment expressions Quick peek Open full term page

Management and Governance learning-path-anchor Template function A template function is a built-in helper used by ARM templates or Bicep to calculate values. ARM deployments fundamentals 5 commands Aliases: Template function, template function, Azure Template function, ARM Template function, ARM functions, deployment functions Quick peek Open full term page

Management and Governance learning-path-anchor Template spec A template spec stores an ARM template or Bicep deployment artifact as a versioned Azure resource. Infrastructure as code fundamentals 5 commands Aliases: Template spec, template spec, Azure Template spec, ARM Template spec, Azure template spec, Microsoft.Resources/templateSpecs Quick peek Open full term page

Management and Governance learning-path-anchor Template spec version A template spec version is a specific immutable version of a template spec. ARM deployments fundamentals 5 commands Aliases: Template spec version, template spec version, Azure Template spec version, ARM Template spec version, template spec versions, Microsoft.Resources/templateSpecs/versions Quick peek Open full term page

Management and Governance learning-path-anchor Template validation Template validation checks whether an ARM or Bicep deployment is structurally and semantically acceptable before deployment. ARM deployments intermediate 5 commands Aliases: Template validation, template validation, Azure Template validation, ARM Template validation, ARM validation, deployment validation, az deployment validate Quick peek Open full term page

Management and Governance learning-path-anchor Tenant deployment A tenant deployment is a Resource Manager deployment executed at Microsoft Entra tenant scope. ARM deployments intermediate 5 commands Aliases: Tenant deployment, tenant deployment, Azure Tenant deployment, tenant scope deployment, az deployment tenant, ARM tenant deployment Quick peek Open full term page

Management and Governance learning-path-anchor Tenant scope Tenant scope is the highest Azure Resource Manager deployment and governance context tied to a Microsoft Entra tenant. Management scopes fundamentals 5 commands Aliases: Tenant scope, tenant scope, Azure Tenant scope, tenant level scope, ARM tenant scope, targetScope tenant Quick peek Open full term page

Developer Tools premium Azure CLI A cross-platform command-line tool for connecting to Azure and executing administrative commands on Azure resources. Command line fundamentals 6 commands Aliases: az, Azure command-line interface Quick peek Open full term page

Developer Tools premium Azure Developer CLI An open-source developer command-line tool that accelerates provisioning, deployment, pipeline setup, and monitoring for application resources on Azure. Developer workflow fundamentals 6 commands Aliases: azd Quick peek Open full term page

Management and Governance premium Explicit dependency An Explicit dependency is a manually declared deployment ordering relationship, commonly expressed with dependsOn in ARM templates or Bicep. Teams use it to force one Azure resource, module, or deployment step to wait for another when implicit dependency detection is not enough. It is not a runtime application dependency, a network dependency, a policy assignment, or a reason to serialize every resource deployment unnecessarily. In production, confirm resource or module names, dependsOn entries, implicit references, parent-child declarations, deployment operations, failed operation timestamps, what-if output, and whether ordering is truly required before treating the design as healthy or ready for release. ARM deployments advanced 6 commands Aliases: dependsOn dependency, manual deployment dependency, Bicep explicit dependency Quick peek Open full term page

Management and Governance premium Extension resource An Extension resource is an Azure Resource Manager resource that adds capabilities to another resource, such as a lock, role assignment, policy assignment, or diagnostic setting. Teams use it to attach governance, access, diagnostics, locks, policies, or configuration behavior to an existing Azure resource or scope without treating the extension as a standalone workload. It is not a child resource that only exists inside a parent namespace, a deployment script, a VM extension package, or proof that the target resource is configured correctly. Azure Resource Manager intermediate 6 commands Aliases: ARM extension resource, resource extension, scope extension resource Quick peek Open full term page

Management and Governance premium Deployment scope Microsoft Learn describes Azure Resource Manager and Bicep deployments as running at a specific scope: resource group, subscription, management group, or tenant. The selected scope determines which resources can be declared directly, where deployment history is recorded, and what permissions the deployment principal needs. ARM deployments fundamentals 5 commands Aliases: ARM deployment scope, Bicep targetScope, deployment boundary Quick peek Open full term page

Management and Governance premium Implicit dependency Implicit dependency is a deployment dependency that Azure Resource Manager infers when one resource references another resource or its properties. ARM deployments fundamentals 5 commands Aliases: Implicit dependency, implicit dependency, implicit-dependency Quick peek Open full term page

DevOps premium Infrastructure deployment script Infrastructure deployment script controls how deployment teams run imperative setup, validation, or bridge logic inside an otherwise declarative Azure infrastructure deployment. Teams see it in bicep files, arm templates. It is not a local shell script, a DevOps pipeline task, a custom script extension, or normal template declarative resource creation; confusing them can create hung deployments, leaked script output. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Infrastructure as Code Intermediate 5 commands Aliases: deployment script, ARM deployment script, Bicep deployment script, deploymentScripts resource, scripted IaC step Quick peek Open full term page

Storage premium Infrastructure encryption for storage Infrastructure encryption for storage controls how Azure Storage applies optional double encryption to blobs, files, queues, or tables depending on account and scope configuration. Teams see it in storage account creation, encryption blade. It is not blob immutability, soft delete, encryption in transit, customer-managed key rotation, or disabling shared key authorization; confusing them can create storage accounts that cannot meet compliance, rebuild-only remediation. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Azure Storage Security Intermediate 5 commands Aliases: storage infrastructure encryption, storage account double encryption, require infrastructure encryption, double encryption for Azure Storage Quick peek Open full term page

Integration premium Integration service environment Integration service environment controls how older Logic Apps workloads used a dedicated isolated runtime and VNet connectivity, and how teams identify remaining dependencies during migration. Teams see it in legacy logic apps ise resources, vnet integration. It is not Logic Apps Standard, App Service Environment, integration account, private endpoint, or a normal Consumption Logic App workflow; confusing them can create unsupported legacy integrations, missed retirement planning. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Logic Apps Advanced 5 commands Aliases: Logic Apps ISE, ISE, Integration Service Environment, dedicated Logic Apps environment Quick peek Open full term page

DevOps premium Pipeline in Azure DevOps A pipeline in Azure DevOps is an automated build, test, and deployment workflow. Microsoft Learn describes Azure Pipelines as CI/CD for many languages, platforms, and targets, with YAML or classic definitions that connect source changes to repeatable delivery stages. CI/CD fundamentals 5 commands Aliases: Azure Pipelines, ADO pipeline, Azure DevOps CI/CD pipeline, YAML pipeline, Azure Pipeline, DevOps pipeline Quick peek Open full term page

DevOps premium Policy as Code Policy as Code means treating Azure guardrails like application code. Instead of clicking policies into existence one subscription at a time, teams write policy definitions, initiatives, assignments, parameters, and exemptions in files, review them in pull requests, test them in lower environments, and deploy them through pipelines. It makes governance repeatable and traceable. A learner should think of it as the difference between a shared checklist and an automated rulebook that can be versioned, approved, rolled back, and proven during audits. Governance operations intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Policy effect A policy effect is the action Azure Policy takes after a rule matches a resource. The rule asks a question, such as whether a storage account allows public access, and the effect decides the response. Some effects only record a finding, some block the request, some add or change properties, and some deploy supporting settings later. For a learner or operator, the effect is the difference between a policy that warns, a policy that prevents drift, and a policy that actively repairs configuration. Azure Policy intermediate 5 commands Aliases: Policy effect, policy-effect Quick peek Open full term page

Management and Governance premium Policy parameter A policy parameter is a safe input box for Azure Policy. Instead of writing separate policies for each allowed region, tag name, diagnostic workspace, or enforcement effect, you define the rule once and pass different values when assigning it. That makes policies easier to reuse across management groups, subscriptions, and environments. Parameters can include defaults, allowed values, friendly display names, and metadata, so platform teams can offer controlled choices without asking every application team to understand the full policy JSON. Azure Policy intermediate 5 commands Aliases: Policy parameter, policy-parameter Quick peek Open full term page

Management and Governance premium Resource group A resource group is an Azure Resource Manager container that holds related resources for a solution. Azure scope fundamentals 5 commands Aliases: RG, Azure resource group Quick peek Open full term page

Management and Governance premium Resource group scope Resource group scope means the command, deployment, policy, or role assignment targets one resource group. It is narrower than subscription scope and broader than a single resource, making it a common boundary for application environments and team ownership. Management scopes intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium What-if deployment A what-if deployment is a preview of changes Azure Resource Manager predicts from an ARM template or Bicep file before deployment. It shows which resources would be created, modified, ignored, or deleted without applying changes, helping teams review infrastructure impact before execution. Infrastructure as code fundamentals 5 commands Aliases: ARM what-if deployment, Bicep what-if deployment, deployment preview Quick peek Open full term page

Management and Governance premium API version An API version is the version selector Azure uses when a tool, template, script, SDK, or REST call asks a resource provider to do something. It usually looks like a date, such as 2023-05-01, but it is not just a label and it is not the same as a product release number. Microsoft Learn anchors this term in Azure resource providers and types, but this field-manual definition is intentionally wider than an older short glossary entry because the page must teach what to inspect, what can break, who owns the. Resource providers fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium ARM template An ARM template is a JSON file that describes the Azure infrastructure you want instead of listing every portal click or command needed to build it. You declare resources, properties, parameters, dependencies, and outputs, then Azure Resource Manager works out how to create or update the environment. Microsoft Learn anchors this term in ARM templates - Azure Resource Manager, but this field-manual definition is intentionally wider than an older short glossary entry because the page must teach what to inspect, what can break, who owns the decision, and which evidence. Infrastructure as code fundamentals 4 commands Aliases: Azure Resource Manager template Quick peek Open full term page

Management and Governance premium Complete deployment mode Complete mode is the dangerous deployment mode. At resource-group scope, it can delete resources that are not in the template. It is useful only when you truly want the template to define the full state, and it needs careful review before production use. ARM deployments intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Deployment correlation ID A deployment correlation ID is the GUID recorded for an Azure Resource Manager deployment and related control-plane operations so teams can trace events, failures, and support evidence across logs. ARM deployments fundamentals 4 commands Aliases: ARM deployment correlation ID, correlationId for deployment, deployment tracking GUID, Azure deployment correlationId Quick peek Open full term page

Management and Governance premium Deployment history Deployment history is the Azure Resource Manager record of template, Bicep, and deployment operations at a scope, used to review past deployments, outputs, errors, and resources affected. Azure Resource Manager fundamentals 4 commands Aliases: ARM deployment history, Azure deployment history, resource group deployment history, template deployment history Quick peek Open full term page

Management and Governance premium Deployment history record A deployment history record is one named Azure Resource Manager deployment entry that captures status, parameters, outputs, correlation ID, timestamps, and operations for a specific deployment run. ARM deployments fundamentals 4 commands Aliases: deployment record, ARM deployment record, Azure deployment record, template deployment record Quick peek Open full term page