Search Azure terms

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

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

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

Management and Governance learning-path-anchor Tags Tags are labels you attach to Azure things so people and tools can understand what they are for. A tag has a name and a value, such as Owner=DataPlatform or Environment=Prod. Tags do not make a virtual machine faster, secure a database, or change a web app setting. They make the estate easier to organize, report on, govern, and automate. Useful tags answer questions the business actually asks: who owns this, what does it support, what environment is it, and who pays for it? Tags and naming advanced 5 commands Aliases: Azure tags, resource tags, name-value tags, Azure metadata tags Quick peek Open full term page

Management and Governance learning-path-anchor Template expression A template expression computes values during ARM template deployment. ARM deployments fundamentals 5 commands Aliases: Template expression, template expression, Azure Template expression, ARM Template expression, ARM expressions, deployment expressions Quick peek Open full term page

Management and Governance learning-path-anchor Template function A template function is a built-in helper used by ARM templates or Bicep to calculate values. ARM deployments fundamentals 5 commands Aliases: Template function, template function, Azure Template function, ARM Template function, ARM functions, deployment functions Quick peek Open full term page

Management and Governance learning-path-anchor Template spec A template spec stores an ARM template or Bicep deployment artifact as a versioned Azure resource. Infrastructure as code fundamentals 5 commands Aliases: Template spec, template spec, Azure Template spec, ARM Template spec, Azure template spec, Microsoft.Resources/templateSpecs Quick peek Open full term page

Management and Governance learning-path-anchor Template spec version A template spec version is a specific immutable version of a template spec. ARM deployments fundamentals 5 commands Aliases: Template spec version, template spec version, Azure Template spec version, ARM Template spec version, template spec versions, Microsoft.Resources/templateSpecs/versions Quick peek Open full term page

Management and Governance learning-path-anchor Template validation Template validation checks whether an ARM or Bicep deployment is structurally and semantically acceptable before deployment. ARM deployments intermediate 5 commands Aliases: Template validation, template validation, Azure Template validation, ARM Template validation, ARM validation, deployment validation, az deployment validate Quick peek Open full term page

Management and Governance learning-path-anchor Tenant deployment A tenant deployment is a Resource Manager deployment executed at Microsoft Entra tenant scope. ARM deployments intermediate 5 commands Aliases: Tenant deployment, tenant deployment, Azure Tenant deployment, tenant scope deployment, az deployment tenant, ARM tenant deployment Quick peek Open full term page

Management and Governance learning-path-anchor Tenant 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

Analytics learning-path-anchor Databricks metastore The top-level Unity Catalog container for catalogs, schemas, tables, volumes, models, functions, and governance permissions. Databricks intermediate 4 commands Aliases: Unity Catalog metastore, Databricks Unity Catalog metastore, metastore Quick peek Open full term page

Analytics learning-path-anchor Databricks MLflow The managed MLflow experience in Azure Databricks for experiments, runs, metrics, artifacts, model lineage, and MLOps evidence. Databricks fundamentals 4 commands Aliases: MLflow on Databricks, Databricks experiment tracking, MLflow tracking Quick peek Open full term page

Analytics learning-path-anchor Databricks schema A Unity Catalog namespace under a catalog that groups tables, views, volumes, models, functions, and permissions. Databricks fundamentals 4 commands Aliases: Unity Catalog schema, Databricks database schema, schema in Unity Catalog 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

Monitoring and Observability learning-path-anchor Throughput Throughput is the amount of work a system completes over time, such as requests, messages, bytes, events, or transactions per second. In Azure, teams measure it with service metrics, logs, and capacity settings to judge whether an app, database, storage account, or messaging pipeline can sustain demand. Performance intermediate 4 commands Aliases: Throughput, throughput, Azure Throughput, Microsoft Learn Throughput, requests per second, events per second, transactions per second, bytes per second, work completed over time 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

AI and Machine Learning premium Azure OpenAI Azure OpenAI provides OpenAI model capabilities through Azure resources, deployments, identity, networking, quota, and monitoring controls. Azure OpenAI intermediate 8 commands Aliases: Azure OpenAI Service Quick peek Open full term page

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

