Search Azure terms

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

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

Integration premium Service Bus premium tier The Service Bus premium tier is the namespace pricing and capability tier that allocates dedicated messaging units to Azure Service Bus. It is chosen for production scenarios that need resource isolation, predictable capacity, private networking, full JMS support, Premium metrics, and advanced resiliency options. Messaging fundamentals 4 commands Aliases: Azure Service Bus Premium tier, Premium messaging tier, Service Bus SKU Premium Quick peek Open full term page

Integration premium Service Bus private endpoint A Service Bus private endpoint is an Azure Private Link network interface that maps a virtual network to a Service Bus Premium namespace. It lets approved clients reach the namespace over private connectivity, reducing public exposure when DNS, network rules, and application routing are configured correctly. Service Bus advanced 4 commands Aliases: Azure Service Bus private endpoint, Service Bus Private Link, Private endpoint for Service Bus Quick peek Open full term page

Integration premium Service Bus queue A Service Bus queue is a brokered messaging entity that stores messages until one receiver can process them. It supports decoupled point-to-point communication, delivery locks, dead-letter handling, duplicate detection, sessions when enabled, and operational settings such as size, time to live, and forwarding. Messaging fundamentals 4 commands Aliases: Azure Service Bus queue, brokered queue, point-to-point Service Bus queue Quick peek Open full term page

Integration premium Service Bus rule A Service Bus rule is a named subscription rule on a topic subscription. It contains a filter condition, and optionally an action, so the subscription receives only matching topic messages or annotates selected messages before they are delivered to consumers. Messaging fundamentals 4 commands Aliases: Azure Service Bus rule, topic subscription rule, Service Bus filter rule Quick peek Open full term page

Integration premium Service Bus SAS policy A Service Bus SAS policy is a shared access authorization rule on a namespace, queue, or topic. It defines rights such as Send, Listen, or Manage and provides keys used to create shared access signature tokens or connection strings. for controlled access. Service Bus fundamentals 4 commands Aliases: Azure Service Bus SAS policy, Service Bus shared access policy, Service Bus authorization rule Quick peek Open full term page

Integration premium Service Bus session A Service Bus session groups related messages by SessionId so a receiver can process that ordered sequence together. Sessions support first-in, first-out handling, request-response workflows, and session state for queues or subscriptions that are created with sessions enabled. within supported tiers. Messaging fundamentals 4 commands Aliases: Azure Service Bus session, message session, SessionId in Service Bus Quick peek Open full term page

Integration premium Service Bus Standard Service Bus Standard is the shared-capacity Azure Service Bus tier that supports queues, topics, subscriptions, sessions, duplicate detection, transactions, scheduled messages, and forwarding. It is often used when advanced messaging features are needed without Premium dedicated capacity or isolation. for broad scenarios. Service Bus fundamentals 4 commands Aliases: Azure Service Bus Standard, Service Bus Standard tier, Standard Service Bus namespace 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 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 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 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

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 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 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 verified Peek-lock In Azure Service Bus, peek-lock is a receive pattern where the broker locks a message, returns it to one receiver, and waits for settlement. The receiver then completes, abandons, defers, dead-letters, or lets the lock expire, enabling at-least-once processing instead of immediate deletion. Service Bus intermediate 5 commands Aliases: peek lock, peek-lock processing, message lock, Service Bus lock, at-least-once receive Quick peek Open full term page

Integration verified Peek-lock receive mode Peek-lock receive mode is the Azure Service Bus client receive mode that locks a message instead of deleting it when received. The receiver must settle the message with complete, abandon, defer, or dead-letter actions, so failures can lead to redelivery rather than silent loss. Service Bus intermediate 5 commands Aliases: Service Bus PeekLock mode, PeekLock receive mode, ReceiveMode.PeekLock, at-least-once receive mode, locked receive mode Quick peek Open full term page

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

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

Integration field-manual-complete Subscription rule A subscription rule is the message-selection logic on an Azure Service Bus topic subscription. A topic can receive many messages, but each subscription usually needs only some of them. Rules decide which messages flow into that subscription by checking properties such as event type, customer, priority, region, or correlation ID. A rule can use SQL-like expressions or faster correlation matching, and it can optionally stamp matching messages with actions. Good rules keep consumers focused. Bad rules create missing messages, duplicate processing, or dead-letter confusion. Service Bus intermediate 5 commands Aliases: Service Bus subscription rule, topic subscription filter rule, Service Bus rule filter Quick peek Open full term page

