Search Azure terms

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

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

Web premium Functions Premium plan Functions Premium plan is a hosting plan for Azure Functions that keeps capacity ready while still supporting event-driven scaling for serverless workloads. Teams use it to reduce cold starts, run longer or heavier functions, use VNet integration, and control minimum and maximum capacity more deliberately than Consumption hosting. In daily Azure work, it appears when engineers stabilize latency-sensitive APIs, connect functions to private dependencies, prepare for event spikes, or replace overprovisioned dedicated App Service capacity. It is not a free tier, a guarantee that code is efficient, unlimited scale, or a substitute for trigger tuning and dependency performance testing. Azure Functions hosting advanced 6 commands Aliases: Elastic Premium plan, Azure Functions Premium, EP plan Quick peek Open full term page

Analytics premium Azure integration runtime Azure integration runtime is the compute infrastructure used by Azure Data Factory and Synapse pipelines to move data, dispatch activities, and connect across network environments. Data integration compute intermediate 5 commands Aliases: Integration Runtime, IR, ADF integration runtime Quick peek Open full term page

AI and Machine Learning premium Azure Machine Learning Azure Machine Learning is a cloud service for managing the machine learning lifecycle, including workspaces, data, training jobs, model deployment, monitoring, and MLOps. Machine learning operations advanced 5 commands Aliases: Azure ML, AML, Machine Learning workspace Quick peek Open full term page

Web premium Dedicated Functions plan An Azure Functions hosting option that runs on an App Service plan. Azure Functions intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Compute premium Durable Functions Microsoft Learn describes Durable Functions as an Azure Functions extension for building stateful workflows in a serverless environment. Developers write orchestrator, activity, and entity functions while the runtime manages checkpoints, state, retries, timers, recovery, and long-running operations across restarts and long delays. Serverless workflows intermediate 5 commands Aliases: Azure Durable Functions, Durable orchestration, Durable workflow Quick peek Open full term page

Web premium Functions scale controller Functions scale controller is the Azure Functions component that watches trigger workload signals and decides how many app instances should run. Teams use it to match serverless capacity to event demand without manually adding workers for every queue, event stream, timer, or HTTP workload. In daily Azure work, it appears when engineers investigate backlog growth, explain unexpected scale-out, tune trigger concurrency, enable scale logs, or decide whether Premium capacity is necessary. It is not an application scheduler, a guaranteed throughput contract, a replacement for downstream capacity, or a setting that can fix inefficient function code by itself. Azure Functions scaling advanced 4 commands Aliases: Azure Functions scale controller, scale controller, Functions autoscale controller Quick peek Open full term page

Web complete Static Web Apps managed functions Built-in Azure Functions APIs deployed and managed with an Azure Static Web Apps site. Static Web Apps intermediate 5 commands Aliases: static-web-apps-managed-functions, Static Web Apps managed functions, SWA managed functions, managed Functions API, Static Web Apps built-in API, Static Web Apps /api functions Quick peek Open full term page

Databases premium Cosmos DB trigger Cosmos DB trigger is a registered JavaScript pre-trigger or post-trigger for Cosmos DB for NoSQL operations inside a container. It runs server-side logic around an item operation when application code explicitly asks Cosmos DB to use it. You see it when teams maintain legacy NoSQL scripts, troubleshoot write behavior, or compare triggers with change feed and Azure Functions. The production check is whether the trigger is necessary, explicitly invoked, partition-scoped, tested, and safer than handling the logic in application code. Document the decision in code, templates, metrics, and runbooks. Azure Cosmos DB intermediate 8 commands Aliases: No aliases yet Quick peek Open full term page

Web premium Extension bundle An Extension bundle in Azure Functions is a packaged set of binding extensions that non-.NET function apps can reference from host.json. Teams use it to enable triggers and bindings such as Storage, Service Bus, Event Hubs, Cosmos DB, and Timer support without manually installing individual .NET extension packages. It is not the function runtime itself, an application dependency lock file, a deployment slot, or a guarantee that every trigger version supports every identity or feature. Azure Functions intermediate 6 commands Aliases: Azure Functions extension bundle, Functions extension bundle, binding extension bundle Quick peek Open full term page

