Search Azure terms

Management and Governance premium Management group Microsoft Learn describes management groups as governance containers above subscriptions that let organizations organize subscriptions into a hierarchy. They support unified policy, access management, and governance controls across many subscriptions instead of repeating the same assignments subscription by subscription at enterprise scale. Azure governance fundamentals 5 commands Aliases: Azure management group, Management group hierarchy, MG scope Quick peek Open full term page

Management and Governance premium Parent management group A parent management group is the branch above a child management group or subscription. Rules assigned at the parent can flow downward, so changing the parent is a broad governance decision, not just a local label change. Management groups fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Root management group The root management group is the top of the Azure governance tree for a tenant. Because everything sits beneath it, policies or access assigned there can have very wide impact. Treat root-scope changes as enterprise-level decisions. Management groups intermediate 5 commands Aliases: tenant root group Quick peek Open full term page

Management and Governance premium Child management group A child management group is a branch under a parent management group. It helps organize subscriptions into smaller governance areas, while still inheriting broad rules from above. Use it when one tenant needs different policy or access boundaries for teams, business units, or environments. Management groups fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Management group hierarchy A management group hierarchy is the tree that organizes an Azure estate. Subscriptions can sit under management groups, management groups can sit under parents, and broad policy or access settings can flow down from higher branches to lower ones. Management groups intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Management group ID A management group ID is the stable name Azure tools use for a management group. The display name can be friendly, but the ID is what CLI commands, resource IDs, and policy assignments need when they target that governance scope. Management groups fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Management group scope Management group scope means the operation targets a branch of the Azure hierarchy, not just one subscription. It is useful for organization-wide policy, access, and landing-zone governance, but mistakes can affect many subscriptions at once. Management scopes intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium field-manual Management group display name A management group display name is the human-readable name shown for a management group in Azure governance views. Teams use it when administrators need a clear label for a management-group node without changing its immutable identifier. In plain English, it gives operators a named control for readable hierarchy navigation, clearer governance ownership, and less confusion during reviews instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. Management groups intermediate 4 commands Aliases: Management group display name, Azure Management Groups, Management groups, Azure management groups, management group ID, management group hierarchy, tenant root group, management group friendly name, displayName Quick peek Open full term page

Management and Governance premium field-manual Management group inheritance Management group inheritance is the way Azure governance assignments at a parent management group flow down to child groups and subscriptions. Teams use it when platform teams want policy, RBAC, and governance controls applied consistently across many subscriptions. In plain English, it gives operators a named control for centralized governance with predictable downstream scope and fewer one-off subscription changes instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. Management groups intermediate 4 commands Aliases: scope inheritance, Management group inheritance, Azure Management Groups, Management groups, Azure management groups, policy assignment, role assignment, Azure management groups and Azure Policy, inherited governance, Azure management groups, Azure Policy, and Azure RBAC Quick peek Open full term page

Management and Governance premium field-manual Management group policy assignment A management group policy assignment is an Azure Policy assignment applied at management-group scope so it affects child subscriptions and resources. Teams use it when governance teams need consistent guardrails across multiple subscriptions from one parent scope. In plain English, it gives operators a named control for centralized policy enforcement, compliance reporting, and fewer repeated subscription-level assignments instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. Azure Policy intermediate 4 commands Aliases: Management group policy assignment, Azure Policy, policy definition, policy initiative, resource group policy assignment, Azure Policy and management groups, policy assignment at management group scope, inherited policy assignment, Azure Policy at management group scope 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 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

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 Indexed mode Indexed mode is the Azure concept that controls which Azure resources are considered during evaluation of a policy definition. Teams see it when working with azure policy definitions, policy mode field. It is not the all mode, an indexed search field, a database index, or an Azure AI Search index; that distinction matters because bad assumptions create resources not evaluated, false compliance confidence. Use the term when reviewing ownership, access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same resource, setting, or behavior. Azure Policy Intermediate 5 commands Aliases: Azure Policy indexed mode, policy definition indexed mode, indexed policy mode, mode indexed Quick peek Open full term page

Management and Governance premium Platform baseline A platform baseline is the minimum set of governance, security, identity, networking, monitoring, and cost controls an Azure environment should inherit before workloads deploy. It sets standard expectations for subscriptions, landing zones, policy assignments, RBAC, logging, tags, and operational ownership across the estate. Governance operations fundamentals 5 commands Aliases: Azure platform baseline, governance baseline, enterprise platform baseline Quick peek Open full term page

