Search Azure terms

Integration learning-path-anchor Throughput unit An Event Hubs throughput unit is a capacity setting in the Standard tier that controls how much ingress and egress a namespace can handle. Operators size TUs, enable Auto-inflate, and monitor throttling so event producers and consumers keep moving data without ServerBusy errors during traffic spikes. Event Hubs advanced 4 commands Aliases: Throughput unit, throughput unit, Azure Throughput unit, Microsoft Learn Throughput unit, Event Hubs TU, TUs, Event Hubs throughput units, Auto-inflate capacity Quick peek Open full term page

Integration command-rich Dead-letter reason Metadata that explains why a Service Bus message was dead-lettered. Messaging and eventing intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Advanced event filter Advanced event filter is an Event Grid subscription filter that matches event fields and data values using advanced operators. In everyday Azure work, teams use it to route only the events that a handler actually needs, without creating separate topics for every condition. The useful evidence is event subscription, key path, operator type, values, event Event Grid intermediate 5 commands Aliases: Event Grid advanced filter, advanced filtering, event subscription advanced filter Quick peek Open full term page

Integration premium AMQP 1.0 AMQP 1.0 is the protocol path Service Bus and Event Hubs clients use for reliable Azure messaging, including native AMQP and WebSockets transport choices. Messaging protocols Intermediate 4 commands Aliases: Advanced Message Queuing Protocol 1.0, AMQP, AMQP over WebSockets, AMQP transport 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

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

Integration premium Auto-forwarding Auto-forwarding lets Azure Service Bus move messages from one queue or subscription to another queue or topic automatically. In plain terms, it is a built-in message handoff. A sender can keep publishing to the source entity while Service Bus forwards the message to the next entity in the chain. Teams use it to centralize processing,. Messaging fundamentals 4 commands Aliases: Service Bus auto forwarding, autoforwarding, queue auto-forwarding, subscription auto-forwarding Quick peek Open full term page

Integration premium Auto-inflate Auto-inflate is Azure Event Hubs’ way to add more Standard tier throughput capacity when traffic grows. In plain terms, you set the namespace’s normal throughput units and an upper limit, and Event Hubs can increase capacity during busy periods. This helps absorb spikes without a person watching the portal every minute. It is especially. Event Hubs intermediate 4 commands Aliases: Event Hubs Auto-inflate, Event Hubs auto inflate, throughput unit auto scale, Event Hubs throughput scaling Quick peek Open full term page

Integration premium Built-in connector A built-in connector is an Azure Logic Apps connector that runs natively with the Logic Apps runtime instead of through a separately hosted managed connector service. Logic Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Capacity unit A capacity measure used by Event Hubs Dedicated clusters. Messaging and eventing intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Checkpoint In Event Hubs, checkpointing is the consumer responsibility of saving the current offset so processing can resume, fail over, or replay from a known position. Messaging and eventing intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium CloudEvents schema A integration pattern or service capability in Event routing that helps teams connect services reliably without tightly coupling every component with clearer ownership, safety, and operational context. Event routing fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Communication Services Azure Communication Services, the platform that adds voice, video, chat, SMS, email, and calling workflows to custom applications through Azure APIs and SDKs Communications Beginner 3 commands Aliases: Azure Communication Services Quick peek Open full term page

Integration premium Connector a prebuilt integration component that lets workflows talk to another service, application, data source, or system through triggers and actions Workflows fundamentals 2 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Consumer group an Event Hubs entity that gives a consuming application its own view of the same event stream without sharing read position with other applications Event streaming fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Consumer lag the backlog signal showing how far an event-processing application is behind the newest events available in Event Hubs or Kafka-compatible streams Event streaming intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Contact messages customer-facing message exchanges that an Azure Communication Services workload sends, receives, tracks, or routes for support, notification, appointment, or service workflows Communication Services intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Correlation filter 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 3 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Dead-letter queue A dead-letter queue stores messages that could not be delivered or processed successfully. Messaging fundamentals 11 commands Aliases: DLQ Quick peek Open full term page