Developer Tools premium Feature flag A Feature flag is a configuration value that controls whether application code for a feature is enabled, disabled, or conditionally available without redeploying the application. Teams use it to release, test, target, disable, or roll back application behavior by changing configuration instead of shipping new code every time. It is not a substitute for authorization, a permanent architecture branch, a secret store, a deployment slot by itself, or a safe rollback if dependencies and data changes are irreversible. Configuration intermediate 6 commands Aliases: feature toggle, App Configuration feature flag, feature management flag, release flag Quick peek Open full term page

Web premium Function deployment slot Function deployment slot is a separate deployment environment inside a Function App that can host a release before it becomes the production slot. Teams use it to test code, app settings, warmup behavior, and integrations under the same app boundary before swapping traffic to the new version. In daily Azure work, it appears when engineers deploy a queue processor safely, warm an HTTP API, test slot settings, or roll back a bad serverless release without rebuilding the app. Azure Functions intermediate 6 commands Aliases: Azure Functions deployment slot, function app slot, staging slot for Functions 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

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

Integration premium Advanced event filter Advanced event filter is an Event Grid subscription filter that matches event fields and data values using advanced operators. In everyday Azure work, teams use it to route only the events that a handler actually needs, without creating separate topics for every condition. The useful evidence is event subscription, key path, operator type, values, event Event Grid intermediate 5 commands Aliases: Event Grid advanced filter, advanced filtering, event subscription advanced filter Quick peek Open full term page

Web premium App Service diagnostics Built-in App Service troubleshooting tools and detectors that help diagnose availability, performance, configuration, networking, and runtime problems. 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 diagnostics, diagnostics Quick peek Open full term page

Web premium Blob trigger Microsoft Learn describes the Blob Storage trigger for Azure Functions as a binding that starts a function when a new or updated blob is detected. The blob content is passed to code, letting serverless workloads react to files, documents, images, data feeds, or storage events. Azure Functions intermediate 5 commands Aliases: Blob trigger, trigger, blob trigger Quick peek Open full term page

AI and Machine Learning premium Document analysis operation A document analysis operation is an asynchronous Document Intelligence request that analyzes a document with a model and returns extracted content, layout, and fields when polling completes. Document Intelligence intermediate 5 commands Aliases: Analyze operation, analyze document operation, Document Intelligence analysis request, async analysis operation 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

AI and Machine Learning premium Document field A document field is a structured value extracted by Document Intelligence, usually with field type, content, confidence, and location metadata in the analyze result. Document Intelligence fundamentals 5 commands Aliases: extracted field, field value, query field, document result field Quick peek Open full term page

AI and Machine Learning premium Document Intelligence Azure AI Document Intelligence is a cloud service that uses OCR and machine learning to extract text, layout, tables, key-value pairs, and fields from documents. Document Intelligence fundamentals 5 commands Aliases: Azure AI Document Intelligence, Azure Document Intelligence, Form Recognizer, intelligent document processing Quick peek Open full term page

AI and Machine Learning premium Document Intelligence custom model A Document Intelligence custom model is a trained model built from representative labeled documents to extract fields from organization-specific document types. Document Intelligence intermediate 5 commands Aliases: custom extraction model, custom neural model, custom template model, trained custom document model Quick peek Open full term page

AI and Machine Learning premium Document Intelligence layout model The Document Intelligence layout model is a prebuilt model that extracts document text, tables, selection marks, structure, and layout information without custom training. Document Intelligence fundamentals 5 commands Aliases: layout model, prebuilt layout model, document layout analysis, layout analysis model Quick peek Open full term page

AI and Machine Learning premium Document Intelligence model A Document Intelligence model is a prebuilt, custom, composed, or classifier model used to analyze documents and return structured extraction or classification results. Document Intelligence fundamentals 5 commands Aliases: document model, prebuilt model, custom model, model ID 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 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 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

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 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 emulator The Event Hubs emulator is a local development tool that simulates Azure Event Hubs so developers can test producers and consumers without connecting to the cloud. Teams use it to prototype and test Event Hubs applications locally before connecting code to a real Azure namespace. It is not a production Event Hubs namespace, a substitute for scale testing, or a guarantee that cloud networking, identity, quota, or geo-recovery behavior works. 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 Event Hubs emulator, local Event Hubs emulator, Event Hubs local emulator 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