Management and Governance premium Platform landing zone A platform landing zone is the shared Azure foundation that hosts common services for workload landing zones. It commonly includes connectivity, identity integration, management groups, policy, security monitoring, private DNS, logging, and automation so application teams can build on consistent enterprise guardrails. Governance operations fundamentals 5 commands Aliases: Azure platform landing zone, shared platform landing zone, enterprise-scale platform landing zone Quick peek Open full term page

Management and Governance premium Policy parameter A policy parameter is a safe input box for Azure Policy. Instead of writing separate policies for each allowed region, tag name, diagnostic workspace, or enforcement effect, you define the rule once and pass different values when assigning it. That makes policies easier to reuse across management groups, subscriptions, and environments. Parameters can include defaults, allowed values, friendly display names, and metadata, so platform teams can offer controlled choices without asking every application team to understand the full policy JSON. Azure Policy intermediate 5 commands Aliases: Policy parameter, policy-parameter Quick peek Open full term page

Management and Governance premium Application landing zone An application landing zone is one or more governed Azure subscriptions for a workload environment, placed under management groups so it inherits platform policies and shared services. Landing zones fundamentals 4 commands Aliases: application landing zone Quick peek Open full term page

Management and Governance premium Chargeback Chargeback bills internal teams or business units for their Azure consumption. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Disabled effect The Disabled effect is an Azure Policy effect that turns off policy evaluation for a policy assignment or parameterized policy path, commonly for testing or controlled exceptions. Azure Policy intermediate 4 commands Aliases: Azure Policy disabled effect, policy disabled effect, effect disabled, disabled policy effect Quick peek Open full term page

Management and Governance premium Scope exclusion A scope exclusion is an intentional carve-out. You can assign a policy broadly, then exclude a specific subscription, resource group, or resource that should not be evaluated. It is useful, but every exclusion should be documented because it weakens coverage. Management scopes fundamentals 4 commands Aliases: notScopes Quick peek Open full term page

Management and Governance premium Scope inheritance Scope inheritance means children can receive rules from their parents. A policy or role assignment at a management group can affect subscriptions below it. This is powerful for governance, but it also means a high-scope mistake can spread quickly. Management scopes fundamentals 4 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 field-manual-complete Subscription placement Subscription placement is where you put an Azure subscription in the management group hierarchy. It sounds administrative, but it decides which inherited guardrails the subscription receives. A production subscription placed under a regulated management group might inherit region restrictions, required logging, security policies, and platform team access. A sandbox subscription might inherit looser controls. Good placement gives workload teams the right amount of freedom without making governance a manual checklist. Bad placement quietly creates the wrong operating model before the first resource is deployed. Management groups intermediate 5 commands Aliases: management group placement, subscription reparenting, subscription hierarchy placement 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

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

Identity premium Entitlement management Entitlement management uses access packages to govern access to groups, applications, SharePoint sites, and other resources for internal and external identities. Identity Governance intermediate 4 commands Aliases: Microsoft Entra entitlement management, Entra entitlement management, access package governance Quick peek Open full term page

Identity field-manual-complete Privileged Identity Management Privileged Identity Management, usually called PIM, is the Microsoft Entra feature that keeps powerful access from being permanently active unless someone really needs it. Access control fundamentals 5 commands Aliases: PIM Quick peek Open full term page

Integration premium API Management backend An API Management backend is the HTTP service that implements a frontend API and its operations behind the API Management gateway. API Management intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium API Management gateway The API Management gateway is the component that receives API requests, applies policies, routes traffic to backends, and returns responses to callers. API Management intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium API Management operation An API Management operation is one callable action inside an API, such as GET /orders or POST /claims. It tells Azure API Management which HTTP method, URL template, parameters, and display name should be exposed to consumers. The operation can map to a backend route, return a mock response, accept. Application delivery and API edge intermediate 4 commands Aliases: APIM operation, API operation in API Management Quick peek Open full term page

Integration premium API Management revision An API Management revision is a safe working copy of an API for changes that should not break consumers. You create a revision, adjust operations, descriptions, policies, or backend settings, test the changes, and then make that revision current when it is ready. Existing consumers keep using the. Application delivery and API edge intermediate 4 commands Aliases: APIM revision, API revision Quick peek Open full term page

Integration premium API Management self-hosted gateway An API Management self-hosted gateway is a containerized copy of the API Management gateway that runs where your APIs live, such as on-premises, another cloud, or an Azure Kubernetes environment. Azure API Management remains the place where teams define APIs, products, policies, and observability.. Application delivery and API edge intermediate 4 commands Aliases: APIM self-hosted gateway, self-hosted API gateway Quick peek Open full term page

