Search Azure terms

Management and Governance learning-path-anchor Tag value A tag value is the answer attached to a tag name. If the tag name is Environment, the value might be Production, Test, or Sandbox. If the name is CostCenter, the value might be a finance code. Values are where governance becomes meaningful, because they separate one owner, workload, data class, or lifecycle state from another. A good value is standardized, approved, and easy to query. A bad value is free-text chaos: prod, production, PROD, live, and critical all trying to mean the same thing. Tags and naming fundamentals 5 commands Aliases: tag values, Azure tag value, resource tag value, tag metadata value Quick peek Open full term page

Management and Governance learning-path-anchor Tagging strategy A tagging strategy is the playbook for using tags without making a mess. It answers simple but important questions: which tags are required, who owns the list, which values are allowed, where tags are applied, and what happens when a resource is missing one. Without a strategy, tags become random notes. With a strategy, tags become a dependable system for cost allocation, ownership, lifecycle cleanup, compliance evidence, and operational routing. The best strategies are small enough to follow and strict enough to m Tags and naming fundamentals 5 commands Aliases: Azure tagging strategy, tag governance strategy, tag taxonomy, resource tagging standard Quick peek Open full term page

Management and Governance learning-path-anchor Tags Tags are labels you attach to Azure things so people and tools can understand what they are for. A tag has a name and a value, such as Owner=DataPlatform or Environment=Prod. Tags do not make a virtual machine faster, secure a database, or change a web app setting. They make the estate easier to organize, report on, govern, and automate. Useful tags answer questions the business actually asks: who owns this, what does it support, what environment is it, and who pays for it? Tags and naming advanced 5 commands Aliases: Azure tags, resource tags, name-value tags, Azure metadata tags 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 root group The tenant root group is the highest management group scope associated with a Microsoft Entra tenant. Management groups fundamentals 4 commands Aliases: Tenant root group, tenant root group, Azure Tenant root group, root management group, root group 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 Advisor score Advisor score is an Azure Advisor percentage score that summarizes how closely resources follow recommended best practices. In everyday Azure work, teams use it to measure improvement across cost, reliability, security, performance, and operational excellence recommendations. The useful evidence is overall score, category score, impacted resource count, potential score increase, date, aggregation level, and filtered Azure Advisor fundamentals 4 commands Aliases: Azure Advisor score, best practices score, cloud optimization score Quick peek Open full term page

Management and Governance premium All mode All mode is an Azure Policy definition mode that evaluates all resource types and relevant scopes supported by the policy rule, and Microsoft recommends using all mode in most cases. Azure Policy fundamentals 3 commands Aliases: Azure Policy all mode, policy mode all, mode all Quick peek Open full term page

Management and Governance premium Allowed locations policy An allowed locations policy is an Azure Policy definition that restricts the Azure regions users can select when deploying resources, helping enforce geo-compliance and regional governance requirements. Azure Policy intermediate 3 commands Aliases: Allowed locations, location allowlist policy, regional restriction policy Quick peek Open full term page

Management and Governance premium Allowed resource types policy An allowed resource types policy is an Azure Policy definition that lets an organization specify which Azure resource types can be deployed, reducing uncontrolled services, complexity, cost risk, and attack surface. Azure Policy fundamentals 3 commands Aliases: Allowed resource types, resource type allowlist policy, allowed types policy 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 Append effect an Azure Policy effect that adds configured fields to a create or update request when a resource matches the policy rule. Azure Policy fundamentals 4 commands Aliases: Append effect, append effect Quick peek Open full term page

Management and Governance premium Application landing zone An application landing zone is one or more governed Azure subscriptions for a workload environment, placed under management groups so it inherits platform policies and shared services. Landing zones fundamentals 4 commands Aliases: application landing zone Quick peek Open full term page

