Search Azure terms

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

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

Management and Governance premium Deployment name A deployment name is the label Azure uses for one ARM or Bicep rollout. It is not the resource name. It helps you find the right deployment history, check status, inspect failed operations, and connect automation logs to the change that actually ran. ARM deployments fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Deployment output A deployment output is what your template hands back after it runs. Instead of hunting for a generated hostname, ID, endpoint, or principal ID, you define an output and let automation read the value directly from the deployment result. ARM deployments fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Deployment parameter A deployment parameter is a value you pass into a template at run time. It keeps the template reusable by letting dev, test, and production use different names, regions, sizes, or settings without rewriting the infrastructure code. ARM deployments fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Deployment script A deployment script is a Microsoft.Resources/deploymentScripts resource that runs Azure CLI or Azure PowerShell during an ARM or Bicep deployment to perform controlled custom actions and return outputs. ARM deployments intermediate 4 commands Aliases: ARM deployment script, Microsoft.Resources/deploymentScripts, Bicep deployment script, template deployment script Quick peek Open full term page

Management and Governance premium Deployment stack action on unmanage Deployment stack action on unmanage is the setting that defines what Azure does with resources that are no longer managed after a deployment stack is updated or deleted, such as detaching or deleting them. ARM deployments intermediate 4 commands Aliases: actionOnUnmanage, deployment stack unmanage action, stack unmanaged resource action, deployment stack cleanup behavior Quick peek Open full term page

Management and Governance premium Deployment stack deny settings Deployment stack deny settings define how stack-managed resources are protected from unauthorized control-plane operations, including deny modes, excluded actions, excluded principals, and child-scope behavior. ARM deployments advanced 4 commands Aliases: deploymentStacks denySettings, stack deny settings, deployment stack deny assignments, deny settings mode Quick peek Open full term page

Management and Governance premium Deployment variable A deployment variable is a named value or expression in an ARM template or Bicep file used to simplify resource definitions, construct repeatable names, reuse calculated values, and reduce duplication during deployment. ARM deployments fundamentals 4 commands Aliases: ARM template variable, Bicep variable, template variable, infrastructure variable Quick peek Open full term page

Management and Governance premium Idempotent deployment An idempotent deployment should be safe to run again. If the desired state has not changed, rerunning the Bicep or ARM deployment should not create duplicate resources or surprise changes; it should confirm or update Azure toward the same intended configuration. ARM deployments fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Incremental deployment mode Incremental mode is the normal ARM deployment behavior. It creates or updates what the template declares, but it does not delete unrelated resources just because they are missing from the template. That makes it safer than complete mode for most ongoing deployments. ARM deployments fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Deployment error A deployment error is Azure telling you that an infrastructure change did not validate or did not complete. It can happen before resources are created, while a provider is processing a request, or after a nested operation fails. Microsoft Learn anchors this term in Troubleshoot common Azure deployment errors, 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 proves the Azure environment is behaving as intended. In field. ARM deployments fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance verified Resource dependency A resource dependency tells Azure Resource Manager which resource must exist before another resource can be deployed, updated, or configured during an ARM or Bicep deployment. ARM deployments fundamentals 5 commands Aliases: ARM dependency, Bicep dependency, dependsOn, implicit dependency, deployment dependency Quick peek Open full term page

Management and Governance verified Resource group deployment A resource group deployment runs an ARM template or Bicep file at one resource group scope so the resources in that workload boundary are created or updated together. ARM deployments intermediate 5 commands Aliases: ARM resource group deployment, deployment group, az deployment group, Bicep resource group deployment, resource group scope deployment Quick peek Open full term page

Management and Governance field-manual-complete Subscription deployment A subscription deployment is an ARM or Bicep deployment that targets an Azure subscription instead of one resource group. It is useful when the thing you are creating or assigning lives at subscription scope, such as resource groups, policy assignments, role assignments, budgets, deployment stacks, or shared governance settings. The deployment still stores metadata in a region, but the resources it affects can organize the entire subscription. It is a common building block for landing zones, subscription vending, and consistent environment setup. It is a platform move, not a workload-only deployment. ARM deployments intermediate 5 commands Aliases: ARM subscription deployment, Bicep subscription scope, subscription-scope deployment, az deployment sub Quick peek Open full term page

Management and Governance verified What-if operation A what-if operation is the Azure Resource Manager evaluation request that powers deployment previews. It analyzes a template at resource group, subscription, management group, or tenant scope and returns predicted change types and property differences before resources are created, updated, or deleted. ARM deployments intermediate 5 commands Aliases: ARM what-if operation, deployment what-if operation, what-if preview operation Quick peek Open full term page

