Search Azure terms

Monitoring premium Application Insights Application Insights is the application performance monitoring capability in Azure Monitor. It collects OpenTelemetry or SDK telemetry such as requests, dependencies, exceptions, traces, metrics, and availability results so teams can continuously understand live application health, performance, failures, and user-impacting behavior. Application observability fundamentals 4 commands Aliases: Azure Application Insights, App Insights, Azure Monitor Application Insights, application performance monitoring, APM Quick peek Open full term page

Monitoring and Observability premium Application Insights connection string An Application Insights connection string specifies the Application Insights resource and endpoints that an instrumented application uses to send telemetry. Application Insights fundamentals 3 commands Aliases: APPLICATIONINSIGHTS_CONNECTION_STRING, application insights connection string Quick peek Open full term page

Monitoring and Observability premium Application map Application Map is an Application Insights view that visualizes application components and dependencies using telemetry, helping teams identify bottlenecks and failure hotspots. Application Insights fundamentals 2 commands Aliases: application map Quick peek Open full term page

Web verified Requests in application queue Requests In Application Queue is an Azure Monitor metric for Microsoft.Web/sites that reports how many Web App or Function App requests are waiting in the application request queue. It helps diagnose saturation, slow handlers, cold starts, thread exhaustion, or delayed scale-out. Web App metric intermediate 6 commands Aliases: RequestsInApplicationQueue, App Service application queue, HTTP requests in application queue, Web App request queue metric, Function App request queue metric 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

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

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 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 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 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 Chat completion A AI platform capability in Azure OpenAI that helps teams build, secure, observe, and govern intelligent applications with clearer ownership, safety, and operational context. Azure OpenAI fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

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

Integration premium Event Hubs consumer offset An Event Hubs consumer offset is the position a consuming application uses to continue reading events within a specific partition, usually captured through checkpoint state. Teams use it to understand where a reader stopped, resumed, replayed, or skipped within a retained Event Hubs partition. It is not a global cursor for the whole event hub, a Service Bus dequeue count, or proof that downstream business processing succeeded. 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: consumer offset, Event Hubs reader offset, stream consumer position 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 Hubs offset An Event Hubs offset is metadata that identifies an event position within a partition of an event hub. Teams use it to describe the exact location of an event in a partition so readers can reason about ordering, replay, and processing position. It is not a timestamp alone, a sequence number alone, a global event hub position, or confirmation that a consumer completed downstream work. 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: event offset, partition offset, stream offset 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

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 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

AI and Machine Learning premium Immersive Reader Immersive Reader is an Azure AI service that adds reading-comprehension features such as focused text display, read-aloud, translation, and grammar aids to applications. Azure AI services fundamentals 5 commands Aliases: Immersive Reader, immersive reader, immersive-reader 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

Monitoring and Observability premium Instrumentation key Instrumentation key controls which Application Insights component receives telemetry and how older application configurations identify the target monitoring resource. Teams see it in application insights resource properties, app settings. It is not a secret access key, API key, SAS token, Log Analytics workspace ID, or managed identity credential; confusing them can create missing telemetry, cross-environment data pollution. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Application Insights Fundamentals 5 commands Aliases: ikey, Application Insights instrumentation key, AI instrumentation key, telemetry instrumentation key Quick peek Open full term page

Monitoring and Observability premium Interaction to Next Paint Interaction to Next Paint controls how teams measure whether web pages feel responsive after real user interactions, especially for Azure-hosted web apps and customer portals. Teams see it in microsoft edge devtools, microsoft clarity dashboards. It is not server response time, Time to First Byte, First Input Delay, Cumulative Layout Shift, or a backend CPU metric; confusing them can create slow clicks, abandoned checkout flows. 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. Web Vitals Intermediate 5 commands Aliases: INP, Core Web Vitals INP, web responsiveness metric, interaction responsiveness Quick peek Open full term page

Monitoring and Observability premium Availability result Availability result is the recorded outcome of an Application Insights availability test run, including whether the probe succeeded, how long it took, and where it ran. In Azure, teams encounter it when teams query Azure Monitor Logs after a synthetic web test reports failures, slow responses, or regional differences. The useful question is what behavior Availability intermediate 4 commands Aliases: AppAvailabilityResults, availability test result, Application Insights availability result Quick peek Open full term page

Monitoring and Observability premium Availability test Availability test is an outside-in monitor that repeatedly calls a public HTTP or HTTPS endpoint and records whether it responded quickly enough. In Azure, teams encounter it when product teams need synthetic checks for websites, APIs, or critical external dependencies before users report an outage. The useful question is what behavior it proves, who owns Availability intermediate 4 commands Aliases: Application Insights availability test, web test, standard test, synthetic test Quick peek Open full term page

AI and Machine Learning premium Azure AI metrics Azure AI metrics is the measurable signals used to observe Azure AI applications, model endpoints, agents, evaluations, safety checks, and business outcomes. Azure AI services intermediate 4 commands Aliases: AI metrics, AI service metrics, Azure AI Metrics Advisor, Azure Monitor metrics for AI, Metrics Advisor, time series anomaly detection Quick peek Open full term page

Monitoring and Observability premium Azure dashboard A customizable Azure portal view for organizing resource tiles, metrics, charts, links, and operational context into private or shared dashboards. Visualization fundamentals 4 commands Aliases: Azure portal dashboard, Portal dashboard Quick peek Open full term page