Integration premium Deferred message A deferred message is an Azure Service Bus message that a receiver has set aside for later retrieval; it remains in the queue or subscription and must be retrieved by sequence number. Messaging intermediate 4 commands Aliases: Service Bus deferred message, message deferral, deferred Service Bus message 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

Integration premium Duplicate detection Duplicate detection in Azure Service Bus detects repeated messages by MessageId within a configured history window so a queue or topic can ignore duplicate sends. Messaging intermediate 4 commands Aliases: Service Bus duplicate detection, duplicate message detection Quick peek Open full term page

Integration premium Email Communication Services Email Communication Services is the Azure Communication Services email capability used to create email resources, configure domains and senders, and send transactional or application email through Azure. Azure Communication Services intermediate 4 commands Aliases: Azure Communication Services Email, ACS Email, Email Communication Service Quick peek Open full term page

Integration premium Event filtering Event filtering in Azure Event Grid limits which events are delivered to an event subscription by event type, subject filters, or advanced filters over event fields. Azure Event Grid intermediate 4 commands Aliases: event filtering Quick peek Open full term page

Integration premium Event Grid advanced filter An Event Grid advanced filter is a filter on an event subscription that evaluates event fields or data values with operators such as string, number, Boolean, or array comparisons. Azure Event Grid intermediate 4 commands Aliases: event grid advanced filter Quick peek Open full term page

Integration premium Event Grid custom topic Event Grid custom topic is a user-created Azure Event Grid topic that gives custom applications an endpoint for publishing business or application events. In Azure, it shows up when custom applications publish shipment, order, payment, device, or workflow events that subscribers need to process independently. Teams use it to review topic name, region, access keys or managed identity options, input schema, event subscriptions, filters, retry policy, dead-letter destination, and monitoring before changing production behavior. It is not an Azure system topic, Event Grid domain, Event Hub, or Service Bus topic. Event routing intermediate 5 commands Aliases: Azure Event Grid custom topic, custom Event Grid topic Quick peek Open full term page

Integration premium Event Grid dead-letter destination Event Grid dead-letter destination is a storage destination used by Azure Event Grid for events that cannot be delivered after retry or configuration handling. In Azure, it shows up when an event subscription needs a recoverable place for undelivered events instead of silently losing operational evidence. Teams use it to review event subscription dead-letter settings, storage account, blob container, identity or access method, retry policy, monitoring, retention, and processing runbook before changing production behavior. It is not a Service Bus dead-letter queue, handler retry loop, poison-message table, or general logging sink. Event routing intermediate 5 commands Aliases: Event Grid dead letter destination, Event Grid dead-letter storage 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 domain Event Grid domain is an Event Grid resource that provides one publishing endpoint for many related domain topics in a large or multi-tenant event solution. In Azure, it shows up when a platform needs to manage thousands of related topics, tenant-specific subscriptions, or application-specific event streams without creating unrelated standalone topics. Teams use it to review domain endpoint, domain topics, access keys or identity controls, event subscriptions, RBAC, filters, publishing application logic, metrics, and tenant ownership model before changing production behavior. It is not a DNS custom domain, Event Grid namespace custom hostname, single custom topic, or Service Bus namespace. Event routing advanced 5 commands Aliases: Azure Event Grid domain, event domain Quick peek Open full term page

Integration premium Event Grid event handler Event Grid event handler is the destination endpoint or Azure service that receives matching events from an Event Grid event subscription and acts on them. In Azure, it shows up when an event-driven workflow needs a function, logic app, webhook, queue, topic, event hub, storage queue, relay connection, or namespace topic to process events. Teams use it to review handler type, endpoint URL or resource ID, authentication method, validation handshake, managed identity permissions, retry behavior, dead-lettering, monitoring, and scaling plan before changing production behavior. It is not the event publisher, Event Grid topic, event schema, or the business event itself. Event routing fundamentals 5 commands Aliases: Event Grid handler, Event Grid destination Quick peek Open full term page