Management and Governance premium Azure 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

Analytics premium Synapse SQL Synapse SQL is the T-SQL analytics capability in Azure Synapse Analytics. It includes dedicated SQL pools for provisioned warehousing and serverless SQL pools for on-demand lake queries, letting teams analyze structured and semi-structured data through familiar SQL endpoints inside a Synapse workspace. Synapse Analytics intermediate 7 commands Aliases: Synapse SQL engine, Azure Synapse SQL, Synapse serverless and dedicated SQL, SQL analytics in Synapse 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

Analytics premium Databricks access connector A first-party Azure resource that gives Azure Databricks a managed identity for Unity Catalog storage credentials and other governed service access. Azure Databricks intermediate 6 commands Aliases: Access Connector for Azure Databricks, Azure Databricks access connector, Databricks managed identity connector Quick peek Open full term page

Analytics premium Databricks catalog The top-level Unity Catalog namespace that organizes schemas, tables, views, volumes, models, functions, permissions, lineage, and governed data ownership. Azure Databricks fundamentals 6 commands Aliases: Unity Catalog catalog, Azure Databricks catalog, catalog object Quick peek Open full term page

Analytics premium Databricks cluster policy A Databricks governance object that limits which cluster settings users can choose, helping control cost, security, runtime consistency, and workload standards. Azure Databricks intermediate 6 commands Aliases: Databricks compute policy, cluster policy, compute policy Quick peek Open full term page

Analytics premium Databricks DBFS The Databricks file-system abstraction behind dbfs:/ paths, useful for workspace files and legacy mounts but carefully governed alongside Unity Catalog. Azure Databricks fundamentals 6 commands Aliases: DBFS, Databricks File System, dbfs:/ Quick peek Open full term page

Management and Governance premium Exemption An Exemption in Azure Policy records an approved exception that excludes a resource hierarchy or individual resource from evaluation of a policy assignment. Teams use it to document a justified policy exception with scope, reason, category, expiration, and evidence instead of silently ignoring noncompliance. It is not a policy exclusion in assignment scope, a deny override, a remediation task, or permission to bypass governance without approval and review. In production, confirm assignment ID, exemption scope, category, expiration, metadata, policy definition references, approving owner, affected resources, compliance impact, and review evidence before treating the design as healthy or ready for release. Azure Policy intermediate 6 commands Aliases: policy exemption, Azure Policy exemption, waiver Quick peek Open full term page

Management and Governance premium Explicit dependency An Explicit dependency is a manually declared deployment ordering relationship, commonly expressed with dependsOn in ARM templates or Bicep. Teams use it to force one Azure resource, module, or deployment step to wait for another when implicit dependency detection is not enough. It is not a runtime application dependency, a network dependency, a policy assignment, or a reason to serialize every resource deployment unnecessarily. In production, confirm resource or module names, dependsOn entries, implicit references, parent-child declarations, deployment operations, failed operation timestamps, what-if output, and whether ordering is truly required before treating the design as healthy or ready for release. ARM deployments advanced 6 commands Aliases: dependsOn dependency, manual deployment dependency, Bicep explicit dependency Quick peek Open full term page

Management and Governance premium Extension resource An Extension resource is an Azure Resource Manager resource that adds capabilities to another resource, such as a lock, role assignment, policy assignment, or diagnostic setting. Teams use it to attach governance, access, diagnostics, locks, policies, or configuration behavior to an existing Azure resource or scope without treating the extension as a standalone workload. It is not a child resource that only exists inside a parent namespace, a deployment script, a VM extension package, or proof that the target resource is configured correctly. Azure Resource Manager intermediate 6 commands Aliases: ARM extension resource, resource extension, scope extension resource Quick peek Open full term page