Integration field-manual-complete Topic filter A topic filter is a Service Bus subscription rule that selects which messages from a topic are delivered to a subscription. Filters can match message properties with SQL expressions or correlation values, and matching rules can optionally apply actions before delivery. Service Bus intermediate 5 commands Aliases: Service Bus filter, subscription filter, topic subscription rule, SQL filter rule, correlation filter rule 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 complete SQL filter Microsoft Learn describes a SQL filter as a Service Bus topic subscription rule filter that uses a SQL-like expression over message system properties and application properties to decide whether a message is selected and copied into a subscription for routing. Messaging fundamentals 4 commands Aliases: Service Bus SQL filter, subscription SQL filter, SQL rule filter, topic subscription filter Quick peek Open full term page

Web premium Service Bus trigger Service Bus trigger is an Azure Functions binding that starts function execution when a message arrives on a Service Bus queue or topic subscription. It connects the Functions runtime to Service Bus, supports queue, topic, and session scenarios, and uses app settings or identity-based connections for access. Azure Functions intermediate 6 commands Aliases: Azure Functions Service Bus trigger, ServiceBusTrigger, Service Bus queue trigger, Service Bus topic trigger Quick peek Open full term page

Databases premium Azure SQL Business Critical tier Azure SQL Business Critical tier is a vCore service tier for OLTP workloads that need high transaction rates, low-latency I/O, and high resilience through isolated replicas. Azure SQL Database fundamentals 5 commands Aliases: Azure SQL Business Critical tier, Business Critical tier, BusinessCritical, Premium-like vCore tier, SQL Business Critical 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

AI and Machine Learning premium Azure OpenAI Service Azure OpenAI Service provides managed access to OpenAI model capabilities through Azure endpoints and enterprise controls. Generative AI fundamentals 11 commands Aliases: Azure OpenAI Quick peek Open full term page

Containers premium Azure Kubernetes Service Azure Kubernetes Service is Azure’s managed Kubernetes service for deploying, scaling, and operating containerized applications while Azure manages much of the cluster control plane. Managed Kubernetes advanced 6 commands Aliases: AKS, managed Kubernetes 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 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

AI and Machine Learning premium Azure AI Search service Azure AI Search service is the Azure resource that hosts Azure AI Search indexes, indexers, skillsets, keys, capacity, networking, and query endpoints. AI platform and search intermediate 4 commands Aliases: AI Search resource, AI Search service, Azure Search service, Search service, search service Quick peek Open full term page

AI and Machine Learning premium Azure AI services Azure AI services is the family of Azure cloud AI APIs and resources, surfaced through Foundry Tools, for vision, speech, language, translation, content, and generative scenarios. AI services fundamentals 4 commands Aliases: AI services, Azure AI services account, Cognitive Services, Foundry Tools Quick peek Open full term page

AI and Machine Learning premium Azure AI services account An Azure resource that provides endpoints, keys, identity, networking, billing, and monitoring for one or more Azure AI service capabilities. Azure AI services fundamentals 4 commands Aliases: AI services account, Azure AI multi-service resource, Foundry resource, Microsoft.CognitiveServices account Quick peek Open full term page

Databases premium Azure SQL service objective An Azure SQL service objective is the named performance level or SKU selected for an Azure SQL Database or elastic pool, defining resource limits, capabilities, and price within the chosen purchasing model. Azure SQL Database intermediate 4 commands Aliases: No aliases yet 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

AI and Machine Learning premium Azure OpenAI Azure OpenAI provides OpenAI model capabilities through Azure resources, deployments, identity, networking, quota, and monitoring controls. Azure OpenAI intermediate 8 commands Aliases: Azure OpenAI Service Quick peek Open full term page

Compute premium Azure Functions Azure Functions is Azure serverless compute for running code from triggers such as HTTP requests, queues, timers, events, and service integrations without managing servers. Serverless compute intermediate 6 commands Aliases: Functions, Function App, serverless functions Quick peek Open full term page

Web premium App Service connection string A named connection string stored in App Service configuration and exposed to application code for supported database or service connectivity. It helps learners understand where the concept appears in Azure operations and what to verify before changing it. App Service intermediate 5 commands Aliases: app service connection string, connection string Quick peek Open full term page