Integration premium Event Grid event schema Event Grid event schema is the JSON structure used to describe an Event Grid event, including metadata and the event data payload sent to subscribers. In Azure, it shows up when publishers, subscribers, filters, and handlers need a shared contract for fields such as id, subject, event type, event time, data, and versioning. Teams use it to review publisher payload format, custom topic input schema, subscription delivery schema, event type names, subject conventions, dataVersion, sample payloads, and handler parser tests before changing production behavior. It is not a database schema, full OpenAPI definition, handler endpoint, or Event Grid subscription. Event routing fundamentals 5 commands Aliases: Azure Event Grid schema, Event Grid schema Quick peek Open full term page

Integration premium Event Grid filter Event Grid filter is the matching configuration on an Event Grid event subscription that decides which events are delivered to a handler. In Azure, it shows up when subscribers should receive only relevant events based on event type, subject prefix or suffix, or advanced fields inside the event payload. Teams use it to review included event types, subject begins-with and ends-with filters, advanced filters, case sensitivity, schema field names, test payloads, and monitoring for matched events before changing production behavior. It is not a firewall rule, diagnostic query, handler-side if statement, or Azure Policy filter. Event routing intermediate 5 commands Aliases: Event Grid subscription filter, Event Grid event filter 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

Integration premium Event Grid MQTT broker An Event Grid MQTT broker is the MQTT publish-subscribe capability in Event Grid namespaces that authenticates clients, authorizes publish and subscribe requests, and routes MQTT messages between interested clients. Teams use it to connect MQTT clients, devices, and services through managed publish-subscribe messaging without running a separate broker platform. It is not a general Event Grid custom topic or an IoT Hub device registry replacement. 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: Azure Event Grid MQTT broker, MQTT broker in Event Grid namespaces Quick peek Open full term page

Integration premium Event Grid namespace An Event Grid namespace is a logical container for Event Grid resources such as namespace topics, clients, client groups, topic spaces, certificates, and permission bindings. Teams use it to group Standard tier Event Grid resources for MQTT broker messaging and HTTP namespace topics under one managed Azure scope. It is not the same thing as a Basic tier custom topic, system topic, partner topic, or domain. 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: Azure Event Grid namespace Quick peek Open full term page

Integration premium Event Grid partner topic An Event Grid partner topic is the customer-managed Event Grid resource where events from an authorized partner are received and then routed through event subscriptions. Teams use it to receive events from a SaaS provider or partner platform and route them to Azure services, applications, or webhooks. It is not a custom topic owned by the customer application or a system topic emitted directly by an Azure resource. 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: Azure Event Grid partner topic, Partner topic 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

Integration premium Event Grid retry policy An Event Grid retry policy controls how Event Grid retries event delivery attempts and when undelivered events are dropped or sent to a dead-letter destination. Teams use it to control how long Event Grid keeps trying to deliver an event when the destination is unavailable, throttled, or returning retryable errors. It is not a guarantee that every failed handler will process every event eventually. 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: Event Grid delivery retry policy Quick peek Open full term page

Integration premium Event Grid subject filter An Event Grid subject filter is an event subscription filter that matches events by subject prefix, subject suffix, or both so only selected events are delivered. Teams use it to send only events with matching subject paths to a destination, such as one container, device group, tenant, department, or workflow. It is not the same as advanced filtering on data fields or a security boundary by itself. 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: subject begins with filter, subject ends with filter Quick peek Open full term page

Integration premium Event Grid system topic An Event Grid system topic represents one or more events published by an Azure service for a specific Azure resource or scope. Teams use it to subscribe to events emitted by Azure services such as Storage, Event Hubs, IoT Hub, Key Vault, or Resource Manager. It is not a custom topic where an application publishes its own events or a partner topic from an external provider. 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: Azure Event Grid system topic, system topic Quick peek Open full term page

Integration premium Event Grid webhook endpoint An Event Grid webhook endpoint is an HTTPS endpoint configured as an event handler that validates ownership and receives Event Grid events over HTTP. Teams use it to send Event Grid events to a custom HTTPS application, API, Azure Function HTTP trigger, automation webhook, or supported workflow endpoint. It is not a storage queue, Event Hubs destination, or an endpoint that can skip Event Grid validation. 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: Event Grid webhook handler, webhook endpoint for Event Grid Quick peek Open full term page

