Search Azure terms

Monitoring and Observability learning-path-anchor Telemetry events Telemetry events are breadcrumbs that say something meaningful happened in an application. They are different from raw logs because they usually have a clear event name and structured properties. A checkout completed, a document uploaded, a feature flag changed, or a device registered can all be telemetry events. In Azure Monitor Application Insights, these events help teams understand behavior, investigate incidents, and measure product outcomes. Good events are intentional, consistently named, and tied to the que Application data advanced 5 commands Aliases: event telemetry, custom events, Application Insights events, Azure Monitor events 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

Monitoring and Observability premium Application Insights connection string An Application Insights connection string specifies the Application Insights resource and endpoints that an instrumented application uses to send telemetry. Application Insights fundamentals 3 commands Aliases: APPLICATIONINSIGHTS_CONNECTION_STRING, application insights connection string Quick peek Open full term page

Monitoring and Observability premium Distributed tracing Distributed tracing follows a request across services, dependencies, and process boundaries so teams can understand latency, failures, and call relationships in a distributed application. Application telemetry intermediate 4 commands Aliases: end-to-end tracing, OpenTelemetry tracing, application distributed trace, transaction trace Quick peek Open full term page

Integration top-250-pre130-priority-upgraded Event Hub An Event Hub is the stream entity inside an Azure Event Hubs namespace that receives, retains, and exposes event data across partitions for producers and consumers. Teams use it to ingest application, telemetry, audit, or device events into one durable stream that multiple readers can process independently. It is not the namespace that hosts capacity, the consumer group that isolates readers, or the downstream analytics job that processes events. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Azure Event Hub, Event Hubs entity, event hub entity Quick peek Open full term page

Databases complete SQL Query Store Microsoft Learn describes Query Store as a SQL feature that captures a history of queries, execution plans, and runtime statistics for review. It helps troubleshoot performance changes, especially regressions caused by plan changes, and is available across SQL Server, Azure SQL Database, Azure SQL Managed Instance, and related SQL platforms. SQL performance monitoring intermediate 5 commands Aliases: Query Store, Azure SQL Query Store, SQL Server Query Store, query performance history Quick peek Open full term page

Security top-250-pre130-priority-upgraded Microsoft Sentinel Microsoft Sentinel means Microsoft cloud SIEM and SOAR service for collecting security signals, detecting threats, investigating incidents, and automating response. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. SIEM and SOAR fundamentals 4 commands Aliases: Sentinel, Azure Sentinel, Microsoft Sentinel SIEM 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

Monitoring and Observability premium Browser telemetry Browser telemetry is client-side performance and usage data collected from web browsers, commonly through the Application Insights JavaScript SDK in Azure Monitor. Frontend performance advanced 3 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium Application map Application Map is an Application Insights view that visualizes application components and dependencies using telemetry, helping teams identify bottlenecks and failure hotspots. Application Insights fundamentals 2 commands Aliases: application map 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

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

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

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

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

Management and Governance premium Application tag An application tag is a resource tag key-value pair that identifies the application, product, workload, or service associated with an Azure resource. Tags and naming fundamentals 4 commands Aliases: application tag Quick peek Open full term page

Identity premium Enterprise application Enterprise application properties in Microsoft Entra ID configure the organization-specific service principal settings for an application, including user assignment, single sign-on, provisioning, and ownership. Microsoft Entra applications intermediate 4 commands Aliases: Entra enterprise application, service principal application, enterprise app 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

Web verified Requests in application queue Requests In Application Queue is an Azure Monitor metric for Microsoft.Web/sites that reports how many Web App or Function App requests are waiting in the application request queue. It helps diagnose saturation, slow handlers, cold starts, thread exhaustion, or delayed scale-out. Web App metric intermediate 6 commands Aliases: RequestsInApplicationQueue, App Service application queue, HTTP requests in application queue, Web App request queue metric, Function App request queue metric Quick peek Open full term page

