Search Azure terms

Networking premium Application Gateway routing rule the Application Gateway component that connects a listener to a backend pool, backend settings, redirect, or path-based routing decision. Application delivery and API edge intermediate 4 commands Aliases: Application Gateway routing rule, application gateway routing rule Quick peek Open full term page

Storage learning-path-anchor Table service endpoint A Table service endpoint is the address your application uses when it talks to Azure Table Storage. For a normal Azure Storage account, it looks like an account-specific table URL. That address is not just a string in a connection setting; it determines DNS resolution, firewall evaluation, private endpoint routing, TLS, SDK configuration, and what operators test during an outage. If the endpoint is wrong, the table might exist and credentials might be valid, but clients still fail to connect. Table Storage intermediate 5 commands Aliases: Azure Table endpoint, Table Storage endpoint, storage table endpoint, Table data-plane endpoint Quick peek Open full term page

Management and Governance learning-path-anchor Tagging strategy A tagging strategy is the playbook for using tags without making a mess. It answers simple but important questions: which tags are required, who owns the list, which values are allowed, where tags are applied, and what happens when a resource is missing one. Without a strategy, tags become random notes. With a strategy, tags become a dependable system for cost allocation, ownership, lifecycle cleanup, compliance evidence, and operational routing. The best strategies are small enough to follow and strict enough to m Tags and naming fundamentals 5 commands Aliases: Azure tagging strategy, tag governance strategy, tag taxonomy, resource tagging standard Quick peek Open full term page

Databases learning-path-anchor Cosmos DB dedicated gateway Azure Cosmos DB dedicated gateway is provisioned server-side compute that fronts an account and enables the integrated cache for supported NoSQL workloads. Azure Cosmos DB fundamentals 3 commands Aliases: No aliases yet 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

Networking premium ExpressRoute ExpressRoute lets organizations extend on-premises networks into Microsoft cloud services over private connectivity provided through a connectivity provider. Teams use it to connect datacenters, branches, or colocation environments to Azure with predictable private paths for workloads that need stronger latency, bandwidth, and routing control than public internet connections. It is not a VPN tunnel, a private endpoint, an internet performance guarantee, or proof that every connected application is secure, redundant, or correctly routed. In production, confirm circuit state, provider state, peering configuration, BGP routes, gateway SKU, connected virtual networks, bandwidth, metrics, DNS path, firewall path, and provider escalation details before. Hybrid connectivity intermediate 6 commands Aliases: Azure ExpressRoute, ExpressRoute circuit, private Microsoft cloud connectivity 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

Storage premium Service endpoint for Storage A service endpoint for Storage enables the Microsoft.Storage endpoint on a virtual network subnet and pairs it with storage account network rules. It lets workloads in that subnet reach Azure Storage over the Microsoft backbone while the account firewall allows only approved virtual network sources. Storage platform intermediate 6 commands Aliases: Azure Storage VNet rule, Microsoft.Storage service endpoint, Service endpoint for Storage, Storage service endpoint, service endpoint for storage, service-endpoint-for-storage Quick peek Open full term page

Monitoring and Observability premium Action group An Azure Monitor action group defines who gets notified and which actions run when an alert fires. It can include notification receivers such as email, SMS, and push, plus automation actions such as webhooks, secure webhooks, Azure Functions, Logic Apps, runbooks, ITSM, or Event Hubs. Alerts fundamentals 5 commands Aliases: Azure Monitor action group, alert action group, monitor action group Quick peek Open full term page

Databases premium Active geo-replication Active geo-replication is an Azure SQL Database business-continuity feature that continuously replicates one primary database to a readable secondary database, often in another Azure region. It supports manual or programmatic geo-failover for individual databases and can also serve read-only workloads from the secondary. Azure SQL continuity advanced 5 commands Aliases: Azure SQL active geo-replication, geo-secondary, geo-replica Quick peek Open full term page

Containers premium AKS ingress controller Microsoft Learn explains AKS ingress through Kubernetes ingress resources and controllers that route HTTP or HTTPS traffic to services in a cluster. AKS application routing options can configure ingress controllers, DNS integration, TLS handling, and related networking components for production applications. AKS networking intermediate 5 commands Aliases: AKS ingress, Ingress controller for AKS, Kubernetes ingress controller Quick peek Open full term page

Web premium App Service VNet integration Microsoft Learn describes App Service virtual network integration as the feature that lets an App Service app access resources in or through an Azure virtual network. It affects outbound traffic from the app; inbound private access uses other controls, such as private endpoints and access restrictions. App Service Networking intermediate 5 commands Aliases: App Service virtual network integration, regional VNet integration, Web App VNet integration Quick peek Open full term page

AI and Machine Learning premium Batch deployment A batch deployment in Azure Machine Learning is the deployment configuration behind a batch endpoint, defining the model or pipeline, compute, environment, and execution behavior for asynchronous inference. Azure Machine Learning intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