AI and Machine Learning premium Feature store A Feature store is a managed repository for machine learning features that lets teams discover, reuse, secure, monitor, and serve consistent feature values for training and inference. Teams use it to keep model features consistent between experimentation, batch training, and production inference instead of letting every team rebuild the same transformations differently. It is not a raw data lake, model registry, dashboard catalog, replacement for data governance, or guarantee that features are unbiased, fresh, or useful for every model. Azure Machine Learning intermediate 6 commands Aliases: Azure Machine Learning feature store, managed feature store, ML feature repository, feature registry Quick peek Open full term page

AI and Machine Learning premium Foundry hub A Foundry hub is a hub-style Microsoft Foundry resource used in selected scenarios to group AI projects with shared security, connections, data access, and governance settings. Teams use it to organize related AI projects that need common connections, managed identities, network controls, storage, security review, and platform governance across teams or application portfolios. It is not a whole Azure tenant, a model deployment by itself, a replacement for project-level permissions, or the required resource shape for every modern Foundry scenario. Microsoft Foundry intermediate 6 commands Aliases: Azure AI Foundry hub, Foundry hub resource, hub-based project, AI hub Quick peek Open full term page

Identity premium Access package An access package bundles resources someone may need for a job or project. Instead of asking separately for groups, apps, or sites, a user requests the package, and Entra applies approval, duration, review, and removal rules. Identity operations fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Identity premium Access review An access review is a governance check asking, “Should this access still exist?” It lets owners, managers, users, or admins review access to groups, apps, access packages, and privileged roles, then keep or remove access based on decisions and recommendations. Governance fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium ACR retention policy An ACR retention policy is a registry-level cleanup rule for untagged manifests in Azure Container Registry. When enabled on a supported registry, it schedules untagged manifests for deletion after the configured number of days, helping control storage growth while requiring care because deleted image data cannot be recovered. Azure Container Registry intermediate 5 commands Aliases: Azure Container Registry retention policy, ACR untagged manifest retention, registry retention policy Quick peek Open full term page

Containers premium ACR scope map An ACR scope map is a reusable set of repository permissions in Azure Container Registry. It groups actions such as content read, content write, delete, and metadata access, then applies that permission boundary to one or more non-Microsoft Entra registry tokens. Azure Container Registry intermediate 5 commands Aliases: Azure Container Registry scope map, repository scope map, registry token scope map Quick peek Open full term page

Monitoring and Observability premium Action group An Azure Monitor action group defines who gets notified and which actions run when an alert fires. It can include notification receivers such as email, SMS, and push, plus automation actions such as webhooks, secure webhooks, Azure Functions, Logic Apps, runbooks, ITSM, or Event Hubs. Alerts fundamentals 5 commands Aliases: Azure Monitor action group, alert action group, monitor action group Quick peek Open full term page

AI and Machine Learning premium Azure AI Foundry Create a governed project boundary where AI teams can build agents, evaluations, files, and model deployments without unmanaged sprawl.; Compare, evaluate, and approve model deployments before a generative AI feature is AI platform fundamentals 5 commands Aliases: AI Foundry, Microsoft Foundry, Foundry resource, Foundry project, Azure AI Foundry, azure ai foundry Quick peek Open full term page

Analytics premium Azure Databricks A unified, open analytics platform on Azure for building, deploying, sharing, and maintaining enterprise data, analytics, and AI solutions at scale. Data engineering and AI intermediate 5 commands Aliases: Databricks on Azure Quick peek Open full term page

Analytics premium Azure Databricks Unity Catalog A unified governance layer in Azure Databricks for data and AI assets, including catalogs, schemas, tables, volumes, models, privileges, and lineage. Data governance intermediate 5 commands Aliases: Unity Catalog Quick peek Open full term page

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

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

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 Azure savings plan An Azure savings plan provides discounted pricing on eligible compute usage when you commit to an hourly spend for one or three years. Cost Management fundamentals 5 commands Aliases: Azure savings plan, Azure savings plans, compute savings plan, savings plan for compute Quick peek Open full term page

Migration premium Azure Site Recovery Azure Site Recovery helps provide disaster recovery by managing replication, failover, and failback for supported workloads. Disaster recovery fundamentals 5 commands Aliases: ASR, Azure Site Recovery, Azure disaster recovery, Site Recovery Quick peek Open full term page