Storage learning-path-anchor Data Lake storage account A storage feature or access model in Data Lake Storage Gen2 that helps teams store, protect, move, and govern application or analytics data with clearer ownership, safety, and operational context. Data Lake Storage Gen2 advanced 19 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Append Block the Blob Storage operation that commits a new block of data to the end of an existing append blob. Blob Storage intermediate 12 commands Aliases: Append Block, append block Quick peek Open full term page

Networking premium DDoS Protection Azure DDoS Protection is a network-layer protection service that helps defend Azure public IP resources against distributed denial-of-service attacks using always-on traffic monitoring, adaptive mitigation, telemetry, and response capabilities. Network security intermediate 6 commands Aliases: Azure DDoS Protection, DDoS Network Protection, DDoS IP Protection, distributed denial of service protection Quick peek Open full term page

Integration premium Event Hubs Azure Event Hubs is a fully managed, real-time data streaming platform for ingesting large volumes of events with low latency and routing them to consumers for processing. Teams use it to collect telemetry, application events, logs, clickstreams, and device data at scale before analytics, functions, or downstream services process them. It is not a queue for command messages, a workflow engine, a database, or an Event Grid routing topic for discrete platform events. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs, Azure Event Hubs service Quick peek Open full term page

Integration premium Event Hubs authorization rule An Event Hubs authorization rule is a named shared access signature policy on a namespace or event hub that grants listen, send, or manage rights through cryptographic keys. Teams use it to control SAS-based producer, consumer, or management access when an application cannot use Microsoft Entra role-based access directly. It is not a Microsoft Entra role assignment, a managed identity, a firewall rule, or a proof that a generated token is safe forever. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Event Hub authorization rule, Event Hubs SAS authorization rule, Shared access policy for Event Hubs Quick peek Open full term page

Integration premium Event Hubs consumer An Event Hubs consumer is an application or service instance that reads events from partitions of an event hub through a consumer group. Teams use it to read and process events from an Event Hub stream for analytics, automation, storage, monitoring, or business applications. It is not a producer, a consumer group definition by itself, a Capture archive, or proof that the application processed events correctly. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs consumer, Event Hubs reader, event stream consumer Quick peek Open full term page

Integration premium Event Hubs consumer offset An Event Hubs consumer offset is the position a consuming application uses to continue reading events within a specific partition, usually captured through checkpoint state. Teams use it to understand where a reader stopped, resumed, replayed, or skipped within a retained Event Hubs partition. It is not a global cursor for the whole event hub, a Service Bus dequeue count, or proof that downstream business processing succeeded. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: consumer offset, Event Hubs reader offset, stream consumer position Quick peek Open full term page

Integration premium Event Hubs emulator The Event Hubs emulator is a local development tool that simulates Azure Event Hubs so developers can test producers and consumers without connecting to the cloud. Teams use it to prototype and test Event Hubs applications locally before connecting code to a real Azure namespace. It is not a production Event Hubs namespace, a substitute for scale testing, or a guarantee that cloud networking, identity, quota, or geo-recovery behavior works. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs emulator, local Event Hubs emulator, Event Hubs local emulator Quick peek Open full term page

Integration premium Event Hubs geo-disaster recovery Event Hubs geo-disaster recovery pairs namespaces and uses an alias so applications can fail over namespace metadata access to a secondary namespace during a regional disaster. Teams use it to keep a stable connection endpoint for disaster recovery planning when an Event Hubs namespace must move to a paired secondary region. It is not automatic failover, a backup of retained event data in standard metadata Geo-DR, or a replacement for application-level replay and regional processing design. Event Hubs intermediate 5 commands Aliases: Event Hubs Geo-DR, Event Hubs disaster recovery alias, Geo-recovery alias Quick peek Open full term page