Management and Governance top-250-pre130-priority-upgraded Deployment operation A deployment operation is the step-by-step evidence inside a deployment. When a template fails, the deployment name tells you which rollout to inspect, and the operations show which resource action succeeded, failed, or returned the error you need to fix. ARM deployments intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium field-manual Management group deployment A management group deployment is an ARM or Bicep deployment executed at management-group scope instead of subscription or resource-group scope. Teams use it when platform teams need to deploy governance resources across a management group hierarchy. In plain English, it gives operators a named control for repeatable policy, role, and subscription-level governance from the correct Azure scope instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. ARM deployments intermediate 4 commands Aliases: Management group deployment, Azure Resource Manager, ARM deployments, ARM and Bicep governance deployments, subscription deployment, resource group deployment, tenant deployment, Azure Resource Manager and Bicep, ARM management group deployment, Bicep management group deployment 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 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

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

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

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 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 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 stack A deployment stack is an Azure Resource Manager resource that manages a group of resources deployed from a Bicep or ARM template, including lifecycle tracking, unmanaged-resource handling, and optional deny settings. Infrastructure as code intermediate 4 commands Aliases: Azure deployment stack, Bicep deployment stack, Microsoft.Resources/deploymentStacks, ARM deployment stack Quick peek Open full term page

AI and Machine Learning learning-path-anchor System message A system message is the instruction layer that tells an Azure OpenAI chat model how it should behave before it answers the user's request. It can define the assistant's role, tone, allowed sources, formatting rules, safety boundaries, and refusal behavior. It is stronger than an ordinary user message, but it is not magic and... Azure OpenAI fundamentals 5 commands Aliases: system prompt, metaprompt, developer instruction, assistant instruction 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 field-manual-complete Azure Resource Manager Azure Resource Manager, often shortened to ARM, is the front door for managing Azure resources. Azure Resource Manager fundamentals 6 commands Aliases: ARM Quick peek Open full term page

Management and Governance field-manual-complete Resource ID A resource ID is the full address of an Azure resource. Azure Resource Manager fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance field-manual-complete Resource provider registration Resource provider registration is the subscription-level step that unlocks a service family. If Microsoft.Network or Microsoft.ContainerRegistry is not registered, Azure may reject deployments even when the resource definition is correct. Resource providers intermediate 5 commands Aliases: Resource provider registration, resource-provider-registration, resource-provider, provider-namespace, provider-registration-state, azure-subscription, azure-resource-manager, bicep, deployment-error, resource-type, resource-provider-feature, policy-assignment Quick peek Open full term page

AI and Machine Learning premium Azure OpenAI resource An Azure OpenAI resource is the Azure control-plane boundary that hosts deployments, endpoints, access, networking, and billing context. Azure OpenAI fundamentals 12 commands Aliases: No aliases yet Quick peek Open full term page

AI and Machine Learning premium Azure OpenAI Azure OpenAI provides OpenAI model capabilities through Azure resources, deployments, identity, networking, quota, and monitoring controls. Azure OpenAI intermediate 8 commands Aliases: Azure OpenAI Service Quick peek Open full term page

Compute premium Azure Functions Azure Functions is Azure serverless compute for running code from triggers such as HTTP requests, queues, timers, events, and service integrations without managing servers. Serverless compute intermediate 6 commands Aliases: Functions, Function App, serverless functions Quick peek Open full term page

Containers premium Azure Kubernetes Service Azure Kubernetes Service is Azure’s managed Kubernetes service for deploying, scaling, and operating containerized applications while Azure manages much of the cluster control plane. Managed Kubernetes advanced 6 commands Aliases: AKS, managed Kubernetes 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 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

Containers premium Kubernetes Deployment A Kubernetes Deployment is a workload controller that declaratively manages ReplicaSets and pods for stateless applications. Kubernetes workloads Intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

DevOps premium Service connection Service connection is an Azure DevOps project resource that stores how a pipeline authenticates to Azure or another external service. In Azure Resource Manager connections, it can use workload identity federation, a managed identity, or a service principal so pipeline tasks can deploy safely. CI/CD fundamentals 6 commands Aliases: Azure DevOps service connection, service endpoint, Azure Pipelines service connection, Azure RM service connection Quick peek Open full term page

Containers premium ACR admin user The ACR admin user is the quick username-and-password login for a registry. It can be convenient for tests, but it weakens accountability because it is shared. For production, prefer Entra identities, managed identities, tokens, or scoped access patterns. Azure Container Registry intermediate 5 commands Aliases: ACR Quick peek Open full term page