Search Azure terms

Analytics field-manual-complete Stream Analytics Azure Stream Analytics is a managed real-time analytics service for processing fast-moving event streams. It connects to inputs such as Event Hubs, IoT Hub, Blob Storage, or Data Lake Storage, runs SQL-like queries over the stream, and writes transformed results to supported outputs. Stream processing fundamentals 5 commands Aliases: Azure Stream Analytics, ASA, stream processing job, real-time analytics job, Stream Analytics Quick peek Open full term page

Analytics field-manual-complete Stream Analytics cluster A Stream Analytics cluster is a dedicated single-tenant environment for running Azure Stream Analytics jobs. It is intended for demanding streaming workloads, gives teams control over which jobs use the cluster, and supports private connectivity scenarios that are not covered by ordinary multi-tenant job placement. Stream Analytics intermediate 5 commands Aliases: Stream Analytics cluster, ASA cluster, dedicated Stream Analytics cluster, single-tenant Stream Analytics capacity Quick peek Open full term page

Analytics field-manual-complete Stream Analytics compatibility level Stream Analytics compatibility level is a job setting that controls selected runtime behaviors for query processing. It lets teams keep older jobs stable or opt into newer processing behavior, so changes in query semantics, partitioning, and supported features can be managed deliberately. Streaming analytics fundamentals 5 commands Aliases: Stream Analytics compatibility level, ASA compatibility level, job compatibility level, Stream Analytics runtime compatibility Quick peek Open full term page

Analytics field-manual-complete Stream Analytics function A Stream Analytics function is custom logic that can be invoked from a Stream Analytics query. Functions extend the SQL-like language for operations such as specialized calculations, string handling, enrichment, aggregation, or machine-learning scoring when built-in query expressions are not enough. Stream Analytics intermediate 5 commands Aliases: Stream Analytics function, ASA function, Stream Analytics user-defined function, JavaScript UDF for Stream Analytics Quick peek Open full term page

Analytics field-manual-complete Stream Analytics input A Stream Analytics input is a named connection between a Stream Analytics job and a data source. Inputs can represent live event streams or reference data, are used by name in the query, and define source type, serialization, authentication, and related connection settings. Streaming analytics fundamentals 5 commands Aliases: Stream Analytics input, ASA input, stream input, reference input for Stream Analytics Quick peek Open full term page

Analytics field-manual-complete Stream Analytics job A Stream Analytics job is the thing that actually runs your real-time processing. You give it input sources, a SQL-like query, optional functions, output destinations, and capacity settings. When the job starts, it continuously reads events, applies the query logic, and pushes results somewhere useful. For a learner, think of the job as the streaming application container. For an operator, it is the Azure resource you start, stop, scale, monitor, troubleshoot, secure, and include in deployment automation. Streaming analytics fundamentals 5 commands Aliases: Stream Analytics job, Azure Stream Analytics job, ASA job, streaming job, real-time analytics job Quick peek Open full term page

Analytics field-manual-complete Stream Analytics no-code editor The Stream Analytics no-code editor is a visual way to build a streaming job without typing the query yourself. You connect supported inputs, shape the data with drag-and-drop transformations, preview records, and choose outputs. Azure then creates a Stream Analytics job behind the experience. It is useful for analysts, platform teams, and engineers who need a quick, governed pipeline but do not want every small stream-processing task to become custom code. It still needs engineering review before production. Stream Analytics intermediate 5 commands Aliases: Stream Analytics no-code editor, ASA no-code editor, no-code Stream Analytics, drag-and-drop Stream Analytics editor, Stream Analytics visual editor Quick peek Open full term page

Analytics field-manual-complete Stream Analytics query A Stream Analytics query is the logic that turns incoming events into useful results. It looks like SQL, but it is built for streams, time windows, late events, joins, reference data, and continuous output. The query decides what fields to keep, what events to filter, how to group data, and where each result goes. For operators, a query is not just code; it is production behavior that can change alerts, dashboards, and records within seconds. Streaming analytics fundamentals 5 commands Aliases: Stream Analytics query, ASA query, Stream Analytics SQL query, streaming query, ASAQL query Quick peek Open full term page

Analytics field-manual-complete Stream Analytics reference data Stream Analytics reference data is the lookup table your stream uses while events are flowing. Instead of sending every business attribute inside each event, you keep stable or slowly changing information separately, such as device metadata, route codes, tariff bands, or product categories. The query joins live events to that reference set and produces richer output. The key idea is simple: events tell you what happened now, while reference data explains what that event means in the business context your operators care about. Streaming analytics intermediate 5 commands Aliases: Azure Stream Analytics reference data, reference data input, ASA reference data, lookup data for Stream Analytics Quick peek Open full term page

