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,996 matching terms. Narrow the search to reduce the list.
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
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
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
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
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
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
Resource provider
Microsoft Learn defines an Azure resource provider as a set of REST operations that supports functionality for a specific Azure service. The provider namespace, such as Microsoft.Storage or Microsoft.Compute, owns resource types, API versions, supported locations, operations, and registration state used by Azure Resource Manager.
Azure Resource Manager
fundamentals
5 commands
Aliases: Azure resource provider, provider namespace, ARM provider
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
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
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
Resource Graph query
A Resource Graph query is a fast way to ask, “What resources do we have?” across subscriptions. It is useful for inventory, governance, cleanup, tagging checks, security investigations, and finding patterns that would be painful to inspect one resource at a time.
Resource Graph
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Resource location
Resource location is the region tied to a resource. For many services it is where the workload runs; for some global resources it may be where metadata is stored. Either way, location affects compliance, capacity, latency, and availability planning.
Azure Resource Manager
fundamentals
4 commands
Aliases: Azure resource location
Quick peek
Open full term page
Management and Governance
premium
Resource provider operation
A resource provider operation is the permission-style action string behind Azure RBAC. It describes what can be done, such as Microsoft.Storage/storageAccounts/read or Microsoft.Compute/virtualMachines/write. If access fails, these operations often explain what permission is missing.
Resource providers
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Resource scope
Resource scope means you are targeting one specific Azure resource. It is the narrowest common scope, useful when access, locks, monitoring, or troubleshooting should affect only that object instead of everything in a resource group or subscription.
Management scopes
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Resource type
Resource type tells Azure what kind of object you are working with. A storage account, virtual machine, and virtual network each has a provider/type string. That string controls which API, permissions, properties, and deployment rules apply.
Resource providers
intermediate
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
verified
Resource delete protection
Resource delete protection uses Azure management locks, usually CanNotDelete, to stop critical resources or resource groups from being deleted by ordinary control-plane operations.
Management locks
fundamentals
5 commands
Aliases: Azure delete protection, management lock delete protection, CanNotDelete lock, delete lock, protected Azure resource
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
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
verified
Resource lock
A resource lock is a control-plane safety catch for Azure resources. It tells Azure Resource Manager to block deletion or broader changes even when the user normally has permission. CanNotDelete is the common production guardrail because it stops accidental removal while still allowing most updates. ReadOnly is stricter and can break normal operations if used carelessly. Locks are not backups, RBAC, soft delete, or data protection. They are a deliberate pause before someone or something changes critical infrastructure.
Azure Resource Manager
fundamentals
5 commands
Aliases: ARM lock, Management lock, Azure resource lock
Quick peek
Open full term page
Management and Governance
verified
Resource mover
Azure Resource Mover helps move supported Azure resources to another region through a controlled workflow. Instead of manually rebuilding every VM, disk, network, and dependency, you create a move collection, add resources, resolve dependencies, prepare the target, initiate the move, and then commit or discard. It is useful when a workload must leave one region for compliance, latency, capacity, feature availability, or disaster-recovery readiness. It does not magically move every service, so support matrices and dependency validation matter.
Azure Resource Manager
fundamentals
5 commands
Aliases: Azure Resource Mover, Move collection workflow
Quick peek
Open full term page
Management and Governance
verified
Resource name
A resource name is the name you give an Azure resource, such as a storage account, virtual network, key vault, web app, or database. It is not the same as the full resource ID. The name is only one part of that ID, but it is what humans see first in portals, logs, scripts, alerts, and cost reports. Naming matters because different resource types have different length, character, uniqueness, DNS, and rename rules. That makes naming a permanent architecture decision in many services.
Azure Resource Manager
fundamentals
5 commands
Aliases: Azure resource name, Resource naming
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
Management and Governance
field-manual-complete
Tracked resource
A tracked resource is an Azure Resource Manager resource type with top-level lifecycle, location, and tags. Unlike proxy or extension resources, tracked resources are represented as managed Azure resources that can be inventoried, tagged, governed, deployed, moved, and queried through Resource Manager. reliably.
Azure Resource Manager
intermediate
5 commands
Aliases: ARM tracked resource, top-level Azure resource, Azure resource, tracked ARM resource, resource with location and tags
Quick peek
Open full term page
Management and Governance
verified
Proxy resource
A proxy resource is an ARM resource that may not have its own regional lifecycle like a tracked resource.
Azure Resource Manager
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
verified
ResourceChanges table
The ResourceChanges table is an Azure Resource Graph table for asking, “What changed on my Azure resources?” It helps you investigate control-plane changes such as updates to resource properties, configuration, location metadata, tags, and other tracked resource details. Instead of opening one resource at a time, you can query change records across subscriptions you can access. It is especially useful after an outage, failed deployment, unexpected cost increase, security finding, or drift review where the first question is not what
Resource Graph
fundamentals
4 commands
Aliases: resourcechanges, Resource Graph changes, Azure resource changes table, resource change history
Quick peek
Open full term page
Management and Governance
verified
ResourceContainers table
The ResourceContainers table is the Azure Resource Graph place to look for the containers that hold or organize resources. In practice, that means management groups, subscriptions, and resource groups rather than the VMs, databases, apps, and storage accounts themselves. It helps you answer questions such as which subscription owns this resource group, what tags exist on resource groups, or how resources roll up under management groups. It is most powerful when joined with the Resources table, because it adds estate
Resource Graph
fundamentals
4 commands
Aliases: ResourceContainers, resource containers, Resource Graph containers table, subscription and resource group table
Quick peek
Open full term page
Management and Governance
verified
Resources table
The Resources table is the main Azure Resource Graph table for asking, “What Azure resources exist, and what do their important properties look like?” It covers the broad inventory of Azure Resource Manager resources such as storage accounts, virtual machines, key vaults, databases, networking objects, app resources, and many others. You use it to search across subscriptions without opening each resource. It is the table behind many governance, inventory, security, migration, and cleanup queries. If Resource Graph is your cloud
Resource Graph
intermediate
4 commands
Aliases: Resources, Resource Graph Resources table, Azure resources inventory table, ARG Resources table
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
Identity
learning-path-anchor
Tenant ID
A tenant ID is the globally unique identifier for a Microsoft Entra tenant.
Microsoft Entra
fundamentals
4 commands
Aliases: Tenant ID, tenant id, Azure Tenant ID, Microsoft Entra tenant ID, directory ID, tenantId
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
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
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
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
Storage
premium
Service endpoint for Storage
A service endpoint for Storage enables the Microsoft.Storage endpoint on a virtual network subnet and pairs it with storage account network rules. It lets workloads in that subnet reach Azure Storage over the Microsoft backbone while the account firewall allows only approved virtual network sources.
Storage platform
intermediate
6 commands
Aliases: Azure Storage VNet rule, Microsoft.Storage service endpoint, Service endpoint for Storage, Storage service endpoint, service endpoint for storage, service-endpoint-for-storage
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 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 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
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