Integration premium API Management version An API Management version is a separate version of an API that helps teams handle breaking changes. Clients can keep using an older version while newer clients adopt the new version when ready. Versions can be identified through a path, header, or query parameter, depending on the versioning. Application delivery and API edge intermediate 4 commands Aliases: APIM version, API version in API Management Quick peek Open full term page

Management and Governance premium Management-plane operation A management-plane operation is an Azure control action. It is what you do when you create a virtual machine, update a storage account setting, assign a role, list resources, validate a deployment, or delete a resource group. Microsoft Learn anchors this term in What is Azure Resource Manager?, 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. Azure Resource Manager fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Storage field-manual-complete Lifecycle management rule Microsoft Learn describes lifecycle policy rules as named definitions with filters and actions. A rule selects blobs by type, prefix, or index tags, then transitions or deletes current versions, previous versions, or snapshots according to age and lifecycle conditions. Azure Storage intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Storage field-manual-complete Storage lifecycle management Policy-based automation that tiers or deletes Azure Blob Storage data as it ages or changes use. Storage lifecycle intermediate 5 commands Aliases: Azure Blob lifecycle management, storage account lifecycle policy, blob lifecycle management policy, storage retention tiering policy Quick peek Open full term page

Storage complete Storage account lifecycle management A storage feature or access model in Storage accounts that helps teams store, protect, move, and govern application or analytics data with clearer ownership, safety, and operational context. Storage accounts advanced 5 commands Aliases: blob lifecycle management, storage lifecycle policy, Azure Storage management policy, blob tiering policy Quick peek Open full term page

Integration complete API Management policy An API Management policy is a rule the gateway runs while handling an API call. Policies can validate tokens, add or remove headers, rewrite URLs, limit rates, cache responses, transform payloads, choose a backend, or return a custom response. They are written as ordered XML statements and can. Application delivery and API edge intermediate 4 commands Aliases: APIM policy, API policy in API Management Quick peek Open full term page

Management and Governance premium field-manual Management group deployment A management group deployment is an ARM or Bicep deployment executed at management-group scope instead of subscription or resource-group scope. Teams use it when platform teams need to deploy governance resources across a management group hierarchy. In plain English, it gives operators a named control for repeatable policy, role, and subscription-level governance from the correct Azure scope instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. ARM deployments intermediate 4 commands Aliases: Management group deployment, Azure Resource Manager, ARM deployments, ARM and Bicep governance deployments, subscription deployment, resource group deployment, tenant deployment, Azure Resource Manager and Bicep, ARM management group deployment, Bicep management group deployment Quick peek Open full term page

Integration field-manual-complete API Management Azure API Management is a hybrid, multicloud API management platform with a gateway, management plane, and developer portal for the full API lifecycle. API Management intermediate 3 commands Aliases: APIM Quick peek Open full term page

Integration strict-validated API Management named value An API Management named value is a reusable name/value pair for policies, supporting plain values, encrypted secrets, policy expressions, and Key Vault references. API Management policies intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance complete Cost Management Cost Management is an Azure glossary term for Microsoft’s FinOps toolset for analyzing, monitoring, allocating, exporting, alerting on, and optimizing Microsoft Cloud costs. In practice, it helps teams reason about connecting Azure spending to owners, budgets, recommendations, forecasts, exports, anomalies, and governance decisions using live Azure evidence, documented ownership, and Microsoft Learn guidance. It should be reviewed through security, reliability, operations, cost, and performance lenses before production changes. Cost Management beginner 3 commands Aliases: Azure Cost Management, Microsoft Cost Management, Microsoft Cost Management and Billing Quick peek Open full term page

Storage field-manual-complete Lifecycle management Microsoft Learn describes Azure Blob Storage lifecycle management as policies with automated rules for moving blobs between hot, cool, cold, and archive tiers or deleting data at the end of its lifecycle. Rules help manage cost as access patterns change. Blob Storage fundamentals 2 commands Aliases: No aliases yet 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

Databases premium Azure SQL logical server An Azure SQL logical server is a logical administrative construct for Azure SQL Database and related SQL resources. Microsoft Learn describes it as the central point for managing a collection of databases, including logins, firewall rules, auditing, threat detection policies, and failover groups. Azure SQL Database fundamentals 16 commands Aliases: No aliases yet Quick peek Open full term page