Analytics field-manual-complete Stream Analytics watermark A Stream Analytics watermark is the job’s best answer to the question, “How far through event time are we?” Streaming data does not always arrive in perfect order. Devices can be offline, brokers can buffer messages, and clocks can drift. The watermark lets the service decide when it is safe to close a time window and produce output. A larger tolerance accepts more late data but delays results. A smaller tolerance produces faster answers but may drop or adjust late events. Streaming analytics fundamentals 5 commands Aliases: Azure Stream Analytics watermark, ASA watermark, event-time watermark, watermark delay Quick peek Open full term page

Analytics field-manual-complete Stream Analytics windowing function A Stream Analytics windowing function lets you ask questions about events over time instead of one event at a time. You might count transactions every minute, average machine temperature over five minutes, detect user activity sessions, or compare current values with a snapshot. The window defines which events belong together before the query aggregates them. Choosing the wrong window can make alerts noisy, late, or misleading, so it is one of the most important design choices in a streaming query. Streaming analytics fundamentals 5 commands Aliases: Azure Stream Analytics windowing function, ASA window function, temporal window, streaming window function Quick peek Open full term page

Analytics field-manual-complete Stream Analytics job diagram A Stream Analytics job diagram is a visual map of what the job is doing. Instead of reading only a query file and metric table, you can see inputs, query steps, outputs, and sometimes physical streaming nodes on one canvas. It is especially helpful when a job runs but produces no results, late results, or results that look wrong. The diagram gives developers and operators a faster way to narrow the problem before rewriting the query or scaling blindly. Stream Analytics intermediate 4 commands Aliases: Stream Analytics job diagram, ASA job diagram, Stream Analytics logical diagram, Stream Analytics physical diagram, job diagram preview Quick peek Open full term page

Analytics field-manual-complete Stream Analytics output A Stream Analytics output is where processed events go after the query runs. It might be a storage account, SQL table, Event Hubs stream, Cosmos DB container, Azure Data Explorer table, Power BI dataset, Azure Function, or another supported sink. The output name is used in the query, so a small naming or schema mistake can send results nowhere useful. For operators, outputs are the handoff point between real-time processing and the systems people actually read, alert from, or store. Streaming analytics fundamentals 4 commands Aliases: Stream Analytics output, ASA output, Stream Analytics sink, output sink, query output destination Quick peek Open full term page

Analytics field-manual-complete Streaming unit A streaming unit is the capacity dial for an Azure Stream Analytics job. When the job needs more compute and memory to keep up with input events, you adjust streaming units rather than managing servers. More SUs can help a job process higher volume, but they are not magic. The query must be able to use the capacity, the inputs need useful partitioning, and the outputs must keep up. Operators treat SUs as a cost and performance lever that must be measured, not guessed. Streaming analytics fundamentals 5 commands Aliases: Azure Stream Analytics streaming unit, Stream Analytics SU, SUs, streaming units Quick peek Open full term page

Web premium Event Hub trigger An Event Hub trigger is an Azure Functions trigger binding that runs a function when events are available from an Azure Event Hub stream. Teams use it to process streaming events with serverless function code instead of running a dedicated worker service for every Event Hubs consumer workload. It is not the event hub itself, a producer, a capture archive, or a guarantee that downstream business processing completed successfully. 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. Azure Functions intermediate 5 commands Aliases: Azure Functions Event Hub trigger, Event Hubs trigger, Event Hubs trigger binding 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 capture Event Hubs Capture automatically writes streaming data from an event hub to Azure Blob Storage or Azure Data Lake Storage based on configured time or size intervals. Teams use it to archive raw event streams to storage for analytics, compliance, replay, or lakehouse ingestion without writing a separate capture consumer. It is not a consumer group, a checkpoint, a data transformation job, or a guarantee that downstream analytics has already processed the archived files. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs Capture, Capture Streaming Events, Event Hubs archive capture Quick peek Open full term page

Integration premium Event Hubs consumer An Event Hubs consumer is an application or service instance that reads events from partitions of an event hub through a consumer group. Teams use it to read and process events from an Event Hub stream for analytics, automation, storage, monitoring, or business applications. It is not a producer, a consumer group definition by itself, a Capture archive, or proof that the application processed events correctly. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs consumer, Event Hubs reader, event stream consumer Quick peek Open full term page

Integration premium Event Hubs 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 processor An event processor is an application component that reads events from partitions, coordinates ownership, processes events, and records checkpoints for recovery. Teams use it to scale consumers across partitions while keeping track of where processing should resume after restarts or failures. It is not a producer, event hub namespace, consumer group by itself, checkpoint store alone, or proof that downstream business work cannot fail. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: EventProcessorClient, stream processor, event processing application Quick peek Open full term page

