Glossary
Search Azure terms
Open a clear definition, then continue into exam context, architecture, commands, operational examples, common mistakes, and related concepts.
Search all
Commands
Learning guides
Concept graph
Compare
Search-first Azure knowledge base
Term results
Search for a term or click a category. Results render only after you ask for them, so the glossary does not dump every available term on first load. Each result includes Quick peek and Open full term page actions.
Start with a search or a category.
Try managed identity , resource group , az group , private endpoint , or click Databases to load all database-related terms.
Showing 50 of 1,984 matching terms. Narrow the search to reduce the list.
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
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
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
Identity
premium
Identity Governance
Identity Governance is a Microsoft Entra set of capabilities for managing identity lifecycle, access lifecycle, access reviews, entitlement management, and privileged access.
Identity operations
intermediate
4 commands
Aliases: Entra ID Governance, identity governance, Identity Governance, Microsoft Entra Identity Governance
Quick peek
Open full term page
Storage
premium
Blob index tags
Blob index tags are key-value attributes on blob data that Azure Storage indexes and exposes for querying across containers in a storage account.
Blob Storage
fundamentals
3 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
field-manual-complete
Landing zone governance
Landing zone governance is the policy, identity, subscription, tagging, cost, security, and compliance control model used to keep Azure landing zones consistent as workloads grow. It uses Azure Policy, RBAC, Cost Management, management groups, and review processes to audit, enforce, and update platform guardrails.
Governance operations
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Integration
verified
Receive and delete
Receive and delete is an Azure Service Bus receive mode where the broker considers a message settled as soon as it sends the message to the receiver. If transfer or processing fails afterward, the message is lost instead of being redelivered.
Azure Service Bus
intermediate
5 commands
Aliases: ReceiveAndDelete, receive-and-delete mode, destructive read, at-most-once receive
Quick peek
Open full term page
Integration
verified
Receive-and-delete mode
A integration pattern or service capability in Messaging that helps teams connect services reliably without tightly coupling every component with clearer ownership, safety, and operational context.
Messaging
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Governance
learning-path-anchor
Tag inheritance
Tag inheritance is the controlled reuse of tags from a higher Azure or billing scope. Cost Management can apply higher-scope tags to usage records for reporting, while Azure Policy can copy selected parent tag values onto resources for governance at scale.
Resource tagging
fundamentals
5 commands
Aliases: inherited tags, Azure tag inheritance, billing tag inheritance, policy tag inheritance
Quick peek
Open full term page
Governance
learning-path-anchor
Tag name
A tag name is the label key in an Azure tag. In Environment=Prod, Environment is the tag name and Prod is the value. The name tells people and tools what question the tag answers: who owns this, what cost center pays for it, what environment is it, or what application does it support? Good tag names are short, consistent, boring, and governed. Bad tag names create duplicate categories like CostCenter, cost-center, CostCentre, and BillingCode that fracture reports.
Resource tagging
fundamentals
5 commands
Aliases: tag key, Azure tag key, resource tag name, metadata tag name
Quick peek
Open full term page
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
Analytics
learning-path-anchor
Synapse Spark pool
A Synapse Spark pool is the workspace compute definition Azure Synapse uses to start Apache Spark sessions. It records node size, node count, autoscale behavior, runtime version, packages, and idle timeout so notebooks, Spark jobs, and pipelines get repeatable distributed processing.
Synapse Analytics
fundamentals
8 commands
Aliases: Apache Spark pool, Spark pool, Synapse Apache Spark pool, serverless Spark pool
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
Monitoring and Observability
premium
Azure Resource Health
Azure Resource Health reports current and past health for individual Azure resources and helps diagnose service-impacting problems.
Operational hygiene
fundamentals
5 commands
Aliases: Azure Resource Health, Azure resource health status, Resource Health, resource availability status
Quick peek
Open full term page
DevOps
premium
Container image build
the build step that turns source, Dockerfile instructions, dependencies, and metadata into a container image stored in a registry
Deployment workflows
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Indexed mode
Indexed mode is the Azure concept that controls which Azure resources are considered during evaluation of a policy definition. Teams see it when working with azure policy definitions, policy mode field. It is not the all mode, an indexed search field, a database index, or an Azure AI Search index; that distinction matters because bad assumptions create resources not evaluated, false compliance confidence. Use the term when reviewing ownership, access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same resource, setting, or behavior.
Azure Policy
Intermediate
5 commands
Aliases: Azure Policy indexed mode, policy definition indexed mode, indexed policy mode, mode indexed
Quick peek
Open full term page
Management and Governance
premium
Platform baseline
A platform baseline is the minimum set of governance, security, identity, networking, monitoring, and cost controls an Azure environment should inherit before workloads deploy. It sets standard expectations for subscriptions, landing zones, policy assignments, RBAC, logging, tags, and operational ownership across the estate.
Governance operations
fundamentals
5 commands
Aliases: Azure platform baseline, governance baseline, enterprise platform baseline
Quick peek
Open full term page
Management and Governance
premium
Policy alias
A policy alias is the name Azure Policy uses to point at a real resource property. Instead of writing a policy against an awkward raw JSON path, you use an alias such as a storage account or virtual machine property. Azure Policy then knows what part of the resource to evaluate. Aliases are what make many deny, audit, append, and modify rules practical. If the alias is wrong, unsupported, or misunderstood, the policy may miss resources or block the wrong deployment.
Azure Policy
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Policy definition mode
Policy definition mode tells Azure Policy what kind of resources the policy should evaluate. The all mode evaluates resource groups, subscriptions, and resource types. The indexed mode focuses on resource types that support tags and location, which is useful for tag and location policies. Some built-in policies use resource provider modes for deeper surfaces such as Kubernetes or Key Vault data. Choosing the wrong mode can make a policy miss resources, mark the wrong resources non-compliant, or fail to behave the way authors expect.
Azure Policy
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Policy initiative
A policy initiative is a bundle of related Azure Policy definitions. Instead of assigning ten separate policies for tags, allowed regions, diagnostics, encryption, and public access, a team can group them into one initiative and assign that package to a scope. It makes a governance baseline easier to deploy, review, and explain. For learners, think of an initiative as a control set: the individual policies still do the checking, but the initiative provides the organized package, shared parameters, and management structure.
Azure Policy
intermediate
5 commands
Aliases: Policy initiative, Policy set definition, policy-initiative
Quick peek
Open full term page
Management and Governance
premium
Policy remediation
Policy remediation is Azure Policy’s controlled repair job for resources that already exist. A deny policy can stop a bad new deployment, but it cannot automatically fix old resources. Remediation is for policies with modify or deployIfNotExists effects, such as adding required tags or deploying missing diagnostic settings. You create a remediation task, Azure finds the affected resources, and the assignment’s managed identity performs the configured change. It is governance automation, but it still needs careful scope, permission, and result review.
Azure Policy
intermediate
5 commands
Aliases: Policy remediation, policy-remediation
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
Monitoring and Observability
premium
Service Health alert
A Service Health alert is an Azure Monitor activity log alert that watches ServiceHealth events for selected subscriptions, regions, and services. It routes incident, planned maintenance, security, or health advisory notifications to action groups so teams learn about platform issues before users report symptoms.
Operational hygiene
intermediate
5 commands
Aliases: Azure Service Health alert, Service Health alert, ServiceHealth activity log alert, platform health alert, service health alert, service-health-alert
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
Web
premium
App Service
Azure App Service is a managed HTTP-based platform for hosting web apps, REST APIs, and mobile back ends without managing the underlying servers. It helps learners understand where the concept appears in Azure operations and what to verify before changing it.
App Service
intermediate
4 commands
Aliases: App Service, app service
Quick peek
Open full term page
Monitoring
premium
Application Insights
Application Insights is the application performance monitoring capability in Azure Monitor. It collects OpenTelemetry or SDK telemetry such as requests, dependencies, exceptions, traces, metrics, and availability results so teams can continuously understand live application health, performance, failures, and user-impacting behavior.
Application observability
fundamentals
4 commands
Aliases: Azure Application Insights, App Insights, Azure Monitor Application Insights, application performance monitoring, APM
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
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
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
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
Monitoring and Observability
premium
Change Analysis
Change Analysis helps identify changes that may have affected application or resource behavior.
Operational hygiene
fundamentals
4 commands
Aliases: No aliases yet
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
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
Security
premium
Data classification tag
A tag or catalog label that marks the sensitivity, owner, regulatory handling, or business classification of an Azure resource or dataset.
Data protection and governance
Intermediate
4 commands
Aliases: classification tag, sensitivity tag, data sensitivity tag, confidentiality tag
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
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
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
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
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
No glossary terms matched that search.
Try a service name, acronym, command group, or category such as RBAC , az group , App Service , Application Insights , Databases , or Azure AI Search .
Clear filters and show matches
Reset search