Web premium Function App The Azure Functions hosting resource that contains one or more functions and their runtime configuration. Serverless intermediate 5 commands Aliases: Azure Function App, Functions app, function app resource Quick peek Open full term page

Web premium Function key Microsoft Learn describes Azure Functions access keys as secret values used to make function endpoints harder to call without authorization. A function key is scoped to a specific function, while host, system, and master keys serve broader runtime or administrative access needs for a function app. Azure Functions security intermediate 5 commands Aliases: Azure Functions access key, Function access key, x-functions-key Quick peek Open full term page

Web premium host.json host.json is the Azure Functions metadata file that configures host-level runtime behavior for all functions in a function app. Azure Functions intermediate 5 commands Aliases: host json, host.json Quick peek Open full term page

Web premium In-process worker model In-process worker model is the Azure Functions .NET execution model where function code runs in the same process as the Functions host. Azure Functions intermediate 5 commands Aliases: In-process worker model, in process worker model, in-process worker model, in-process-worker-model Quick peek Open full term page

Compute premium Input binding Input binding controls how serverless code receives external data without hand-writing every service connection, query, or blob read inside the function body. Teams see it in function.json files, code attributes. It is not a trigger, output binding, SDK call, API route, or dependency injected service; confusing them can create missing input data, secret exposure in settings. 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. Azure Functions Fundamentals 5 commands Aliases: Azure Functions input binding, function input binding, binding input, declarative input binding Quick peek Open full term page

Web premium Isolated worker model Isolated worker model is the Azure Functions execution model where .NET function code runs in a separate worker process instead of inside the Functions host process. Azure Functions intermediate 5 commands Aliases: .NET isolated worker, Azure Functions isolated process, dotnet-isolated, out-of-process worker, isolated Functions worker Quick peek Open full term page

Containers premium KEDA KEDA is the Kubernetes Event-driven Autoscaling component that scales workloads based on external event sources and metrics, including scale-to-zero scenarios. Autoscaling intermediate 5 commands Aliases: Kubernetes Event-driven Autoscaling, event-driven autoscaler, KEDA scaler, scaled object Quick peek Open full term page

Web premium local.settings.json Microsoft Learn describes local.settings.json as the Azure Functions local settings file that stores app settings and tool settings for local development. Values in this file are used only locally and must be added separately to the function app in Azure. Azure Functions intermediate 5 commands Aliases: No aliases yet 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

Storage premium SFTP for Blob Storage SFTP for Blob Storage is the storage-account feature that exposes blob containers to SFTP clients after hierarchical namespace is enabled. Administrators configure local users, authentication methods, home directories, and permission scopes so external or internal clients can transfer files without custom SFTP infrastructure. Blob Storage advanced 5 commands Aliases: Blob Storage SFTP, SFTP for Blob Storage, SFTP landing zone, storage SFTP local user, SFTP-enabled storage account Quick peek Open full term page

Databases premium Cosmos DB change feed Cosmos DB change feed is a built-in way to read changes that happen in a container. Instead of constantly scanning for new or updated items, an application can process the feed and react when writes occur. Teams use it to update search indexes, build materialized views, move data, trigger workflows, or keep another store in sync. It is not the same as a general queue; it is tied to container writes, partitioning, leases, continuation state, and the mode used to read changes. Azure Cosmos DB intermediate 4 commands Aliases: Azure Cosmos DB change feed, change feed processor, Cosmos DB feed Quick peek Open full term page

Web premium Custom container web app an Azure App Service web app that runs a team-supplied container image instead of a built-in runtime stack. App Service intermediate 4 commands Aliases: App Service custom container, Web App for Containers, containerized App Service app Quick peek Open full term page

Storage premium Dequeue count Dequeue count is the Queue Storage message property that records how many times a message has been retrieved for processing, helping consumers identify retry loops, stuck work, and poison-message conditions. Queue Storage fundamentals 4 commands Aliases: queue message dequeue count, Azure Queue dequeue count, message dequeue count, queue trigger dequeue count 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