Search Azure terms

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 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 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 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 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 template-specs-upgraded Schema Registry Schema Registry is the place in Azure Event Hubs where teams store and manage the shape of event payloads. Messaging and eventing intermediate 6 commands Aliases: Azure Schema Registry, Event Hubs Schema Registry, schema group, Avro schema registry, event schema registry Quick peek Open full term page

Integration premium field-manual Max delivery count The max delivery count setting is the Service Bus setting that controls how many delivery attempts a message can have before it moves to the dead-letter queue. Teams use it when messages may fail repeatedly and the system needs a safe limit before isolating poisoned work. In plain English, it gives operators a named control for controlled retry behavior, poison-message isolation, and clearer recovery workflow for consumers instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. Azure Service Bus intermediate 4 commands Aliases: Max delivery count, maximum delivery count, Service Bus maxDeliveryCount, MaxDeliveryCount, Service Bus delivery limit, Service Bus delivery attempts, Azure Service Bus Quick peek Open full term page

Integration verified Receive-and-delete mode A integration pattern or service capability in Messaging that helps teams connect services reliably without tightly coupling every component with clearer ownership, safety, and operational context. Messaging fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

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

Monitoring and Observability learning-path-anchor Throughput Throughput is the amount of work a system completes over time, such as requests, messages, bytes, events, or transactions per second. In Azure, teams measure it with service metrics, logs, and capacity settings to judge whether an app, database, storage account, or messaging pipeline can sustain demand. Performance intermediate 4 commands Aliases: Throughput, throughput, Azure Throughput, Microsoft Learn Throughput, requests per second, events per second, transactions per second, bytes per second, work completed over time Quick peek Open full term page

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

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

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

Analytics learning-path-anchor Synapse Spark pool A Synapse Spark pool is the workspace compute definition Azure Synapse uses to start Apache Spark sessions. It records node size, node count, autoscale behavior, runtime version, packages, and idle timeout so notebooks, Spark jobs, and pipelines get repeatable distributed processing. Synapse Analytics fundamentals 8 commands Aliases: Apache Spark pool, Spark pool, Synapse Apache Spark pool, serverless Spark pool Quick peek Open full term page

Analytics learning-path-anchor Synapse workspace managed identity A Synapse workspace managed identity is the workspace's own identity in Microsoft Entra ID. Instead of saving passwords, keys, or connection strings inside pipelines and notebooks, Synapse can use this identity to ask for tokens and reach trusted Azure resources. It is commonly used for Data Lake Storage, Key Vault, SQL, and linked service... Synapse Analytics intermediate 8 commands Aliases: Synapse managed service identity, Synapse MSI, workspace system-assigned identity, Synapse workspace identity Quick peek Open full term page

Databases premium Azure Managed Redis Azure Managed Redis is a Microsoft-managed in-memory data store based on Redis Enterprise, used for low-latency caching, session storage, messaging, and semantic cache scenarios. Managed cache intermediate 6 commands Aliases: Managed Redis, Redis Enterprise on Azure, Azure Redis Enterprise 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 subscription Service Bus subscription is a named receiver under a Service Bus topic. It behaves like a virtual queue: messages published to the topic are copied into the subscription when its rules match, and receivers read, lock, complete, defer, or dead-letter those subscription messages. Messaging fundamentals 6 commands Aliases: Azure Service Bus subscription, topic subscription, Service Bus topic subscription, subscription entity Quick peek Open full term page

Integration premium Service Bus topic Service Bus topic is a publish-subscribe entity inside a Service Bus namespace. Publishers send one message to the topic, and matching subscriptions receive their own copies. Topics are used when several downstream systems need the same business event without coupling the publisher to every receiver. Messaging fundamentals 6 commands Aliases: Azure Service Bus topic, Service Bus pub-sub topic, topic entity, broker topic 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 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

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

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 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 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 transaction Service Bus transaction is a broker-supported execution scope that commits or rolls back multiple messaging operations as one unit. Standard and Premium support transactions for sends, receives, completions, deferrals, dead-lettering, and related transfers, while management operations and Basic tier are outside that model. Messaging intermediate 5 commands Aliases: Azure Service Bus transaction, Service Bus transactional processing, broker transaction, atomic messaging operation Quick peek Open full term page

Analytics learning-path-anchor Synapse SQL CETAS Synapse SQL CETAS means CREATE EXTERNAL TABLE AS SELECT. It creates external table metadata and exports the result of a T-SQL SELECT statement in parallel to files in Azure Storage or Azure Data Lake Storage Gen2 for later SQL or lake consumption. Synapse Analytics fundamentals 6 commands Aliases: CREATE EXTERNAL TABLE AS SELECT, CETAS, Synapse CETAS, serverless SQL CETAS Quick peek Open full term page

Analytics learning-path-anchor Synapse SQL external table A Synapse SQL external table is database metadata that lets Synapse SQL query files stored outside the database, usually in Azure Storage or ADLS Gen2. It references an external data source, file format, and file location for governed SQL analytics. Synapse Analytics fundamentals 6 commands Aliases: external table in Synapse, Synapse external table, SQL external table, external table over lake files Quick peek Open full term page

Analytics learning-path-anchor Synapse SQL on-demand Synapse SQL on-demand is the serverless SQL pool model in Azure Synapse Analytics. It lets teams run T-SQL queries over data in the lake without provisioning dedicated warehouse capacity, storing only metadata objects while using external data sources, views, functions, and security objects. Synapse Analytics fundamentals 6 commands Aliases: SQL on-demand, Synapse serverless SQL, serverless SQL in Synapse, built-in serverless SQL pool Quick peek Open full term page

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

Analytics learning-path-anchor Synapse workspace firewall A Synapse workspace firewall is the IP allowlist around a Synapse workspace when it accepts public network traffic. It decides which client IPv4 ranges can attempt to connect before identity permissions are evaluated. It does not grant access by itself; a user or service still needs the right Azure, Synapse, or SQL permissions. It... Synapse Analytics intermediate 6 commands Aliases: Synapse IP firewall rule, workspace firewall rule, Synapse workspace IP allowlist, Synapse public endpoint firewall Quick peek Open full term page

Storage learning-path-anchor Sync group A sync group is the container that tells Azure File Sync which cloud file share and which Windows Server folders should stay synchronized. Think of it as one file namespace with a hub in Azure and one or more on-premises or edge locations attached to it. If two groups represent different shares or business... Files, queues, and tables fundamentals 6 commands Aliases: Azure File Sync group, file sync group, sync topology, storage sync group 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 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 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 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 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