Integration premium Event handler An event handler is the destination that receives Event Grid events and takes action, such as Azure Functions, Logic Apps, Event Hubs, Service Bus, Storage Queue, or a webhook. Teams use it to process Event Grid events by running code, starting workflows, buffering messages, streaming telemetry, or invoking a custom endpoint. It is not the event source, topic, filter, or schema that only decides what gets sent. 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: Azure Event Grid handler, event destination 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 auto-inflate Event Hubs auto-inflate is a Standard tier feature that automatically increases throughput units up to a configured maximum when namespace traffic exceeds current capacity. Teams use it to absorb variable ingress or egress bursts without manually raising throughput units every time traffic spikes. It is not automatic scale-down, unlimited capacity, partition scaling, or a replacement for capacity testing and consumer lag monitoring. 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: Auto-inflate for Event Hubs, Event Hubs automatic throughput scaling Quick peek Open full term page

Integration premium Event Hubs batch An Event Hubs batch is a client-side group of events prepared for sending or processing together while respecting Event Hubs size, partition, and producer constraints. Teams use it to send or process multiple events efficiently instead of making every event a separate network operation. It is not an Azure resource, a Capture file, a partition, or a guarantee that every event in business logic was processed exactly once. 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 Hubs event batch, EventDataBatch, batch send to Event Hubs Quick peek Open full term page

Integration premium Event Hubs capture Event Hubs Capture automatically writes streaming data from an event hub to Azure Blob Storage or Azure Data Lake Storage based on configured time or size intervals. Teams use it to archive raw event streams to storage for analytics, compliance, replay, or lakehouse ingestion without writing a separate capture consumer. It is not a consumer group, a checkpoint, a data transformation job, or a guarantee that downstream analytics has already processed the archived files. 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 Capture, Capture Streaming Events, Event Hubs archive capture Quick peek Open full term page

Integration premium Event Hubs checkpoint An Event Hubs checkpoint is a consumer-maintained record of progress, usually an offset or sequence number per partition, used to resume processing without rereading every event. Teams use it to remember how far a consumer has processed in each partition so stream processing can restart, scale, or fail over without losing its place. It is not the event data itself, a retention policy, a capture archive, or a guarantee that every downstream business action succeeded exactly once. Event Hubs intermediate 5 commands Aliases: Event Hubs consumer checkpoint, Event Hubs offset checkpoint, EventProcessor checkpoint 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 dedicated cluster An Event Hubs dedicated cluster is a single-tenant Dedicated tier Event Hubs deployment that provides reserved capacity for enterprise-scale streaming workloads. Teams use it to run high-volume, low-latency event streaming workloads with isolated capacity instead of sharing a multitenant namespace tier. It is not a single event hub entity, a consumer group, a Kafka cluster you manage yourself, or a small development namespace. 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: Dedicated Event Hubs cluster, Event Hubs Dedicated tier cluster, Event Hubs cluster 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 namespace An Event Hubs namespace is the management container for one or more event hubs and controls shared settings such as network access, SKU, capacity, and authorization. Teams use it to group event hubs under one managed Azure resource boundary for scale, networking, authorization, monitoring, and operational ownership. It is not an individual event hub stream, a consumer group, a storage account, or a generic directory folder. 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 namespace, namespace, Event Hubs resource container 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 An Event Hubs partition is an ordered sequence of events within an event hub that enables parallel event ingestion and consumption. Teams use it to split a stream into parallel ordered logs so producers and consumers can scale while preserving order within each partition. It is not a separate namespace, a consumer group, a database shard with automatic rebalancing, or a guarantee that all events are globally ordered. 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: partition, Event Hubs stream partition, event stream partition 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 private endpoint An Event Hubs private endpoint is a Private Link network interface that lets clients reach an Event Hubs namespace through a private IP address in a virtual network. Teams use it to keep Event Hubs traffic on private network paths and restrict namespace access from public internet routes. It is not an outbound connection from Event Hubs into your subnet, a substitute for authentication, or a guarantee that every Azure service can still reach the namespace. Event Hubs intermediate 5 commands Aliases: Private Link for Event Hubs, Event Hubs Private Link, private endpoint connection 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 publisher policy An Event Hubs publisher policy is a send-focused authorization pattern or rule that limits which publisher can send events to a namespace or event hub. Teams use it to grant producers only the send access they need without giving them broad manage or listen permissions. It is not a consumer group, schema rule, Event Grid filter, permanent secret vault, or proof that a producer follows the approved payload contract. 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: publisher policy, send policy, Event Hubs send authorization policy Quick peek Open full term page