Management and Governance premium Application tag An application tag is a resource tag key-value pair that identifies the application, product, workload, or service associated with an Azure resource. Tags and naming fundamentals 4 commands Aliases: application tag 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 Audit effect Audit effect is the Azure Policy setting that records non-compliance without blocking or changing the resource. It is the safer observation mode for many governance rollouts because teams can see what would be flagged before moving to deny, modify, or deployIfNotExists. Audit does not fix anything by itself. It creates compliance evidence and warning. Azure Policy fundamentals 2 commands Aliases: Azure Policy audit effect, audit policy effect, policy audit, audit compliance effect Quick peek Open full term page

Management and Governance premium AuditIfNotExists effect AuditIfNotExists effect is Azure Policy’s way to say, “this resource is allowed to exist, but something related to it is missing.” It does not deny the deployment. Instead, after the resource provider accepts a create or update, Policy checks for a companion resource or configuration, such as diagnostics, extensions, or protection. Azure Policy fundamentals 4 commands Aliases: Azure Policy auditIfNotExists, audit if not exists, policy audit related resource, auditIfNotExists policy effect Quick peek Open full term page

Management and Governance premium Azure Advisor Azure Advisor is the Azure recommendation service that reviews resource configuration and usage signals, then suggests best-practice actions for healthier cloud deployments. In Azure, teams encounter it when platform teams need a prioritized backlog for cost savings, reliability fixes, security hardening, performance improvements, and operational excellence. The useful question is what behavior it proves, who Optimization fundamentals 4 commands Aliases: Advisor, Azure Advisor recommendations, Advisor score Quick peek Open full term page

Management and Governance premium Azure control plane The Azure control plane is the part of Azure you use to manage resources rather than consume the application or data inside them. Microsoft Learn anchors this term in Azure control plane and data plane, 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 use, start with the technical boundary: Technically, the Azure control plane is handled by. Azure Resource Manager intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Azure data plane The Azure data plane is the part of Azure you use after a resource exists, when you interact with the capability that resource provides. Microsoft Learn anchors this term in Azure control plane and data plane, 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 use, start with the technical boundary: Technically, data-plane operations are service-specific operations against. Azure Resource Manager fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Azure Lighthouse Azure Lighthouse enables secure delegated management of Azure resources across customer tenants, supporting service providers and central teams with scalable cross-tenant governance. Delegated resource management advanced 5 commands Aliases: Lighthouse, delegated resource management, Microsoft Managed Services delegation Quick peek Open full term page

Management and Governance premium Azure Policy Azure Policy is a governance service for creating, assigning, and managing rules that evaluate Azure resources. Azure Policy fundamentals 7 commands Aliases: Policy Quick peek Open full term page

Management and Governance premium Azure reservation An Azure reservation is a one-year or three-year commitment that provides discounted pricing for eligible Azure resource usage. Cost Management fundamentals 5 commands Aliases: Azure Reservations, Azure reservation, reservation order, reserved capacity, reserved instance Quick peek Open full term page

Management and Governance premium Azure Resource Graph Azure Resource Graph is the fast inventory search engine for Azure resources. Microsoft Learn anchors this term in What is Azure Resource Graph?, 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 use, start with the technical boundary: Technically, Azure Resource Graph extends Azure Resource Management by maintaining queryable resource data across the subscriptions available to the signed-in. Fleet discovery fundamentals 4 commands Aliases: ARG Quick peek Open full term page

Management and Governance premium Azure savings plan An Azure savings plan provides discounted pricing on eligible compute usage when you commit to an hourly spend for one or three years. Cost Management fundamentals 5 commands Aliases: Azure savings plan, Azure savings plans, compute savings plan, savings plan for compute Quick peek Open full term page

