Search Azure terms

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 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 Resource provider API profile A resource provider API profile is a compatibility idea: instead of choosing every API version one by one, a profile represents a known set of Resource Manager API versions that tooling can target together. Microsoft Learn anchors this term in Azure resource providers and resource 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 decision, and which evidence proves the Azure environment is behaving as intended. In field use, start with. Resource providers fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Resource provider feature A resource provider feature is a switchable or gated capability exposed by an Azure provider namespace. Many Azure services ship new behaviors gradually, and some features must be registered for a subscription before the service lets you use them. This is not the same as registering the provider namespace itself. Microsoft Learn anchors this term in az feature, 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. Resource providers fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Resource provider mode Resource provider mode is a policy-design concept, not ordinary provider registration. In Azure Policy, a mode tells the policy engine what kind of resources or provider surface the definition evaluates. Most learners meet the common all or indexed modes first, but some policy definitions use provider-specific modes for specialized resource providers or data-plane-like surfaces. Microsoft Learn anchors this term in Azure Policy definition structure basics, 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. Azure Policy fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

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

Management and Governance 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 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 Provider namespace A provider namespace tells you which Azure service family owns a resource type. Microsoft.Storage, Microsoft.Compute, and Microsoft.Network are examples. It matters because permissions, API versions, registration, and error messages often point back to the provider namespace. Resource providers intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance field-manual-complete Provider registration state Provider registration state is the subscription-level status for a resource provider namespace, such as Registered, Registering, or NotRegistered. Microsoft Learn explains that registration enables Azure Resource Manager to use that provider’s resource types, locations, and operations without waiting for every region to finish. Resource providers intermediate 4 commands Aliases: No aliases yet 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 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

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

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

AI and Machine Learning premium AI services resource An AI services resource is the Azure resource, commonly Microsoft.CognitiveServices/accounts with kind AIServices, that provides the governance scope for AI service access, networking, billing, monitoring, keys, endpoints, model deployments, projects, and related configuration. Azure AI services fundamentals 3 commands Aliases: Azure AI services resource, Foundry resource, AIServices resource, Cognitive Services account 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 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 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 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 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 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 verified Resource group policy assignment A resource group policy assignment applies an Azure Policy definition or initiative to one resource group so resources inside that group are audited, denied, modified, or remediated according to the assignment. Azure Policy intermediate 5 commands Aliases: policy assignment at resource group, Azure Policy resource group scope, resource group scoped policy, RG policy assignment, policy scope resource group 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

Identity verified Resource identity A resource identity is the Azure identity a workload uses when it needs permission to call another service. Most teams see it as a system-assigned or user-assigned managed identity on a VM, App Service, Function, container app, automation account, or data service. Instead of storing a password or client secret, the resource receives a Microsoft Entra identity and uses tokens. Operators then grant that identity roles on Key Vault, Storage, SQL, Cosmos DB, or other dependencies. Identity operations fundamentals 5 commands Aliases: Workload identity for a resource, Managed identity surface 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 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 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

Governance field-manual-complete Non-compliant resource A non-compliant resource is an Azure resource that failed a policy check. The policy might require a tag, approved region, diagnostic setting, encryption option, private endpoint, SKU, or other rule. The resource still exists, but Azure Policy is saying its current state does not match the assigned governance standard. Non-compliance is not always an outage or a security breach. It is a signal that someone must review the rule, scope, exemption, and resource details to decide whether the resource needs remediation or the policy needs adjustment. Azure Policy intermediate 4 commands Aliases: No aliases yet 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 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 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