Integration premium Event Hubs retention Event Hubs retention is the configured period that events remain available in an event hub for consumers to read or replay. Teams use it to decide how long stream data remains available for consumers, replay, analytics validation, and recovery after downstream outages. It is not permanent archival storage, Event Hubs Capture, blob lifecycle retention, a consumer checkpoint, or a guarantee that old events can be recovered after expiration. 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 retention, message retention, retention time Quick peek Open full term page

Integration premium Event Hubs SAS policy An Event Hubs SAS policy is an authorization rule with shared keys and permissions that can produce SAS tokens or connection strings for Event Hubs access. Teams use it to grant time-bound or key-based Event Hubs access when Microsoft Entra ID is not practical for a producer or consumer. It is not a managed identity, RBAC assignment, Key Vault secret by itself, or a safe replacement for least-privilege access review. 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: shared access signature policy, SAS authorization rule, Event Hubs access policy 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 offset An event offset is position metadata that identifies where an event sits within an ordered partition or stream. Teams use it to describe where a specific event was read from so teams can resume, replay, investigate gaps, and compare processing progress. It is not a global event ID, timestamp-only bookmark, consumer group, checkpoint file, or guarantee that business processing completed successfully. 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: offset, stream offset, partition offset Quick peek Open full term page

Integration premium Event ordering policy An event ordering policy is an architectural rule that defines how producers and consumers preserve required event order, usually by using stable partition keys and partition-scoped processing. Teams use it to decide which events must stay in order and how partition keys, consumers, retries, and downstream writes will preserve that order. It is not a single Azure Event Hubs setting, global ordering across all partitions, a timestamp sort, or a replacement for idempotent processing. 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: ordering policy, event order strategy, partition ordering rule 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

Integration premium Event subscription An Event subscription is an Event Grid configuration that selects events from a source and delivers matching events to a destination endpoint. Teams use it to route storage, resource, custom, or partner events to the correct webhook, function, queue, topic, or event handler. It is not the event source itself, an Azure subscription, an Event Hubs consumer group, or proof that the destination successfully processed every event. In production, confirm source scope, event types, filters, endpoint URL or resource ID, authentication method, dead-letter destination, retry settings, diagnostic logs, and receiving application owner before treating the design as healthy or ready. Event Grid intermediate 6 commands Aliases: Event Grid subscription, event routing subscription, event delivery subscription Quick peek Open full term page

Integration premium Integration account Integration account controls where Logic Apps stores reusable B2B artifacts that workflows use to translate, validate, sign, decode, encode, or route enterprise messages. Teams see it in logic apps workflows, integration account artifacts. It is not a Logic App workflow, an Azure Storage account, an API connection, an Integration Service Environment, or a general-purpose document repository; confusing them can create failed EDI exchanges, expired certificates. 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. Enterprise integration Intermediate 5 commands Aliases: Logic Apps integration account, enterprise integration account, B2B artifact account, EDI artifact store Quick peek Open full term page

Integration premium Integration service environment Integration service environment controls how older Logic Apps workloads used a dedicated isolated runtime and VNet connectivity, and how teams identify remaining dependencies during migration. Teams see it in legacy logic apps ise resources, vnet integration. It is not Logic Apps Standard, App Service Environment, integration account, private endpoint, or a normal Consumption Logic App workflow; confusing them can create unsupported legacy integrations, missed retirement planning. 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. Logic Apps Advanced 5 commands Aliases: Logic Apps ISE, ISE, Integration Service Environment, dedicated Logic Apps environment Quick peek Open full term page

Integration premium Kafka endpoint Kafka endpoint is the Kafka-compatible protocol endpoint on Azure Event Hubs that lets Kafka clients produce to and consume from event hubs without operating Kafka brokers. Event streaming intermediate 5 commands Aliases: Event Hubs Kafka endpoint, Apache Kafka endpoint, Kafka-compatible endpoint, Kafka protocol endpoint Quick peek Open full term page