Integration premium Event Hubs Kafka endpoint An Event Hubs Kafka endpoint lets Apache Kafka clients connect to Azure Event Hubs by using the Kafka protocol instead of managing Kafka brokers. Teams use it to move or run Kafka producer and consumer applications on Event Hubs while keeping the familiar Kafka protocol and client model. It is not a self-managed Kafka cluster, a full replacement for every Kafka broker feature, or proof that existing applications need no configuration testing. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: Event Hubs for Apache Kafka, Kafka-compatible Event Hubs endpoint, Apache Kafka endpoint Quick peek Open full term page

Integration premium Event Hubs offset An Event Hubs offset is metadata that identifies an event position within a partition of an event hub. Teams use it to describe the exact location of an event in a partition so readers can reason about ordering, replay, and processing position. It is not a timestamp alone, a sequence number alone, a global event hub position, or confirmation that a consumer completed downstream work. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: event offset, partition offset, stream offset Quick peek Open full term page

Integration premium Event Hubs partition key An Event Hubs partition key is a value supplied by a producer that determines which partition receives related events, helping preserve order for events with the same key. Teams use it to route related events to the same partition when applications need ordered processing for a tenant, device, account, route, or business entity. It is not a database primary key, a Cosmos DB partition key, a security boundary, or a guarantee that the selected partition will never become hot. Event Hubs intermediate 5 commands Aliases: partition key, event partition key, producer partition key Quick peek Open full term page

Integration premium Event Hubs processing unit An Event Hubs processing unit is reserved Premium tier capacity that provides isolated compute, memory, and storage resources for an Event Hubs namespace. Teams use it to size Premium Event Hubs workloads that need predictable streaming capacity, stronger tenant isolation, and room for busy producers and consumers. It is not a Standard throughput unit, a Dedicated capacity unit, a partition count, or an automatic guarantee that every consumer application will keep up. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: processing unit, PU, Premium processing unit Quick peek Open full term page

Integration premium Event Hubs producer An Event Hubs producer is an application, service, device, or client that sends events to an event hub. Teams use it to identify the workload that publishes telemetry, transactions, logs, or business events into an Event Hubs stream. It is not a consumer, event processor, checkpoint, storage capture destination, or proof that downstream systems processed the event. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: producer, event publisher, Event Hubs publisher client Quick peek Open full term page

Integration premium Event Hubs schema registry Event Hubs schema registry is a central repository in Event Hubs for schemas used by event-driven and messaging applications. Teams use it to let producers and consumers share versioned event schemas so payloads stay consistent as applications evolve. It is not an event hub partition, a data catalog for every dataset, an automatic validator for all messages, or a substitute for application-side schema handling. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: Azure Schema Registry, schema group, Event Hubs Schema Registry Quick peek Open full term page

Integration premium Event Hubs throughput unit An Event Hubs throughput unit is pre-purchased Standard tier capacity shared by all event hubs in a namespace for ingress and egress. Teams use it to size Standard Event Hubs namespaces so producers and consumers have enough shared streaming bandwidth for expected traffic. It is not a Premium processing unit, Dedicated capacity unit, partition count, consumer group, or a guarantee that every application has dedicated capacity. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: throughput unit, TU, Standard throughput unit Quick peek Open full term page

Integration premium Event processor An event processor is an application component that reads events from partitions, coordinates ownership, processes events, and records checkpoints for recovery. Teams use it to scale consumers across partitions while keeping track of where processing should resume after restarts or failures. It is not a producer, event hub namespace, consumer group by itself, checkpoint store alone, or proof that downstream business work cannot fail. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: EventProcessorClient, stream processor, event processing application Quick peek Open full term page

Monitoring and Observability premium Instrumentation key Instrumentation key controls which Application Insights component receives telemetry and how older application configurations identify the target monitoring resource. Teams see it in application insights resource properties, app settings. It is not a secret access key, API key, SAS token, Log Analytics workspace ID, or managed identity credential; confusing them can create missing telemetry, cross-environment data pollution. 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. Application Insights Fundamentals 5 commands Aliases: ikey, Application Insights instrumentation key, AI instrumentation key, telemetry instrumentation key Quick peek Open full term page

