Glossary
Search Azure terms
Open a clear definition, then continue into exam context, architecture, commands, operational examples, common mistakes, and related concepts.
Search all
Commands
Learning guides
Concept graph
Compare
Search-first Azure knowledge base
Term results
Search for a term or click a category. Results render only after you ask for them, so the glossary does not dump every available term on first load. Each result includes Quick peek and Open full term page actions.
Start with a search or a category.
Try managed identity , resource group , az group , private endpoint , or click Databases to load all database-related terms.
Showing 50 of 1,986 matching terms. Narrow the search to reduce the list.
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
Networking
premium
Application Gateway backend pool
the group of backend targets that an Application Gateway can forward matched requests to after a listener and routing rule select them.
Application delivery and API edge
intermediate
4 commands
Aliases: Application Gateway backend pool, application gateway backend pool
Quick peek
Open full term page
Networking
premium
Application Gateway HTTP setting
the Application Gateway backend configuration that controls how the gateway connects to backend servers for HTTP or HTTPS requests.
Application delivery and API edge
intermediate
4 commands
Aliases: Application Gateway HTTP setting, application gateway http setting
Quick peek
Open full term page
Networking
premium
Application Gateway listener
the Application Gateway component that waits for client requests on a frontend IP address, port, protocol, and optional hostname or certificate.
Application delivery and API edge
intermediate
4 commands
Aliases: Application Gateway listener, application gateway listener
Quick peek
Open full term page
Networking
premium
Application Gateway routing rule
the Application Gateway component that connects a listener to a backend pool, backend settings, redirect, or path-based routing decision.
Application delivery and API edge
intermediate
4 commands
Aliases: Application Gateway routing rule, application gateway routing rule
Quick peek
Open full term page
Security
premium
Application Gateway WAF policy
An Application Gateway WAF policy stores Web Application Firewall configuration for Application Gateway v2. It includes managed rules, custom rules, exclusions, and policy settings, and can be associated globally, with a listener, or with a path-based rule for targeted web request inspection.
Web application firewall
intermediate
4 commands
Aliases: Application Gateway WAF policy, WAF policy for Application Gateway, Azure WAF policy, regional WAF 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
Networking
premium
Front Door
Azure Front Door is Microsoft’s global edge service for modern web applications. Microsoft Learn describes it as a cloud CDN that provides fast, reliable, and secure access to static and dynamic content through Microsoft’s global edge network worldwide.
Application delivery and API edge
intermediate
5 commands
Aliases: Azure Front Door, AFD, Azure Front Door Standard, Azure Front Door Premium, global edge
Quick peek
Open full term page
Networking
premium
Front Door origin group
A Front Door origin group is a logical grouping of origins that receives similar traffic and controls health probing and load balancing behavior.
Application delivery and API edge
intermediate
5 commands
Aliases: Azure Front Door origin group, AFD origin group, backend pool in Front Door, origin pool
Quick peek
Open full term page
Networking
premium
Front Door profile
Front Door profile is the top-level Azure Front Door Standard or Premium resource that groups edge endpoints, routes, origins, domains, rule sets, security associations, and delivery settings. Teams use it to manage a global application entry point without treating each endpoint, route, or origin as a separate product. In daily Azure work, it shows up when engineers review edge architecture, add a new website, tune routing, attach custom domains, configure WAF, or troubleshoot global traffic. It is not the same thing as a single endpoint, DNS name, backend app, CDN cache rule, or web application firewall policy.
Application delivery and API edge
intermediate
5 commands
Aliases: Azure Front Door profile, AFD profile, Front Door Standard/Premium profile
Quick peek
Open full term page
Integration
premium
Developer portal
The developer portal is the Azure API Management portal where API consumers discover APIs, read documentation, sign in, subscribe to products, retrieve subscription details, and test API operations when allowed.
Application delivery and API edge
intermediate
4 commands
Aliases: API Management developer portal, APIM developer portal, developer portal in API Management, API consumer portal
Quick peek
Open full term page
Networking
premium
Front Door cache purge
A Front Door cache purge removes selected cached content from Azure Front Door edge locations so future requests retrieve fresh content from the origin.
Application delivery and API edge
intermediate
4 commands
Aliases: Azure Front Door cache purge, AFD cache purge, Front Door purge content
Quick peek
Open full term page
Networking
premium
Front Door endpoint
A Front Door endpoint is a logical grouping of one or more routes associated with domain names in an Azure Front Door profile.
Application delivery and API edge
intermediate
4 commands
Aliases: Azure Front Door endpoint, AFD endpoint, azurefd.net endpoint
Quick peek
Open full term page
Networking
premium
Front Door origin
A Front Door origin is a backend application or service endpoint that Azure Front Door can route client requests to through an origin group.
Application delivery and API edge
intermediate
4 commands
Aliases: Azure Front Door origin, AFD origin, origin server, backend origin
Quick peek
Open full term page
Networking
premium
Front Door route
Front Door route is the Azure Front Door configuration that decides which domain and path patterns send user requests to which origin group. Teams use it to connect edge endpoints and custom domains to backend applications while controlling accepted protocols, forwarding behavior, caching, and rule-set association. In daily Azure work, it shows up when engineers add APIs, split static and dynamic paths, migrate origins, route traffic between regions, or investigate why a request reached the wrong backend.
Application delivery and API edge
intermediate
4 commands
Aliases: AFD route, Azure Front Door route, edge route
Quick peek
Open full term page
Networking
premium
Front Door rules engine
Front Door rules engine is the Azure Front Door capability that applies edge rules to matching requests before they are sent to an origin. Teams use it to move selected routing, redirect, rewrite, header, and cache behavior to the edge instead of baking every rule into application code. In daily Azure work, it shows up when engineers tune SEO redirects, add security headers, rewrite paths, vary caching, preserve legacy URLs, or explain unexpected behavior before the origin ever receives traffic.
Application delivery and API edge
advanced
4 commands
Aliases: Front Door rule set, AFD rule set, rules engine
Quick peek
Open full term page
Networking
premium
Load balancer frontend IP
Microsoft Learn describes a Load Balancer frontend IP configuration as the address-facing entry point that receives client traffic for a load balancer. It can use a public or private IP address and is connected to rules, probes, and backend pools.
Application delivery and API edge
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Networking
premium
Load balancer health probe
Microsoft Learn describes an Azure Load Balancer health probe as the check that determines whether backend pool instances are healthy enough to receive new traffic. Probe configuration includes protocol, port, interval, and threshold choices that influence traffic distribution. Operators should review it with the connected Azure resource settings.
Application delivery and API edge
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Networking
premium
Load balancer rule
Microsoft Learn describes a load-balancing rule as the configuration that maps a frontend IP address and port to backend pool addresses and ports. The rule defines how incoming traffic is distributed and which health probe validates backend availability. Operators should review it with the connected Azure resource settings.
Application delivery and API edge
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Networking
premium
Outbound rule
An outbound rule is a Standard Azure Load Balancer configuration that controls outbound SNAT for backend pool instances. It defines which frontend IP configurations are used, which backend pool receives outbound access, protocol behavior, allocated SNAT ports, idle timeout, and optional TCP reset handling.
Application delivery and API edge
intermediate
4 commands
Aliases: Load Balancer outbound rule, outbound NAT rule, SNAT rule, Standard Load Balancer egress rule
Quick peek
Open full term page
Networking
template-specs-upgraded
Rewrite rule
Application Gateway rule logic for modifying request or response headers and URLs before backend handling.
Application delivery and API edge
intermediate
6 commands
Aliases: Application Gateway rewrite rule, URL rewrite rule, HTTP header rewrite rule, rewrite rule set, App Gateway rewrite
Quick peek
Open full term page
Networking
field-manual-complete
URL path map
A URL path map is an Azure Application Gateway configuration that routes requests to different backend pools based on path patterns in the URL. It connects path rules, backend targets, and HTTP settings so one gateway can serve multiple application paths.
Application Gateway
intermediate
5 commands
Aliases: path-based routing map, Application Gateway path map, URL route map, path rule map
Quick peek
Open full term page
Networking
top-250-pre130-priority-upgraded
Inbound NAT rule
Inbound NAT rule is an Azure Load Balancer rule that maps a frontend IP address and port to a backend virtual machine or scale-set instance port for inbound connectivity in Azure.
Application delivery and API edge
intermediate
5 commands
Aliases: Inbound NAT rule, inbound nat rule, inbound-nat-rule
Quick peek
Open full term page
Networking
field-manual-complete
Load balancer backend pool
Microsoft Learn describes a backend pool as the collection of resources that receive traffic from an Azure Load Balancer. Backend pools can include instances added through network interfaces or IP addresses, and multiple pools can serve different traffic groups.
Application delivery and API edge
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
Networking
premium
Application Gateway
Application Gateway is an Azure web traffic load balancer for HTTP and HTTPS applications. It routes requests by host name, path, listener, rule, backend pool, and health status, and can add TLS termination and Web Application Firewall controls when those features are configured.
Application delivery
fundamentals
4 commands
Aliases: Azure Application Gateway, App Gateway, regional layer 7 load balancer, HTTP application load balancer
Quick peek
Open full term page
Databases
premium
Cosmos DB API for Gremlin
Managed Cosmos DB graph API for relationship-heavy workloads that model data as vertices, edges, properties, and Gremlin traversals.
Azure Cosmos DB
intermediate
4 commands
Aliases: Azure Cosmos DB for Apache Gremlin, API for Gremlin, Gremlin API
Quick peek
Open full term page
AI and Machine Learning
premium
Face API
The Face API is an Azure AI service API that provides face detection, recognition, verification, identification, grouping, and related face analysis capabilities. Teams use it to build applications that detect faces in images, compare faces, verify identity scenarios, support liveness workflows, or organize face-related image data under approved responsible AI controls. It is not a general computer vision labeler, proof of identity by itself, a surveillance policy, or permission to use biometric capabilities without legal, privacy, and access review.
Azure AI services
intermediate
6 commands
Aliases: Azure AI Face, Azure Face API, Face service
Quick peek
Open full term page
Databases
premium
Cosmos DB MongoDB API
Cosmos DB MongoDB API means the Azure Cosmos DB API that lets many MongoDB applications use Cosmos DB through MongoDB-compatible drivers and tools. It is the practical label operators use when they decide how application data should be modeled, queried, protected, and monitored in Azure Cosmos DB. In plain English, it explains where developers, platform engineers, and support teams meet: the application wants fast data access, while the platform controls scale, cost, security, and recovery. A good glossary entry helps the team know which setting to inspect, which owner to involve, and which symptoms prove the design works.
Azure Cosmos DB
intermediate
5 commands
Aliases: Azure Cosmos DB MongoDB API, cosmos db mongodb api
Quick peek
Open full term page
Databases
premium
Cosmos DB Table API
Cosmos DB Table API is the Cosmos DB API that supports applications written for Azure Table Storage-style key-value tables with Cosmos DB capabilities. It lets teams keep a familiar table model while using Cosmos DB account management, global distribution, throughput, and monitoring. You see it when applications use PartitionKey and RowKey entities, Azure Table SDKs, or migrations from Azure Table Storage. The production check is whether the table access pattern, partition key, throughput model, and consistency expectations fit Cosmos DB rather than basic storage tables. Document the decision in code, templates, metrics, and runbooks.
Azure Cosmos DB
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Integration
premium
Event Grid delivery retry
Event Grid delivery retry is the Event Grid behavior that retries event delivery when a subscriber endpoint temporarily fails or returns retryable responses. In Azure, it shows up when handlers may be unavailable, slow, throttled, or temporarily blocked, but events still need controlled redelivery before dead-lettering or expiration. Teams use it to review maximum delivery attempts, event time-to-live, endpoint response behavior, dead-letter destination, subscription filters, monitoring, and handler readiness before changing production behavior. It is not application-level retry code, Service Bus lock renewal, Event Hubs checkpointing, or a guaranteed infinite replay mechanism.
Event routing
intermediate
5 commands
Aliases: Event Grid retry policy, Event Grid event retry
Quick peek
Open full term page
Integration
premium
Event Grid delivery schema
Event Grid delivery schema is the event format Azure Event Grid uses when sending an event to a subscriber endpoint. In Azure, it shows up when publishers and handlers must agree on whether delivered events use Event Grid schema, CloudEvents v1.0, or a custom input schema shape. Teams use it to review event subscription delivery schema, publisher input schema, handler parser, API contract, sample payloads, validation tests, filters, and compatibility monitoring before changing production behavior. It is not the handler destination type, the event source, a JSON schema registry, or the business data model itself.
Event routing
intermediate
5 commands
Aliases: Event Grid event delivery schema, event delivery schema
Quick peek
Open full term page
Integration
premium
Event Grid pull delivery
Event Grid pull delivery is an HTTP consumption model where applications connect to Event Grid namespace topics and read CloudEvents at their own pace using queue-like semantics. Teams use it to let applications read events when they are ready instead of receiving every event through immediate push delivery. It is not a Basic tier push subscription, Service Bus queue, or Event Hubs consumer group. In production, confirm the source, subscription, destination, filters, schema, identity, retry behavior, failure handling, monitoring, and owner before treating the route as safe.
Event Grid
intermediate
5 commands
Aliases: HTTP pull delivery, pull delivery in Event Grid
Quick peek
Open full term page
Monitoring
premium
Application Insights
Application Insights is the application performance monitoring capability in Azure Monitor. It collects OpenTelemetry or SDK telemetry such as requests, dependencies, exceptions, traces, metrics, and availability results so teams can continuously understand live application health, performance, failures, and user-impacting behavior.
Application observability
fundamentals
4 commands
Aliases: Azure Application Insights, App Insights, Azure Monitor Application Insights, application performance monitoring, APM
Quick peek
Open full term page
Identity
premium
Application permission
An application permission is an app-only permission, also exposed as an app role, that lets a client application access a resource without a signed-in user after consent is granted.
Identity operations
fundamentals
4 commands
Aliases: application permission
Quick peek
Open full term page
Storage
premium
Azure Tables API
Azure Cosmos DB for Table provides an API for table-style key-value data where entities are identified by partition key and row key, supporting applications written for Azure Table storage that need premium capabilities.
Table Storage
intermediate
4 commands
Aliases: Azure Table API, Cosmos DB for Table API, Azure Table Storage API
Quick peek
Open full term page
Databases
premium
Cosmos DB API for Cassandra
Managed Cosmos DB API for Cassandra-style wide-column applications using familiar Cassandra drivers, CQL concepts, and Azure Cosmos DB operations.
Azure Cosmos DB
intermediate
4 commands
Aliases: Azure Cosmos DB for Apache Cassandra, API for Cassandra, Cassandra API
Quick peek
Open full term page
Databases
premium
Cosmos DB API for MongoDB
Managed Cosmos DB API for document applications that use MongoDB-compatible drivers, tools, commands, and connection patterns.
Azure Cosmos DB
intermediate
4 commands
Aliases: Azure Cosmos DB for MongoDB, API for MongoDB, MongoDB API
Quick peek
Open full term page
Databases
premium
Cosmos DB API for NoSQL
Native Azure Cosmos DB API for JSON items, containers, SQL-style queries, SDKs, change feed, partitioning, and request-unit based operations.
Azure Cosmos DB
intermediate
4 commands
Aliases: Azure Cosmos DB for NoSQL, API for NoSQL, Core SQL API, SQL API
Quick peek
Open full term page
Integration
premium
API
An API is a defined interface of operations that clients call, often represented in Azure API Management by frontend operations mapped to backend services.
API Management
beginner
3 commands
Aliases: No aliases yet
Quick peek
Open full term page
Virtual Desktop Infrastructure
premium
Application group
An Azure Virtual Desktop application group controls access to a full desktop or a logical grouping of RemoteApp applications from a host pool.
Virtual desktops
fundamentals
2 commands
Aliases: application group
Quick peek
Open full term page
Networking
premium
Application security group
An application security group lets you group virtual machine network interfaces so network security group rules can target application roles instead of explicit IP addresses.
Network security
fundamentals
2 commands
Aliases: ASG, application security group
Quick peek
Open full term page
AI and Machine Learning
premium
Assistants API
Assistants API is the older assistant-building API pattern that organizes an AI workflow around assistants, threads, messages, runs, tools, and files. It helped developers build stateful assistants without inventing every orchestration object themselves. In 2026, it should be treated as a migration-sensitive term because Azure documentation marks the classic Assistants API as deprecated and.
Azure OpenAI
intermediate
2 commands
Aliases: Azure OpenAI Assistants API, OpenAI Assistants API, classic Assistants API, Assistants API v2
Quick peek
Open full term page
AI and Machine Learning
verified
Realtime API
The GPT Realtime API in Azure OpenAI supports low-latency conversational interactions where audio, text, and model responses can stream during the same session. Applications can use supported transports such as WebRTC, SIP, or WebSocket to build voice agents, assistants, and live interaction experiences.
Azure OpenAI
advanced
5 commands
Aliases: GPT Realtime API, Azure OpenAI Realtime API, realtime audio API, streaming voice API
Quick peek
Open full term page
Networking
premium
Web Application Firewall
Azure Web Application Firewall is a centralized protection service for HTTP applications. It can run with Application Gateway, Front Door, Application Gateway for Containers, or Azure CDN, using managed and custom rules to detect and block common exploits such as SQL injection and cross-site scripting.
Application security
fundamentals
6 commands
Aliases: WAF, Azure WAF, Application Gateway WAF, Front Door WAF
Quick peek
Open full term page
Containers
premium
API server authorized IP ranges
API server authorized IP ranges are an AKS security setting that limits who can reach the Kubernetes control-plane endpoint. Instead of letting any public IP attempt a connection to the API server, the cluster allows only specified public CIDR ranges, such as corporate VPN, jump-host, automation,.
Azure Kubernetes Service
intermediate
5 commands
Aliases: AKS API server authorized IP ranges, authorized API server IP ranges
Quick peek
Open full term page
Integration
premium
Event Grid managed identity delivery
Event Grid managed identity delivery is the pattern where Event Grid uses a managed identity on a topic, domain, or system topic to authenticate event delivery to supported destinations. In Azure, it shows up when teams want to deliver events to Azure destinations without storing destination keys or embedding secrets in event subscription configuration. Teams use it to review system-assigned or user-assigned identity, Event Grid topic or domain identity settings, destination RBAC role assignments, delivery identity settings, dead-letter identity settings, and monitoring before changing production behavior.
Event routing
advanced
5 commands
Aliases: Event Grid managed identity event delivery, managed identity delivery for Event Grid
Quick peek
Open full term page
No glossary terms matched that search.
Try a service name, acronym, command group, or category such as RBAC , az group , App Service , Application Insights , Databases , or Azure AI Search .
Clear filters and show matches
Reset search