Integration premium Lock duration Microsoft Learn describes Service Bus lock duration as the time a peek-locked message remains unavailable to other receivers while one receiver processes it. The default is one minute, and queues or subscriptions can be configured differently. Operators should review it with the connected Azure resource settings. Messaging and eventing intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Lock renewal Microsoft Learn describes lock renewal in Azure Service Bus as extending the lock on an already locked message so the current receiver can continue processing it. Clients can renew manually or use automatic lock-renewal features. Operators should review it with the connected Azure resource settings. Messaging fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Logic Apps managed identity A Logic Apps managed identity is the Microsoft Entra identity assigned to a Logic Apps workflow or Standard logic app resource so the workflow can authenticate to supported Azure resources without storing passwords, shared keys, or long-lived secrets in governed production environments. Azure Logic Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Message deferral Message deferral is a Service Bus capability that lets an application put a received message aside and retrieve it later by its sequence number. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Service Bus intermediate 4 commands Aliases: deferred message, Service Bus deferral, defer message Quick peek Open full term page

Integration premium Message lock Message lock is a Service Bus delivery lock that gives one receiver exclusive time to process and settle a message. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Service Bus fundamentals 4 commands Aliases: Service Bus lock, PeekLock message lock, brokered message lock Quick peek Open full term page

Integration premium Message session Message session is a Service Bus ordering feature that groups related messages into sessions identified by a shared session ID. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Service Bus intermediate 4 commands Aliases: Service Bus session, session-enabled queue, message session ID Quick peek Open full term page

Integration premium Sequence number A sequence number in Azure Event Hubs is the ordered number assigned to an event within a specific partition. It helps consumers identify position in the partition log, resume or replay processing from a known point, and diagnose gaps, duplicates, or lag alongside offsets and enqueued time. Event Hubs stream processing intermediate 4 commands Aliases: Event Hubs sequence number, event sequence number, partition sequence number, stream sequence number Quick peek Open full term page

Integration premium Service Bus Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. It helps decouple applications and services, load-balance work across competing consumers, route data across boundaries, and coordinate transactional workflows that require reliable messaging, ordering, sessions, duplicate detection, and dead-letter handling. Messaging fundamentals 6 commands Aliases: Azure Service Bus, Service Bus Messaging Quick peek Open full term page

Integration premium Service Bus authorization rule Service Bus authorization rule is a shared access policy on a namespace, queue, or topic. It names a key pair and grants Listen, Send, or Manage rights, letting applications create SAS tokens or connection strings scoped to the messaging entity they are allowed to use. Service Bus fundamentals 6 commands Aliases: Service Bus SAS policy, Service Bus shared access policy, Service Bus authorization policy, SAS authorization rule Quick peek Open full term page

Integration premium Service Bus auto-forwarding Service Bus auto-forwarding chains a queue or subscription to another queue or topic in the same namespace. When enabled, Service Bus removes messages from the source and places them on the destination automatically, letting teams build routing topologies without a custom relay consumer inside the broker. Messaging intermediate 5 commands Aliases: Service Bus forwarding, Service Bus forwardTo, auto-forwarding chain, forward dead-lettered messages Quick peek Open full term page

Integration premium Service Bus batch delete Service Bus batch delete removes multiple messages from a queue or subscription in one server-side operation. It uses a requested count and optional enqueue-time cutoff, reducing receive-and-delete loops for expired or irrelevant messages, while remaining best effort and limited by entity support. Service Bus fundamentals 4 commands Aliases: Service Bus message purge, Service Bus DeleteMessagesAsync, batch delete messages, Service Bus cleanup Quick peek Open full term page

Integration premium Service Bus duplicate detection Service Bus duplicate detection lets a queue or topic remember application-supplied MessageId values for a configured window. If the same MessageId is sent again within that window, the send succeeds but the duplicate message is dropped, reducing uncertainty after retries or network failures. Messaging intermediate 4 commands Aliases: Service Bus duplicate detection window, requiresDuplicateDetection, duplicateDetectionHistoryTimeWindow, MessageId deduplication Quick peek Open full term page