Analytics premium Session window A session window is an Azure Stream Analytics windowing function that groups events separated by no more than a configured timeout. The window starts with the first event, extends while related events keep arriving, and closes when inactivity or maximum duration ends the session. Stream Analytics intermediate 5 commands Aliases: Session window, session-window, session window, Session-window Quick peek Open full term page

Storage premium Trusted Microsoft services for storage Trusted Microsoft services for Azure Storage are specific Azure services that Microsoft documents as eligible for storage firewall exceptions. Depending on the service, access may be based on tenant registration, supported operations, or managed identity authorization combined with Azure RBAC or Data Lake ACLs. Storage platform intermediate 5 commands Aliases: trusted Azure services for Storage, storage trusted services list, Azure Storage trusted services, trusted services storage firewall Quick peek Open full term page

Analytics premium Tumbling window In Azure Stream Analytics, a tumbling window groups events into fixed-size, non-overlapping, contiguous time intervals. Each event belongs to only one window, making the function useful for periodic aggregations such as counts, averages, totals, or alerts over live streaming data. Stream Analytics intermediate 5 commands Aliases: TumblingWindow, TUMBLINGWINDOW, tumbling window function, fixed non-overlapping window Quick peek Open full term page

Analytics premium Auto Loader Auto Loader is the Azure Databricks feature that watches cloud storage and brings in new files without forcing engineers to rescan everything manually. In plain terms, it is a safer ingestion pattern for folders that keep receiving CSV, JSON, Parquet, images, or other data files. It can process existing files, then continue with new. Analytics platform intermediate 4 commands Aliases: Databricks Auto Loader, cloudFiles, Auto Loader cloud files, Lakeflow Auto Loader Quick peek Open full term page

Analytics premium Hopping window Hopping window is a Stream Analytics time window that moves forward by a fixed hop while each event can belong to more than one overlapping window. Stream Analytics intermediate 4 commands Aliases: HOPPINGWINDOW, Stream Analytics hopping window, Hopping window, hopping-window 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

Analytics field-manual-complete Late arrival policy A late arrival policy in Azure Stream Analytics defines how events are handled when their event timestamp is older than their arrival time beyond the configured late-arrival tolerance. Microsoft Learn describes late and out-of-order behavior, including dropping events or adjusting timestamps when TIMESTAMP BY is used. Streaming analytics intermediate 10 commands Aliases: No aliases yet Quick peek Open full term page

Analytics verified Windowing function A windowing function in Azure Stream Analytics defines time boundaries for processing continuous events. Tumbling, hopping, sliding, session, and snapshot windows let queries aggregate, join, and detect patterns across event-time periods instead of evaluating each incoming event as a standalone record. Stream Analytics intermediate 6 commands Aliases: Stream Analytics windowing function, temporal window, streaming window, Azure Stream Analytics window 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

Analytics complete Sliding window Microsoft Learn describes sliding windows in Azure Stream Analytics as time windows that produce output when events enter or exit the window. They evaluate changing groups of events across a defined duration, making them useful for near-real-time calculations such as rolling counts, moving averages, or threshold detection. Stream Analytics intermediate 6 commands Aliases: Sliding window function, Stream Analytics sliding window, rolling time window Quick peek Open full term page

Analytics verified Reference data Reference data is the lookup information your streaming job needs but does not receive as live events. Think device catalogs, store locations, tariff codes, risk bands, or product mappings. In Azure Stream Analytics, the event stream keeps moving while reference data supplies Stream Analytics intermediate 5 commands Aliases: Azure Stream Analytics reference data, lookup data, slowly changing lookup data, streaming reference dataset Quick peek Open full term page

Analytics verified Reference data input A reference data input is the wiring between a Stream Analytics job and the lookup data it needs. The reference data is the table or file; the input is the job setting that says where that data lives, what alias the query Streaming analytics fundamentals 5 commands Aliases: Stream Analytics reference input, reference input alias, reference lookup input Quick peek Open full term page

Analytics verified Watermark In Azure Stream Analytics, a watermark is the engine's event-time progress marker. It advances from observed event times and configured tolerance windows, letting the job decide when a time window is complete enough to emit repeatable, timely results at scale. Stream processing intermediate 5 commands Aliases: Azure Stream Analytics watermark, event-time watermark, streaming watermark, watermark time Quick peek Open full term page

Analytics verified Watermark delay Watermark delay is the visible waiting time created when Azure Stream Analytics holds event-time output until late-arrival and out-of-order tolerances are satisfied. It reflects a deliberate accuracy-versus-latency choice, especially when events arrive late, partitions are sparse, or TIMESTAMP BY is used. Stream Analytics intermediate 5 commands Aliases: Stream Analytics watermark delay, event-time output delay, late arrival delay, out-of-order tolerance delay Quick peek Open full term page

