Search Azure terms

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

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

Compute premium Durable orchestration A durable orchestration coordinates a reliable long-running workflow by using an orchestrator function that schedules activities, checkpoints progress, and resumes after interruptions. Serverless workflows intermediate 4 commands Aliases: durable orchestrator, orchestration instance 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

Web premium Activity function Activity function is the worker function called by a Durable Functions orchestrator to perform one concrete unit of work. In everyday Azure work, teams use it to move side effects such as API calls, database writes, document generation, or messages out of deterministic orchestration code. The useful evidence is activity name, orchestration instance ID, retry Durable Functions intermediate 5 commands Aliases: Durable Functions activity, Durable activity function, orchestrator activity 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

Compute premium Entity function An entity function is a Durable Functions function that defines operations for reading and updating small pieces of durable state called durable entities. Azure Functions / Durable Functions intermediate 4 commands Aliases: entity function Quick peek Open full term page

Web premium Function Function is a small unit of Azure Functions code that runs when a trigger fires, such as an HTTP request, timer, queue message, event, or database change. Teams use it to execute focused serverless logic without managing a full web server, worker service, or long-running virtual machine for every task. In daily Azure work, it shows up when engineers process messages, expose lightweight APIs, react to events, run schedules, orchestrate workflows, or troubleshoot one failing handler inside a larger function app. Serverless beginner 4 commands Aliases: Azure function, serverless function, function trigger handler Quick peek Open full term page

Web verified Orchestrator function An orchestrator function is the Durable Functions workflow function that coordinates activity functions, sub-orchestrations, timers, external events, and durable state. It checkpoints progress through the Durable Task framework, must run deterministically, and should describe workflow logic instead of performing direct I/O or random work. Azure Functions intermediate 4 commands Aliases: Durable Functions orchestrator, orchestration function, workflow orchestrator, deterministic orchestrator Quick peek Open full term page

Integration top-250-pre130-priority-upgraded Logic App A Logic App is an Azure Logic Apps resource or workflow that automates business and integration processes by connecting a trigger, actions, connectors, data operations, conditions, and monitoring so systems can exchange information without custom glue code everywhere in governed production environments. Azure Logic Apps fundamentals 4 commands Aliases: Azure Logic Apps Quick peek Open full term page

Integration top-250-pre130-priority-upgraded Logic Apps Consumption Logic Apps Consumption is the Azure Logic Apps hosting option where each logic app resource contains one workflow that runs in the multitenant Azure Logic Apps service and is typically billed by trigger executions, actions, and connector usage in governed production environments. Azure Logic Apps intermediate 4 commands Aliases: Logic Apps Consumption Quick peek Open full term page

Containers premium field-manual Manual job A manual job is a Container Apps job that runs only when an operator, schedule, pipeline, or API call starts it. Teams use it when teams need containerized work that should not run continuously or scale from events automatically. In plain English, it gives operators a named control for controlled execution for maintenance, batch, migration, and operational tasks instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. Azure Container Apps intermediate 4 commands Aliases: Manual job, Azure Container Apps, Azure Container Apps jobs, scheduled job, event-driven job, container app, manual Container Apps job, on-demand job 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

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

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

Analytics learning-path-anchor Synapse SQL on-demand Synapse SQL on-demand is the serverless SQL pool model in Azure Synapse Analytics. It lets teams run T-SQL queries over data in the lake without provisioning dedicated warehouse capacity, storing only metadata objects while using external data sources, views, functions, and security objects. Synapse Analytics fundamentals 6 commands Aliases: SQL on-demand, Synapse serverless SQL, serverless SQL in Synapse, built-in serverless SQL pool Quick peek Open full term page

Storage premium Local filesystem Microsoft Learn describes App Service file access as a managed sandbox with persistent and temporary filesystem locations for deployed content, logs, and runtime operations. Apps can read and write allowed paths, but storage behavior differs by platform, plan, and deployment method. Storage advanced 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance learning-path-anchor Template expression A template expression computes values during ARM template deployment. ARM deployments fundamentals 5 commands Aliases: Template expression, template expression, Azure Template expression, ARM Template expression, ARM expressions, deployment expressions Quick peek Open full term page

Management and Governance learning-path-anchor Template function A template function is a built-in helper used by ARM templates or Bicep to calculate values. ARM deployments fundamentals 5 commands Aliases: Template function, template function, Azure Template function, ARM Template function, ARM functions, deployment functions Quick peek Open full term page

Analytics learning-path-anchor Databricks metastore The top-level Unity Catalog container for catalogs, schemas, tables, volumes, models, functions, and governance permissions. Databricks intermediate 4 commands Aliases: Unity Catalog metastore, Databricks Unity Catalog metastore, metastore Quick peek Open full term page

Analytics learning-path-anchor Databricks schema A Unity Catalog namespace under a catalog that groups tables, views, volumes, models, functions, and permissions. Databricks fundamentals 4 commands Aliases: Unity Catalog schema, Databricks database schema, schema in Unity Catalog Quick peek Open full term page

Storage verified Queue Storage Azure Queue Storage is a storage service for keeping large numbers of small messages until an application or worker retrieves and processes them. It supports asynchronous web-queue-worker designs, authenticated HTTP or HTTPS access, and integration with Azure Functions, SDKs, and automation tools. Queue Storage beginner 5 commands Aliases: Queue Storage 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

AI and Machine Learning premium Scoring profile A scoring profile is an Azure AI Search index setting that boosts ranking for matches that meet business rules. It can weight text fields or apply functions for freshness, distance, magnitude, or tags, and a query chooses one profile to influence returned order. Azure AI Search fundamentals 8 commands Aliases: Azure AI Search scoring profile, search relevance profile, relevance scoring profile, scoringProfiles, boosting profile 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

Analytics premium Databricks catalog The top-level Unity Catalog namespace that organizes schemas, tables, views, volumes, models, functions, permissions, lineage, and governed data ownership. Azure Databricks fundamentals 6 commands Aliases: Unity Catalog catalog, Azure Databricks catalog, catalog object 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

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

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 App Service Environment Microsoft Learn describes App Service Environment as a single-tenant App Service deployment that runs in a customer virtual network. It hosts App Service plans and apps with stronger network isolation, dedicated compute boundaries, and high-scale hosting compared with the public multitenant App Service model. App Service isolation intermediate 5 commands Aliases: ASE, Azure App Service Environment, app service environment Quick peek Open full term page

Analytics premium Azure Databricks Unity Catalog A unified governance layer in Azure Databricks for data and AI assets, including catalogs, schemas, tables, volumes, models, privileges, and lineage. Data governance intermediate 5 commands Aliases: Unity Catalog 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

AI and Machine Learning premium Azure OpenAI managed identity Azure OpenAI managed identity uses Microsoft Entra identities so Azure workloads can call model endpoints without stored keys. Azure OpenAI intermediate 5 commands Aliases: No aliases yet 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