Search Azure terms

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 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 Billing account A billing account is the Azure billing scope used to manage invoices, payments, subscriptions, and cost relationships. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Billing profile A billing profile is a billing account child object that manages invoice, payment, and purchase-related information for a set of charges. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cost anomaly Cost anomaly is an Azure glossary term for an unusual Azure spending pattern that Cost Management highlights because usage or cost changed differently than expected. In practice, it helps teams reason about early detection of unexpected charges, runaway usage, misconfigured resources, or workload behavior that changed without financial review 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 intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Cost export Cost export is an Azure glossary term for a recurring Cost Management job that writes cost and usage datasets to Azure Storage for reporting, reconciliation, analytics, or automation. In practice, it helps teams reason about moving detailed cost data out of the portal and into governed storage, data pipelines, Power BI models, or finance systems 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 intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance verified Actual cost Actual cost is the Cost Management view of charges as they are billed for a period, instead of spreading commitment purchases across future usage. In everyday Azure work, teams use it to reconcile monthly invoices, show subscription spend, and explain what Azure charged now. The useful evidence is billing period, scope, meter, resource, currency, tags, Cost Management fundamentals 4 commands Aliases: Azure actual cost, billing cost, actual charges Quick peek Open full term page

Management and Governance verified Cost allocation Cost allocation is an Azure glossary term for the Cost Management practice of splitting shared Azure charges across the subscriptions, resource groups, or tags that should financially own them. In practice, it helps teams reason about chargeback, showback, shared platform costs, central services, and fair business accountability for cloud spend 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 intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance top-250-pre130-priority-upgraded Amortized cost Amortized cost is a Cost Management view that spreads reservation or savings plan purchases across the period they benefit, instead of showing the full purchase spike on the billing date. FinOps fundamentals 3 commands Aliases: amortized costs, amortized cost metric, reservation amortization, Amortized cost Quick peek Open full term page

Management and Governance complete Cost Analysis Cost Analysis is an Azure glossary term for the Cost Management workspace for exploring Azure spending by scope, service, resource, tag, time period, meter, and trend. In practice, it helps teams reason about understanding where money is going, why it changed, and which owner should respond before budgets or forecasts are missed 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 Analysis, Cost Management Cost Analysis Quick peek Open full term page

Management and Governance complete Cost forecast Cost forecast is an Azure glossary term for a projected estimate of future Azure costs based on historical resource use and the selected Cost Analysis scope. In practice, it helps teams reason about predicting whether current usage trends will exceed budget, funding, or commitment expectations before the billing period ends 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: No aliases yet Quick peek Open full term page

Management and Governance premium Cost center tag Cost center tag is an Azure glossary term for a resource tag value used to connect Azure charges to the internal department, project, product, or accounting code that funds them. In practice, it helps teams reason about cost ownership, chargeback, showback, budget reporting, and policy enforcement across subscriptions and resource groups 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: No aliases yet Quick peek Open full term page

Management and Governance premium Cost recommendation Cost recommendation is an Azure glossary term for an Azure Advisor or Cost Management suggestion that identifies a likely way to reduce spend or improve cost efficiency. In practice, it helps teams reason about turning usage and configuration telemetry into actionable savings opportunities such as right-sizing, cleanup, reservations, or commitment planning 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. Azure Advisor 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 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

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

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

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

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

Integration verified Receive and delete Receive and delete is an Azure Service Bus receive mode where the broker considers a message settled as soon as it sends the message to the receiver. If transfer or processing fails afterward, the message is lost instead of being redelivered. Azure Service Bus intermediate 5 commands Aliases: ReceiveAndDelete, receive-and-delete mode, destructive read, at-most-once receive Quick peek Open full term page

Integration verified Receive-and-delete mode A integration pattern or service capability in Messaging that helps teams connect services reliably without tightly coupling every component with clearer ownership, safety, and operational context. Messaging fundamentals 5 commands Aliases: No aliases yet 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 Fabric capacity A Fabric capacity is a dedicated pool of compute resources that powers Microsoft Fabric workloads assigned to workspaces. Teams use it to provide shared compute for Fabric workspaces, reports, lakehouses, warehouses, notebooks, pipelines, and real-time workloads under an assigned capacity SKU. It is not a single workspace, a Power BI report, a storage account, a Databricks cluster, or a guarantee that every tenant workload has unlimited performance. In production, confirm capacity name, SKU, region, admin list, assigned workspaces, workload settings, metrics app evidence, throttling, refresh history, pause state, billing owner, and reservation or scaling plan before treating the design as. Microsoft Fabric intermediate 6 commands Aliases: Microsoft Fabric capacity, Fabric F SKU, Fabric compute capacity 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

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

Analytics premium Dedicated SQL pool resume Dedicated SQL pool resume restarts compute for a paused Azure Synapse dedicated SQL pool so users and workloads can query the warehouse again and compute billing resumes. Analytics platform intermediate 4 commands Aliases: resume dedicated SQL pool, Synapse SQL pool resume, start SQL DW compute Quick peek Open full term page