Analytics verified Window function A window function in Azure Stream Analytics groups streaming events into time-based windows so queries can aggregate data across bounded periods. Tumbling, hopping, sliding, session, and snapshot windows let jobs calculate counts, averages, or patterns over event-time intervals rather than treating every event as isolated. Stream Analytics intermediate 5 commands Aliases: Stream Analytics window function, windowing function, temporal window, TumblingWindow, HoppingWindow Quick peek Open full term page

Integration top-250-pre130-priority-upgraded Event Hubs consumer group Event Hubs consumer group is an independent view over an Event Hubs event stream that lets a consuming application maintain its own read position without interfering with other consumers in Azure. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs consumer group, Event Hubs reader group, consumer group, Event Hubs consumer group Quick peek Open full term page

Analytics verified Out-of-order event policy An out-of-order event policy in Azure Stream Analytics defines how a job handles events that arrive with timestamps earlier than the expected event time. The policy uses a configured tolerance window and action, such as adjusting the timestamp or dropping the event, to protect streaming results. Streaming analytics intermediate 4 commands Aliases: Stream Analytics out-of-order policy, out-of-order tolerance, event ordering tolerance, out-of-order event handling Quick peek Open full term page

Databases premium PostgreSQL log analytics PostgreSQL log analytics means collecting PostgreSQL flexible server logs in Azure Monitor so operators can search them, build alerts, and investigate problems with KQL. Instead of downloading log files manually or guessing from symptoms, teams route PostgreSQLLogs and related categories to a Log Analytics workspace. The value comes from patterns: failed connections, slow queries, audit events, PgBouncer signals, configuration effects, and workload changes. It is not free and not automatically useful; teams must choose categories, retention, workspace access, alert logic, and dashboards that match the database risk. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL log analytics, postgresql log analytics, Azure Database for PostgreSQL flexible server Quick peek Open full term page

Web field-manual-complete App Service log stream App Service log stream is the live tail for an App Service app. App Service diagnostics intermediate 5 commands Aliases: Azure App Service log stream, app service log stream Quick peek Open full term page

Analytics field-manual-complete Streaming ingestion Streaming ingestion is the path that gets fresh events into Azure Data Explorer quickly, often within seconds, instead of waiting for larger batch ingestion cycles. It is useful for operational telemetry, logs, alerts, and near-real-time analytics where people need to query the newest data quickly. It is not the best answer for every high-volume table; queued ingestion may be better for large sustained loads. The practical decision is latency versus throughput efficiency, table design, mapping quality, and operational cost. Azure Data Explorer intermediate 5 commands Aliases: Azure Data Explorer streaming ingestion, ADX streaming ingestion, Kusto streaming ingestion, low latency ingestion Quick peek Open full term page

Analytics premium Azure Synapse Analytics Azure Synapse Analytics is Microsoft’s integrated analytics service for enterprise data warehousing, big data, data integration, and exploratory analytics. Synapse Analytics intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Data Lake analytics workload A production analytics workload that stores, transforms, governs, and serves large data sets from a data lake using Azure services such as ADLS Gen2, Data Factory, Databricks, Synapse, or Fabric. Data Lake Storage Intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Identity premium Log Analytics Data Reader A Log Analytics Data Reader assignment is an Azure built-in RBAC role for letting approved users, groups, or workload identities query the Log Analytics logs they are allowed to view across workspaces and tables without granting workspace administration, table management, or broader monitoring control. Azure RBAC fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium Log Analytics table A Log Analytics table is the named storage structure inside a Log Analytics workspace that holds one kind of Azure Monitor log record, with its own schema, plan, retention behavior, access considerations, and KQL query patterns for troubleshooting, analytics, and compliance. Azure Monitor Logs fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Monitoring and Observability premium Log Analytics workspace A Log Analytics workspace is the Azure Monitor Logs data store where collected log records are retained, secured, queried with KQL, and used by alerts, workbooks, Microsoft Sentinel, Application Insights, and operations teams to troubleshoot and govern Azure workloads in governed production environments. Azure Monitor Logs fundamentals 4 commands Aliases: workspace, LAW Quick peek Open full term page

Containers verified Container Apps log stream A live log stream for a Container App replica or revision. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Storage field-manual-complete Storage analytics logs Storage Analytics logs are classic Azure Storage logs that record details about successful and failed requests for Blob, Queue, and Table services. They help troubleshoot request-level behavior, but Azure Monitor storage logs are generally preferred for modern monitoring, querying, alerting, and centralized retention. Storage monitoring fundamentals 5 commands Aliases: classic storage logs, Azure Storage Analytics logging, storage request logs Quick peek Open full term page

Analytics learning-path-anchor Databricks Photon The native vectorized Azure Databricks engine for accelerating eligible SQL, DataFrame, ETL, and streaming workloads. Databricks intermediate 4 commands Aliases: Photon engine, Photon acceleration, Databricks vectorized engine 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

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