Search Azure terms

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 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 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 verified Resource drift Resource drift is the gap between the intended Azure configuration in code, policy, or design and the resource state that actually exists after manual changes or unmanaged deployments. Operational hygiene intermediate 5 commands Aliases: Azure resource drift, infrastructure drift, configuration drift, IaC drift, deployment drift 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 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 complete Stale resource Microsoft Learn guidance around governance, Advisor, Resource Graph, and environment management supports treating stale resources as cloud assets that no longer show clear ownership, usage, or recent change activity. The concept helps teams find abandoned workloads, reduce risk, and clean up cost before forgotten resources become incidents. Operational hygiene intermediate 5 commands Aliases: stale-resource, Stale resource, unused Azure resource, orphaned resource, abandoned cloud resource, stale cloud asset Quick peek Open full term page

Management and Governance verified Orphaned resource An orphaned resource is an Azure resource that still exists but no longer has a clear owner, workload, lifecycle plan, or business purpose. It is usually found through tags, activity history, cost reports, resource inventory, or governance reviews, then confirmed before cleanup to avoid deleting shared dependencies. Operational hygiene intermediate 4 commands Aliases: unowned Azure resource, unused Azure resource, abandoned resource, stale cloud asset Quick peek Open full term page

Management and Governance verified Resource naming convention A resource naming convention is the agreed pattern your team uses when naming Azure resources. It turns names from random labels into useful clues about workload, environment, region, resource type, and sequence. A good convention is not just pretty formatting. It must fit Azure provider rules, length limits, uniqueness scopes, DNS behavior, and immutability constraints. It also needs room for growth without leaking secrets or forcing every business detail into the name. Tags carry richer metadata; names help humans navigate Governance fundamentals 4 commands Aliases: Azure naming convention, resource naming standard, Azure resource name standard, cloud naming convention 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 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 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 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 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 compliance state Policy compliance state is the status Azure Policy reports after evaluating a resource against an assigned rule. It tells you whether the resource appears compliant, non-compliant, exempt, conflicting, or not fully known for that evaluation. This is not just a dashboard color. It is the evidence operators use to decide whether a deployment broke a rule, whether a remediation task is needed, or whether an exemption is hiding risk. A learner should connect compliance state to a specific resource, policy assignment, definition, timestamp, and scope. Azure Policy fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Policy Insights Policy Insights is where Azure Policy compliance evidence becomes queryable. Azure Policy definitions and assignments describe what should happen, but Policy Insights shows what Azure observed after evaluation. It stores state records that show current compliance and event records that show recent evaluation activity. Operators use it to answer questions such as which resources are non-compliant, which assignment is responsible, when the state changed, and whether remediation improved results. It turns policy from a static rule set into operational telemetry. Azure Policy intermediate 5 commands Aliases: Policy Insights, policy-insights Quick peek Open full term page

Management and Governance premium Policy state Policy state is the evidence record behind an Azure Policy compliance result. It answers practical questions such as which resource was evaluated, which policy assignment applied, whether the resource was compliant, and when Azure last knew that result. The portal summarizes these states, but operators often query them directly through Azure CLI, REST, or Resource Graph when they need proof. Policy state is especially useful when a dashboard says “non-compliant” and the team needs to locate the exact resource, policy, scope, and reason. Azure Policy intermediate 5 commands Aliases: Policy state, policy-state 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

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

Analytics field-manual-complete Kusto Query Language Kusto Query Language, or KQL, is the query language used across Azure Data Explorer, Microsoft Fabric, Azure Monitor, and Microsoft Sentinel to explore structured, semi-structured, and text data, filter records, summarize results, detect patterns, and build operational analytics and dashboards. Resource Graph fundamentals 4 commands Aliases: KQL Quick peek Open full term page

Management and Governance complete Snapshot TTL Microsoft Learn performance guidance treats time to live as a caching control that decides how long stored data remains useful before refresh. In Azure dashboards, a snapshot TTL defines how long a cached view of resources, metrics, costs, or health should be trusted. Dashboard operations advanced 4 commands Aliases: cache snapshot TTL, dashboard snapshot TTL, cached snapshot freshness, snapshot time to live Quick peek Open full term page

Management and Governance strict-validated Compliance state Compliance state is the Azure Policy evaluation result that indicates whether a resource complies with assigned policy rules, is noncompliant, exempt, conflicted, or not yet evaluated. Azure Policy Intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance verified Resource abbreviation Resource abbreviation recommendations in the Cloud Adoption Framework provide short examples mapped to Azure resource types and provider namespaces. Teams use them in naming conventions to keep names readable, consistent, and within resource length limits while still showing what each resource is. Tags and naming fundamentals 6 commands Aliases: Azure resource abbreviation, CAF resource abbreviation, naming abbreviation, resource type prefix, Azure naming prefix 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 lifecycle Resource lifecycle is the story of what happens to an Azure resource from the moment someone asks for it until it is retired. It includes naming, approval, deployment, ownership, tagging, access, monitoring, patching, scaling, cost review, backup, policy compliance, change control, and cleanup. The point is not paperwork. The point is knowing who owns the resource, why it exists, what depends on it, how it changes safely, and when it should be removed. Without that trail, every later change becomes slower and riskier. Operational hygiene fundamentals 5 commands Aliases: Cloud resource lifecycle, Resource retirement lifecycle 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

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

Analytics premium Databricks managed resource group The Azure resource group created or referenced for Databricks-managed infrastructure that supports a workspace and its classic compute resources. Azure Databricks intermediate 6 commands Aliases: managed resource group, Azure Databricks managed resource group, workspace managed resource group 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

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

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

AI and Machine Learning premium Document Intelligence resource A Document Intelligence resource is the Azure AI service resource that provides the endpoint, keys, region, pricing tier, network configuration, and monitoring for Document Intelligence APIs. Document Intelligence fundamentals 5 commands Aliases: Azure Document Intelligence resource, Document Intelligence account, AI service resource, Form Recognizer resource Quick peek Open full term page

AI and Machine Learning premium Foundry resource A Foundry resource is the primary Azure resource for building, deploying, and managing generative AI models, agents, evaluations, and applications. Microsoft Foundry intermediate 5 commands Aliases: Microsoft Foundry resource, Foundry AIServices resource, AI Services Foundry resource 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 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 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 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

AI and Machine Learning premium Multi-service AI resource Multi-service AI resource means an Azure AI resource that exposes supported AI service capabilities through one managed resource object. You see it when teams build applications that combine language, vision, speech, translation, or content services without creating a separate resource for every feature. Think of it as one Azure resource boundary for supported AI capabilities, with identity, network, monitoring, and billing attached. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure AI services fundamentals 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