Search Azure terms

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

Internet of Things premium Device identity A device identity is the IoT Hub identity registry entry that represents a permitted device or module, including its device ID, authentication material, status, and connection-related metadata. IoT identity fundamentals 4 commands Aliases: IoT Hub device identity, IoT device registry identity, device registry entry, IoT device ID Quick peek Open full term page

Internet of Things premium Device Provisioning Service Device Provisioning Service is an Azure IoT helper service that enables zero-touch, just-in-time provisioning of devices to one or more linked IoT hubs using enrollments and allocation policies. IoT provisioning fundamentals 4 commands Aliases: Azure IoT Hub Device Provisioning Service, IoT DPS, DPS, zero-touch device provisioning Quick peek Open full term page

Internet of Things premium Device twin A device twin is the IoT Hub JSON document that stores device metadata, tags, desired properties, and reported properties so cloud applications and devices can synchronize configuration and state. Device state fundamentals 4 commands Aliases: IoT Hub device twin, device twin properties, twin desired properties, twin reported properties 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 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

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

AI and Machine Learning learning-path-anchor Text to speech Text to speech in Azure AI Speech converts written text or SSML into synthesized audio using neural voices, custom voice options, language support, and APIs. Teams use it to add spoken responses to apps, contact centers, accessibility tools, devices, and media workflows while governing region, keys, networking, and quota. Azure AI services fundamentals 4 commands Aliases: Text to speech, text to speech, Azure Text to speech, Microsoft Learn Text to speech, TTS, speech synthesis, Azure AI Speech synthesis, neural voices, SSML speech 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

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

Storage command-rich Table row key A Table row key is the unique name of an entity inside one Azure Table partition. PartitionKey gets you to the right group; RowKey identifies the exact record in that group. Together they form the entity primary key. RowKey design often carries an order ID, device ID, timestamp pattern, sequence number, or composite value. It matters because point reads, updates, deletes, duplicate detection, and... Storage platform intermediate 5 commands Aliases: Azure Table RowKey, Table Storage RowKey, Table row key value, RowKey property Quick peek Open full term page

Databases command-rich Cosmos DB for Table Azure Cosmos DB for Table is a managed NoSQL key-value and table API compatible with Azure Table storage SDKs and tools. Data platform intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

App and integration services field-manual-complete Notification Hubs Azure Notification Hubs is the Azure service teams use to send push notifications to mobile apps and connected devices. Instead of every backend talking separately to Apple, Google, or other platform notification systems, the app registers devices with a hub and the backend sends messages through that hub. It is useful for alerts, reminders, promotions, operational updates, and personalized messages. Notification Hubs does not replace the mobile app or messaging strategy; it provides the scalable push delivery layer behind them. Mobile messaging intermediate 4 commands Aliases: Azure Notification Hubs 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

Databases premium Cosmos DB spatial index Cosmos DB spatial index is an indexing-policy entry that helps Cosmos DB for NoSQL query valid GeoJSON points, lines, polygons, and multipolygons efficiently. It makes location-aware queries practical without scanning every item in a container. You see it when applications store coordinates, service areas, delivery zones, device positions, or map features in JSON items. The production check is whether GeoJSON shape, indexed path, query function, and partition strategy all line up. Document the decision in code, templates, metrics, and runbooks. Azure Cosmos DB intermediate 7 commands Aliases: No aliases yet 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 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

Databases premium Foreign key A foreign key is a column or set of columns that links rows in one table to key values in another table and helps enforce referential integrity. Teams use it to keep child records such as orders, invoices, payments, devices, or claim lines tied to valid parent records instead of allowing orphaned data to silently enter the database. It is not an index by itself, a security boundary, a substitute for business validation, or an enforced guarantee in every Azure analytics engine that can store a declared relationship. Relational database intermediate 6 commands Aliases: FK, foreign key constraint, referential constraint, SQL foreign key 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 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

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

Storage premium Service SAS A service SAS is a shared access signature that delegates limited access to a specific Azure Storage service resource, such as a blob, queue, table, or file. It is signed with a storage account key and constrains permissions, resource scope, protocol, IP range, and expiry time. Blob Storage fundamentals 6 commands Aliases: Azure Storage service SAS, Service SAS, service sas, service shared access signature, service-sas, storage service SAS Quick peek Open full term page

Identity premium Azure tenant An Azure tenant is the Microsoft Entra directory that provides identity and access management for users, groups, applications, service principals, devices, and Azure resources associated with an organization. Azure identity fundamentals 5 commands Aliases: tenant, Microsoft Entra tenant, tenant ID Quick peek Open full term page

Virtual Desktop Infrastructure premium Azure Virtual Desktop Azure Virtual Desktop is a desktop and app virtualization service that runs on Azure, delivering Windows desktops and RemoteApp experiences with host pools, session hosts, and flexible control. Virtual desktops fundamentals 5 commands Aliases: AVD 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 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 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 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 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 producer An Event Hubs producer is an application, service, device, or client that sends events to an event hub. Teams use it to identify the workload that publishes telemetry, transactions, logs, or business events into an Event Hubs stream. It is not a consumer, event processor, checkpoint, storage capture destination, or proof that downstream systems processed the event. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: producer, event publisher, Event Hubs publisher client Quick peek Open full term page

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

AI and Machine Learning premium Foundry Local Foundry Local is an on-device AI runtime and SDK for shipping applications that run curated generative AI models locally on user hardware. Microsoft Foundry intermediate 5 commands Aliases: Microsoft Foundry Local, Foundry Local CLI, on-device AI inference, local AI runtime Quick peek Open full term page

Internet of Things premium IoT Edge IoT Edge is the Azure IoT runtime and deployment pattern that runs cloud-managed container modules on local edge devices while communicating with IoT Hub. Edge computing intermediate 5 commands Aliases: Azure IoT Edge, IoT Edge runtime, edge modules, edgeAgent, edgeHub, edge device 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

Storage premium Table entity A Table entity is one record in Azure Table Storage. It behaves like a flexible row: it must have a PartitionKey and RowKey, it gets a service-managed Timestamp, and it can carry custom properties that your application defines. Unlike a relational row, entities in the same table do not have to share every property. That flexibility is useful for metadata, device state, user preferences,... Table Storage fundamentals 5 commands Aliases: Azure Table entity, Table Storage entity, entity in Azure Table Storage, Azure Tables entity Quick peek Open full term page

Storage premium Table property A Table property is one named value on an Azure Table entity. Some properties are required system fields, such as PartitionKey, RowKey, and Timestamp. The rest are custom fields that your application chooses, such as status, amount, device version, or retry count. Properties make Table Storage flexible because different entities can carry different sets of fields. That flexibility is useful, but it also means... Table Storage fundamentals 5 commands Aliases: Azure Table property, Table Storage property, entity property, custom Table property 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