Management and Governance premium Azure subscription An Azure subscription is a management, billing, and scale unit for Azure resources. Azure scope fundamentals 7 commands Aliases: subscription Quick peek Open full term page

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 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 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 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 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 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 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 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 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 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 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 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 premium Billing account A billing account is the Azure billing scope used to manage invoices, payments, subscriptions, and cost relationships. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Billing profile A billing profile is a billing account child object that manages invoice, payment, and purchase-related information for a set of charges. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Budget alert A budget alert is the notification Azure creates when spending or usage reaches a configured budget threshold. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Business unit tag A business unit tag is an Azure resource tag that identifies which department, product line, cost center, or operating group owns a resource or its spend. Tags and naming fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cache freshness Cache freshness describes how current cached data or a cached response is compared with the origin source. Dashboard operations advanced 2 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium CanNotDelete lock A CanNotDelete lock is an Azure Resource Manager management lock that prevents a resource, resource group, or subscription from being deleted while still allowing many read and update operations. Management locks intermediate 4 commands Aliases: delete lock Quick peek Open full term page

Management and Governance premium Chargeback Chargeback bills internal teams or business units for their Azure consumption. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Child management group A child management group is a branch under a parent management group. It helps organize subscriptions into smaller governance areas, while still inheriting broad rules from above. Use it when one tenant needs different policy or access boundaries for teams, business units, or environments. Management groups fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Child resource A child resource is an ARM or Bicep resource whose full type and name include a parent resource segment, whether declared inside the parent or separately with a parent reference. Azure Resource Manager fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cloud resource hygiene Cloud resource hygiene is an operational governance practice for keeping Azure resources organized, tagged, owned, secured, monitored, costed, and retired when no longer needed. Operational hygiene intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Commitment discount a cost-management arrangement where Azure gives lower pricing when an organization commits to predictable usage, spend, or capacity for a fixed period Cost Management Intermediate 3 commands Aliases: No aliases yet 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 Compliance scan an Azure Policy evaluation run that checks resources against assigned policy and initiative definitions so their current compliance results can be refreshed Azure Policy Intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cost anomaly Cost anomaly is an Azure glossary term for an unusual Azure spending pattern that Cost Management highlights because usage or cost changed differently than expected. In practice, it helps teams reason about early detection of unexpected charges, runaway usage, misconfigured resources, or workload behavior that changed without financial review using live Azure evidence, documented ownership, and Microsoft Learn guidance. It should be reviewed through security, reliability, operations, cost, and performance lenses before production changes. Cost Management intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cost center tag Cost center tag is an Azure glossary term for a resource tag value used to connect Azure charges to the internal department, project, product, or accounting code that funds them. In practice, it helps teams reason about cost ownership, chargeback, showback, budget reporting, and policy enforcement across subscriptions and resource groups using live Azure evidence, documented ownership, and Microsoft Learn guidance. It should be reviewed through security, reliability, operations, cost, and performance lenses before production changes. Cost Management beginner 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cost export Cost export is an Azure glossary term for a recurring Cost Management job that writes cost and usage datasets to Azure Storage for reporting, reconciliation, analytics, or automation. In practice, it helps teams reason about moving detailed cost data out of the portal and into governed storage, data pipelines, Power BI models, or finance systems using live Azure evidence, documented ownership, and Microsoft Learn guidance. It should be reviewed through security, reliability, operations, cost, and performance lenses before production changes. Cost Management intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cost recommendation Cost recommendation is an Azure glossary term for an Azure Advisor or Cost Management suggestion that identifies a likely way to reduce spend or improve cost efficiency. In practice, it helps teams reason about turning usage and configuration telemetry into actionable savings opportunities such as right-sizing, cleanup, reservations, or commitment planning using live Azure evidence, documented ownership, and Microsoft Learn guidance. It should be reviewed through security, reliability, operations, cost, and performance lenses before production changes. Azure Advisor intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Data catalog Data catalog is a governed inventory of data assets, metadata, business context, ownership, lineage, and access signals used to help people find and understand data. Data governance intermediate 4 commands Aliases: Data catalog Quick peek Open full term page

Management and Governance premium Data classification Data classification is the practice of assigning logical labels or classes to data assets so teams understand sensitivity, business meaning, and handling requirements. Data governance intermediate 4 commands Aliases: Data classification Quick peek Open full term page