DevOps premium Canary deployment Canary deployment is a release approach that sends a small portion of real traffic to a new version before rolling it out broadly. Deployment workflows intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps session an isolated, short-lived execution environment from a Container Apps dynamic session pool, often used for sandboxed code or custom runtime tasks Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps traffic split percentage-based Container Apps ingress routing that sends traffic to active revisions or labels for canary, blue-green, or A/B releases Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Cosmos DB partition key value Cosmos DB partition key value means the actual value stored on an item for the configured partition key path in Azure Cosmos DB. In plain English, it is the thing developers and operators check when they need to understand how data access really works. It connects the application model to routing items into logical partitions, enabling efficient point reads, transactional scope, and balanced throughput. For a production team, it turns vague database talk into a specific thing to inspect in the portal, SDK code, templates, metrics, and incident notes. Azure Cosmos DB intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Analytics premium Databricks workspace VNet injection Databricks workspace VNet injection is the deployment model that places Azure Databricks compute resources into customer-managed virtual network subnets so network security, routing, and private connectivity controls can be applied. Databricks advanced 5 commands Aliases: VNet-injected Databricks workspace, customer-managed VNet workspace, Databricks VNet injection, workspace in customer VNet Quick peek Open full term page

AI and Machine Learning premium Document classifier A document classifier is a Document Intelligence custom classification model that identifies document types or pages before extraction and routing. Document Intelligence intermediate 5 commands Aliases: custom classifier, Document Intelligence classifier, classification model, page classifier 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

Networking premium Front Door Azure Front Door is Microsoft’s global edge service for modern web applications. Microsoft Learn describes it as a cloud CDN that provides fast, reliable, and secure access to static and dynamic content through Microsoft’s global edge network worldwide. Application delivery and API edge intermediate 5 commands Aliases: Azure Front Door, AFD, Azure Front Door Standard, Azure Front Door Premium, global edge Quick peek Open full term page

Networking premium Front Door origin group A Front Door origin group is a logical grouping of origins that receives similar traffic and controls health probing and load balancing behavior. Application delivery and API edge intermediate 5 commands Aliases: Azure Front Door origin group, AFD origin group, backend pool in Front Door, origin pool Quick peek Open full term page

Networking premium Front Door profile Front Door profile is the top-level Azure Front Door Standard or Premium resource that groups edge endpoints, routes, origins, domains, rule sets, security associations, and delivery settings. Teams use it to manage a global application entry point without treating each endpoint, route, or origin as a separate product. In daily Azure work, it shows up when engineers review edge architecture, add a new website, tune routing, attach custom domains, configure WAF, or troubleshoot global traffic. It is not the same thing as a single endpoint, DNS name, backend app, CDN cache rule, or web application firewall policy. Application delivery and API edge intermediate 5 commands Aliases: Azure Front Door profile, AFD profile, Front Door Standard/Premium profile Quick peek Open full term page

Networking premium Ingress Ingress controls how users, APIs, partners, and internal services can reach a workload and which network controls protect that entry point. Teams see it in container apps ingress settings, kubernetes ingress controllers. It is not egress, a firewall rule alone, a load balancer backend pool, or an application route inside code; confusing them can create public exposure, unreachable apps. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Application Networking Fundamentals 5 commands Aliases: incoming application traffic, inbound app traffic, Container Apps ingress, external ingress, internal ingress Quick peek Open full term page

AI and Machine Learning premium Invoice model Invoice model controls how teams automate invoice data extraction before routing results into approvals, ERP systems, payment workflows, audits, or exception handling queues. Teams see it in document intelligence studio, prebuilt invoice api calls. It is not a custom document model, a receipt model, an invoice section in billing, an accounting system, or a generative model that summarizes documents; confusing them can create incorrect payment amounts, missed line items. 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. Document Intelligence Intermediate 5 commands Aliases: prebuilt invoice model, Document Intelligence invoice model, invoice extraction model, invoice processing model Quick peek Open full term page

AI and Machine Learning premium Key phrase extraction Key phrase extraction controls how text-mining workloads turn comments, claims, documents, and support tickets into searchable phrases for search, analytics, routing, and review. Teams see it in azure ai language resources, azure ai search skillsets. It is not keyword search, entity recognition, sentiment analysis, embeddings, semantic ranking, or manually authored metadata tags; confusing them can create missing important topics, noisy tags. 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. Language and search enrichment Intermediate 5 commands Aliases: Azure Language key phrase extraction, key phrase skill, KeyPhraseExtractionSkill, key phrases Quick peek Open full term page

Containers premium Kubenet Kubenet is an AKS network plugin where nodes receive virtual network IP addresses and pods receive IP addresses from a separate pod CIDR, with routing handled through user-defined routes. AKS networking Intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

AI and Machine Learning premium Sentiment analysis Sentiment analysis in Azure AI Language evaluates text and returns sentiment labels such as positive, neutral, negative, or mixed, with confidence scores at document and sentence level. Microsoft has announced retirement of this Azure Language feature after the support window, so production planning should include migration options. Azure AI Language fundamentals 5 commands Aliases: Azure sentiment analysis, text sentiment analysis, sentiment and opinion mining, Azure AI Language sentiment Quick peek Open full term page

Web premium Serverless API deployment Serverless API deployment in Azure commonly means publishing HTTP-triggered Azure Functions, often with zip deployment, run-from-package, Static Web Apps APIs, or API Management integration. The deployment packages code, configuration, identity, routing, and monitoring so an API endpoint can scale without dedicated server management. Azure Functions intermediate 5 commands Aliases: serverless API release, Azure Functions API deployment, HTTP trigger deployment, function API deployment 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 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