Monitoring and Observability premium Interaction to Next Paint Interaction to Next Paint controls how teams measure whether web pages feel responsive after real user interactions, especially for Azure-hosted web apps and customer portals. Teams see it in microsoft edge devtools, microsoft clarity dashboards. It is not server response time, Time to First Byte, First Input Delay, Cumulative Layout Shift, or a backend CPU metric; confusing them can create slow clicks, abandoned checkout flows. 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. Web Vitals Intermediate 5 commands Aliases: INP, Core Web Vitals INP, web responsiveness metric, interaction responsiveness Quick peek Open full term page

Internet of Things premium IoT Hub IoT Hub is the managed Azure service that provides secure, bidirectional communication between IoT applications and their connected devices at scale. Device messaging intermediate 5 commands Aliases: Azure IoT Hub, device-to-cloud messaging, cloud-to-device messaging, IoT message hub, IoT Hub endpoint Quick peek Open full term page

Monitoring and Observability premium KQL KQL controls how operators search telemetry, detect incidents, investigate performance, build dashboards, create alerts, and summarize operational evidence across Azure services. Teams see it in log analytics workspaces, azure monitor logs. It is not SQL, PromQL, OData filters, ARM template expressions, Azure Data Factory expression language, or application code; confusing them can create missed incidents, expensive queries. 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. Query language Fundamentals 5 commands Aliases: Kusto Query Language, Kusto query, Azure Monitor query language, Sentinel query language Quick peek Open full term page

Web premium App Service Azure App Service is a managed HTTP-based platform for hosting web apps, REST APIs, and mobile back ends without managing the underlying servers. It helps learners understand where the concept appears in Azure operations and what to verify before changing it. App Service intermediate 4 commands Aliases: App Service, app service Quick peek Open full term page

Monitoring and Observability premium Availability result Availability result is the recorded outcome of an Application Insights availability test run, including whether the probe succeeded, how long it took, and where it ran. In Azure, teams encounter it when teams query Azure Monitor Logs after a synthetic web test reports failures, slow responses, or regional differences. The useful question is what behavior Availability intermediate 4 commands Aliases: AppAvailabilityResults, availability test result, Application Insights availability result Quick peek Open full term page

Monitoring and Observability premium Availability test Availability test is an outside-in monitor that repeatedly calls a public HTTP or HTTPS endpoint and records whether it responded quickly enough. In Azure, teams encounter it when product teams need synthetic checks for websites, APIs, or critical external dependencies before users report an outage. The useful question is what behavior it proves, who owns Availability intermediate 4 commands Aliases: Application Insights availability test, web test, standard test, synthetic test Quick peek Open full term page

AI and Machine Learning premium Azure AI metrics Azure AI metrics is the measurable signals used to observe Azure AI applications, model endpoints, agents, evaluations, safety checks, and business outcomes. Azure AI services intermediate 4 commands Aliases: AI metrics, AI service metrics, Azure AI Metrics Advisor, Azure Monitor metrics for AI, Metrics Advisor, time series anomaly detection Quick peek Open full term page

Databases premium Azure Cosmos DB Azure Cosmos DB is a fully managed database service for NoSQL, relational, and vector workloads. It supports global distribution, elastic scale, multiple APIs, request-unit capacity, backup, and high availability so modern applications can store and query data without operating database servers. Azure Cosmos DB fundamentals 4 commands Aliases: Azure Cosmos DB, Cosmos DB, Azure Cosmos DB for NoSQL, Cosmos database, global NoSQL database, request-unit database Quick peek Open full term page

Databases premium Azure Cosmos DB for NoSQL The native document database API of Azure Cosmos DB for JSON data, SQL-like queries, partitioning, indexing, and scalable request-unit throughput. Azure Cosmos DB intermediate 4 commands Aliases: Cosmos DB NoSQL API, Azure Cosmos DB SQL API Quick peek Open full term page