Management and Governance premium Data lineage Metadata that describes how data moves and transforms across systems. Data governance advanced 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Deny assignment A deny assignment is an Azure authorization control that blocks specified actions at a scope even when role assignments would otherwise grant access. Azure RBAC intermediate 4 commands Aliases: Azure deny assignment, RBAC deny assignment, system-protected deny assignment, Authorization deny assignment Quick peek Open full term page

Management and Governance premium Deny effect The Deny effect is an Azure Policy effect that prevents a resource request from succeeding when the request does not match the policy rule. Azure Policy intermediate 4 commands Aliases: Azure Policy deny, policy deny effect, deny policy effect, resource request deny Quick peek Open full term page

Management and Governance premium DenyAction effect The DenyAction effect is an Azure Policy effect that blocks specific intended actions on matched resources, commonly used to prevent deletion of critical resources. Azure Policy advanced 4 commands Aliases: denyAction, Azure Policy DenyAction, policy deny action, delete protection policy effect Quick peek Open full term page

Management and Governance premium DeployIfNotExists effect The DeployIfNotExists effect is an Azure Policy effect that runs a template deployment when a related required resource or configuration is missing. Azure Policy advanced 4 commands Aliases: DINE effect, deploy if not exists, Azure Policy DeployIfNotExists, policy remediation deployment 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 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 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

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

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 Disabled effect The Disabled effect is an Azure Policy effect that turns off policy evaluation for a policy assignment or parameterized policy path, commonly for testing or controlled exceptions. Azure Policy intermediate 4 commands Aliases: Azure Policy disabled effect, policy disabled effect, effect disabled, disabled policy effect Quick peek Open full term page

Management and Governance premium Drift detection Drift detection identifies differences between the expected configuration baseline and the actual state of resources, policies, workloads, or managed infrastructure. Operational compliance intermediate 5 commands Aliases: configuration drift detection, resource drift detection, drift monitoring, infrastructure drift detection Quick peek Open full term page

Management and Governance premium Environment tag An environment tag is a resource tag value used to classify Azure resources by lifecycle stage or operating environment, such as dev, test, staging, or production. Tags and governance fundamentals 4 commands Aliases: environment tag Quick peek Open full term page

Management and Governance premium Exemption An Exemption in Azure Policy records an approved exception that excludes a resource hierarchy or individual resource from evaluation of a policy assignment. Teams use it to document a justified policy exception with scope, reason, category, expiration, and evidence instead of silently ignoring noncompliance. It is not a policy exclusion in assignment scope, a deny override, a remediation task, or permission to bypass governance without approval and review. In production, confirm assignment ID, exemption scope, category, expiration, metadata, policy definition references, approving owner, affected resources, compliance impact, and review evidence before treating the design as healthy or ready for release. Azure Policy intermediate 6 commands Aliases: policy exemption, Azure Policy exemption, waiver 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 Global resource Global resource is an Azure resource or service configuration whose behavior is global or nonregional instead of being deployed as a normal workload in one Azure region. Teams use it to understand why resources such as Azure Front Door, DNS-related services, or tenant-level identity features do not behave like regional compute or storage resources. In daily Azure work, it shows up when engineers choose a resource group location for metadata, design global routing, review service availability, explain compliance scope, or troubleshoot why a regional outage affects dependencies differently. Azure Resource Manager intermediate 4 commands Aliases: nonregional Azure resource, global Azure resource, Azure global service resource Quick peek Open full term page

Management and Governance premium Governance baseline A governance baseline is the minimum set of policies, access controls, tags, logging, security, and compliance requirements that Azure environments must meet before workloads are trusted for production. Governance operations intermediate 4 commands Aliases: Azure governance baseline, cloud governance baseline, landing zone governance baseline Quick peek Open full term page

Management and Governance premium Governance scope Governance scope is the Azure boundary where governance controls such as policy assignments, initiatives, locks, role assignments, tags, or exemptions apply and are inherited. Management scopes intermediate 4 commands Aliases: Azure governance scope, policy scope, control scope 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 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