Integration premium Service Bus filter Service Bus filter is a rule on a topic subscription that decides which published messages are copied into that subscription. Filters evaluate message properties, not the body, and can use correlation filters or SQL filters, with actions available to modify matched messages. Messaging fundamentals 5 commands Aliases: Service Bus subscription filter, topic subscription rule filter, SQL filter, correlation filter, Service Bus rule filter Quick peek Open full term page

Integration premium Service Bus geo-replication Service Bus geo-replication is a Premium-tier feature that continuously replicates a namespace's metadata and message data from the primary region to a secondary region. It lets operators promote the secondary when the primary region degrades, preserving queues, topics, subscriptions, filters, and message state. Service Bus advanced 5 commands Aliases: Service Bus data replication, Service Bus regional replication, Service Bus secondary region, Service Bus namespace replication, Service Bus Premium geo replication Quick peek Open full term page

Integration premium Service Bus JMS Service Bus JMS is Azure Service Bus support for Java Message Service applications. It lets Java and Jakarta workloads communicate with Service Bus queues and topics through JMS APIs over AMQP, with Premium support for JMS 1.1 and JMS 2.0 and limited JMS 1.1 support in Standard. Service Bus advanced 5 commands Aliases: Azure Service Bus JMS, JMS over AMQP for Service Bus, Service Bus Java Message Service, Service Bus JMS 2.0, Service Bus JMS 1.1 Quick peek Open full term page

Integration premium Service Bus lock duration Service Bus lock duration is the configured peek-lock period for a queue or topic subscription message. During that period, one receiver owns the message and other receivers cannot process it. The default is one minute, the maximum configured value is five minutes, and clients can renew locks. Messaging intermediate 5 commands Aliases: message lock duration, peek-lock duration, Service Bus peek lock duration, queue lock duration, subscription lock duration Quick peek Open full term page

Integration premium Service Bus managed identity Service Bus managed identity means using Microsoft Entra managed identities so Azure-hosted applications can access Service Bus without stored credentials. Applications receive RBAC roles such as Data Sender or Data Receiver, while Service Bus namespace identities may also be assigned for service-managed scenarios such as encryption configuration. Service Bus fundamentals 5 commands Aliases: Service Bus identity-based access, Service Bus Entra authentication, managed identity for Service Bus, Service Bus secretless authentication, Service Bus RBAC identity Quick peek Open full term page

Integration premium Service Bus message A Service Bus message is the unit of data sent to a queue or topic. It contains a binary payload plus broker properties and application properties that control routing, settlement, duplicate detection, sessions, expiration, correlation, and how producers and consumers understand the work. Messaging fundamentals 5 commands Aliases: Service Bus brokered message, Azure Service Bus message, ServiceBusMessage, Service Bus payload, broker message Quick peek Open full term page

Integration premium Service Bus namespace A Service Bus namespace is the Azure management, DNS, identity, and network container for Service Bus messaging entities. It scopes queues, topics, subscriptions, rules, authorization settings, SKU choice, diagnostics, and access endpoints so applications can exchange brokered messages through one named service boundary. Messaging fundamentals 4 commands Aliases: Azure Service Bus namespace, Namespace, Service Bus broker namespace Quick peek Open full term page

Integration premium Service Bus prefetch Service Bus prefetch is a client-side receiver setting that fetches messages into a local buffer before the application asks for them. A nonzero prefetch count can reduce receive latency and improve throughput, but locked messages can expire if the client buffers more work than it can process. Messaging intermediate 4 commands Aliases: Azure Service Bus prefetch, Prefetch count, Service Bus receiver buffer Quick peek Open full term page

Integration premium Service Bus Premium Service Bus Premium is the Azure Service Bus offering for mission-critical brokered messaging with dedicated resources called messaging units. It provides stronger isolation, predictable throughput, Premium-only features such as private endpoints and full JMS 2.0 support, and scaling options for production namespaces. Service Bus fundamentals 4 commands Aliases: Azure Service Bus Premium, Premium Service Bus, Service Bus Premium Messaging Quick peek Open full term page