Search Azure terms

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

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 Subscription alias A subscription alias is a handle for creating or tracking a subscription through automation. Instead of manually creating every subscription in the portal, platform teams can use aliases to request, inspect, and reconcile new subscriptions programmatically. Management scopes fundamentals 5 commands Aliases: No aliases yet 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

Management and Governance premium Paired region strategy A paired region strategy means you do not choose a second Azure region by guesswork. You check whether the primary region has a Microsoft-defined pair, whether the service you are using actually relies on that pair, and whether your workload still needs its own failover design. Microsoft Learn anchors this term in Azure region pairs and nonpaired regions, 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. Management scopes fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Region pair A region pair is Azure's planned partner region for resilience within a geography. It helps with disaster recovery thinking, platform update sequencing, and data residency planning, but you still need to confirm whether each service actually supports paired-region replication. Management scopes fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Resource scope Resource scope means you are targeting one specific Azure resource. It is the narrowest common scope, useful when access, locks, monitoring, or troubleshooting should affect only that object instead of everything in a resource group or subscription. Management scopes fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium 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 Subscription state Subscription state tells you whether a subscription can actually be used. A disabled or past-due subscription can block deployments, updates, or resource access, so state is one of the first things to check when many unrelated Azure actions suddenly fail. Management scopes intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance field-manual-complete Subscription scope Subscription scope means an Azure operation is aimed at a whole subscription rather than one resource group or one resource. The subscription becomes the boundary for access, policy, deployments, inventory, locks, budgets, and many reports. If you assign a role at subscription scope, every child resource group can inherit it. If you deploy at subscription scope, you can create items such as resource groups or subscription-wide policy assignments. It is broader than most workload changes, so it is useful, powerful, and easy to overuse. Management scopes fundamentals 5 commands Aliases: subscription-level scope, Azure subscription boundary, subscription management 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 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

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

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

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

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

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

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

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

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

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

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

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

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

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 Deployment scope Microsoft Learn describes Azure Resource Manager and Bicep deployments as running at a specific scope: resource group, subscription, management group, or tenant. The selected scope determines which resources can be declared directly, where deployment history is recorded, and what permissions the deployment principal needs. ARM deployments fundamentals 5 commands Aliases: ARM deployment scope, Bicep targetScope, deployment boundary Quick peek Open full term page

Management and Governance premium Invoice section Invoice section controls how Microsoft Customer Agreement charges are grouped on invoices so finance and engineering teams can allocate ownership and review monthly spend. Teams see it in cost management and billing portal, billing accounts. It is not an invoice model, resource group, management group, cost center tag, billing profile, subscription, or Azure Policy assignment; confusing them can create misallocated cloud spend, subscription charges on the wrong invoice group. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Cost Management and Billing Fundamentals 5 commands Aliases: MCA invoice section, billing invoice section, Azure invoice section, invoice grouping Quick peek Open full term page

Management and Governance premium Policy assignment The object that applies a policy or initiative to a management group, subscription, resource group, or resource scope. Azure Policy fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Policy notScope Policy notScope is the list of places where an Azure Policy assignment should not apply. Think of it as a surgical exclusion inside a larger assignment. A governance team might assign a location policy to an entire management group, then exclude a disaster recovery resource group or migration subscription that needs temporary freedom. The assignment still exists at the parent scope, but Azure Policy skips the excluded child scope during evaluation, so those resources do not appear as non-compliant for that assignment. Azure Policy intermediate 5 commands Aliases: notScopes, Policy notScope, policy-not-scope 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

Monitoring and Observability premium Service Health alert A Service Health alert is an Azure Monitor activity log alert that watches ServiceHealth events for selected subscriptions, regions, and services. It routes incident, planned maintenance, security, or health advisory notifications to action groups so teams learn about platform issues before users report symptoms. Operational hygiene intermediate 5 commands Aliases: Azure Service Health alert, Service Health alert, ServiceHealth activity log alert, platform health alert, service health alert, service-health-alert Quick peek Open full term page

Storage premium SFTP for Azure Blob Storage SFTP for Azure Blob Storage lets clients connect to a storage account through SSH File Transfer Protocol for file access, transfer, and management. It requires a supported storage account with hierarchical namespace enabled, then local users and scoped permissions control access to containers and paths. Storage platform intermediate 5 commands Aliases: Azure Blob Storage SFTP, SFTP support for Azure Blob Storage, storage account SFTP, Blob SFTP endpoint, SFTP for Azure Blob Storage Quick peek Open full term page

Analytics learning-path-anchor Synapse Studio Synapse Studio is the browser-based workspace experience for Azure Synapse Analytics. It exposes hubs for data, development, integration, monitoring, and management, letting users author notebooks and SQL scripts, build pipelines, configure connections, review access, and work with Git-backed or live artifacts. Synapse Analytics fundamentals 6 commands Aliases: Azure Synapse Studio, Synapse web workspace, Synapse workspace UI, Synapse authoring experience Quick peek Open full term page