Web premium Deployment Center Deployment Center is the Azure portal experience for configuring and reviewing App Service deployment sources, such as GitHub, Azure Repos, Bitbucket, local Git, and supported build providers. Deployment fundamentals 4 commands Aliases: App Service Deployment Center, Azure Deployment Center, deployment center in App Service, continuous deployment center Quick peek Open full term page

AI and Machine Learning premium Deployment type Deployment type is the Azure AI or Microsoft Foundry model hosting option, such as standard, global, data-zone, regional, batch, serverless, or provisioned deployment, that determines availability, data processing location, capacity model, cost, and operational behavior. Microsoft Foundry intermediate 4 commands Aliases: Microsoft Foundry deployment type, Azure AI deployment type, model deployment type, Foundry Models deployment type 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

Integration premium Developer portal The developer portal is the Azure API Management portal where API consumers discover APIs, read documentation, sign in, subscribe to products, retrieve subscription details, and test API operations when allowed. Application delivery and API edge intermediate 4 commands Aliases: API Management developer portal, APIM developer portal, developer portal in API Management, API consumer portal 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

Monitoring and Observability premium Diagnostic setting A diagnostic setting is an Azure Monitor configuration that routes platform logs and metrics from a resource to supported destinations such as Log Analytics, Event Hubs, or Storage. Diagnostics fundamentals 4 commands Aliases: Azure Monitor diagnostic setting, resource diagnostic setting, platform log routing, diagnostic settings 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

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 Easy Auth Easy Auth is the built-in authentication and authorization capability in Azure App Service and Azure Functions for signing in users with identity providers such as Microsoft Entra. App Service security fundamentals 4 commands Aliases: App Service Authentication, App Service built-in authentication Quick peek Open full term page

AI and Machine Learning premium Endpoint traffic split Azure Machine Learning online endpoints can allocate percentages of live traffic across deployments and can mirror traffic to validate a new deployment before full rollout. Azure Machine Learning intermediate 4 commands Aliases: online endpoint traffic split, traffic allocation, blue green endpoint split 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

Storage premium Entity group transaction An entity group transaction is an atomic batch of Table service operations on entities in the same table and with the same PartitionKey value. Table Storage intermediate 4 commands Aliases: entity group transaction Quick peek Open full term page

Monitoring and Observability premium Error budget An error budget is the amount of unreliability a service can consume while still meeting its service level objective over a defined measurement window. SRE and reliability intermediate 4 commands Aliases: error budget Quick peek Open full term page

Monitoring and Observability premium Error rate Error rate is the proportion of requests, operations, or events that fail compared with the total volume over a defined time window. Metrics and SRE fundamentals 4 commands Aliases: error rate Quick peek Open full term page

Storage premium ETag An ETag is an opaque identifier that represents the current version of a resource and is commonly used for optimistic concurrency checks. Concurrency and resource state intermediate 4 commands Aliases: etag Quick peek Open full term page

AI and Machine Learning premium Function calling Function calling is an AI application pattern where a model chooses a developer-defined tool and returns structured arguments so the application can call real business logic. Teams use it to let assistants retrieve data, create tickets, schedule work, search systems, or call APIs while the application remains responsible for execution and validation. In daily Azure work, it shows up when engineers build agents, connect chat to backend tools, audit model-selected actions, validate JSON arguments, or debug why a model called the wrong function. Azure OpenAI advanced 4 commands Aliases: tool calling, OpenAI function calling, model tool call Quick peek Open full term page

Web premium Function cold start Function cold start is the delay before a function begins processing when the host, worker, language runtime, dependencies, or deployment package must initialize first. Teams use it to explain latency spikes after inactivity, new deployments, scale-out events, app restarts, dependency loading, or worker specialization in serverless workloads. In daily Azure work, it shows up when engineers investigate slow first requests, choose a hosting plan, enable always-ready capacity, prewarm slots, tune package size, or distinguish app code latency from platform startup. Azure Functions intermediate 4 commands Aliases: Azure Functions cold start, cold start, serverless cold start Quick peek Open full term page

Web premium Function runtime version Function runtime version is the version of the Azure Functions host that executes function code and loads trigger bindings for a Function App. Teams use it to keep code, language support, extension bundles, and hosting behavior aligned as Azure Functions evolves and older runtimes retire. In daily Azure work, it appears when engineers upgrade Node, Python, Java, or .NET functions, investigate startup failures, review support deadlines, or compare app settings across slots. It is not the application code version, package version, language worker alone, or proof that every extension and dependency is compatible. Azure Functions runtime intermediate 4 commands Aliases: Azure Functions runtime version, FUNCTIONS_EXTENSION_VERSION, Functions host version 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

AI and Machine Learning premium Grounded generation Grounded generation is a generative AI pattern where model responses are based on supplied source material, retrieved enterprise content, tool results, or other approved grounding data. Generative AI intermediate 4 commands Aliases: grounded AI generation, grounded response generation, RAG answer generation Quick peek Open full term page

AI and Machine Learning premium Groundedness detection Groundedness detection checks whether a generated text response is supported by provided source material and flags responses that appear ungrounded or inconsistent with that material. Azure AI Content Safety advanced 4 commands Aliases: groundedness filter, ungroundedness detection, AI groundedness check Quick peek Open full term page