Glossary
Search Azure terms
Open a clear definition, then continue into exam context, architecture, commands, operational examples, common mistakes, and related concepts.
Search all
Commands
Learning guides
Concept graph
Compare
Search-first Azure knowledge base
Term results
Search for a term or click a category. Results render only after you ask for them, so the glossary does not dump every available term on first load. Each result includes Quick peek and Open full term page actions.
Start with a search or a category.
Try managed identity , resource group , az group , private endpoint , or click Databases to load all database-related terms.
Showing 100 of 110 web terms. Narrow the search to reduce the list.
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
Always On
Always On is an Azure App Service platform setting that keeps an app loaded and prevents it from being unloaded after idle periods, helping reduce cold starts and background-job interruptions.
App Service
intermediate
3 commands
Aliases: App Service Always On, always-on setting, keep warm setting
Quick peek
Open full term page
Web
premium
Always ready instance
An always ready instance is prewarmed Azure Functions capacity kept available for selected function apps or groups so new executions can start faster and avoid cold-start delays.
Azure Functions
intermediate
3 commands
Aliases: prewarmed function instance, Azure Functions always ready, premium always ready instance
Quick peek
Open full term page
Web
premium
App Service
Azure App Service is a managed HTTP-based platform for hosting web apps, REST APIs, and mobile back ends without managing the underlying servers. It helps learners understand where the concept appears in Azure operations and what to verify before changing it.
App Service
intermediate
4 commands
Aliases: App Service, app service
Quick peek
Open full term page
Web
premium
App Service auth token store
An App Service Authentication feature that stores provider tokens for signed-in users so application code can access them through the built-in authentication flow. 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 auth token store, auth token store
Quick peek
Open full term page
Web
premium
App Service authentication provider
An identity provider configured in App Service Authentication, such as Microsoft Entra ID, that handles user sign-in for the app. 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 authentication provider, authentication provider
Quick peek
Open full term page
Web
premium
App Service backup
An App Service feature for creating on-demand or scheduled backups of app content and supported configuration, with restore to an app or slot. 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 backup, backup
Quick peek
Open full term page
Web
premium
App Service connection string
A named connection string stored in App Service configuration and exposed to application code for supported database or service connectivity. 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 connection string, connection string
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
Web
premium
App Service Environment v3
App Service Environment v3 is the current App Service Environment generation for single-tenant, dedicated App Service hosting with simplified networking and high-scale isolated workloads.
App Service isolation
intermediate
5 commands
Aliases: Azure App Service Environment v3, app service environment v3
Quick peek
Open full term page
Web
premium
App Service Hybrid Connections
App Service Hybrid Connections let an App Service app make outbound TCP connections to a specific host and port in another network through Azure Relay.
App Service networking
intermediate
5 commands
Aliases: Azure App Service Hybrid Connections, app service hybrid connections
Quick peek
Open full term page
Web
premium
App Service Linux worker
An App Service Linux worker is the Linux-based App Service compute instance that runs an app using a built-in Linux runtime stack or custom container.
App Service runtime
intermediate
5 commands
Aliases: Azure App Service Linux worker, app service linux worker
Quick peek
Open full term page
Web
premium
App Service logs
Microsoft Learn explains App Service diagnostic logging as settings that collect application logs, web server logs, detailed errors, failed request traces, container logs, and platform resource logs for App Service apps. These logs can be streamed, stored temporarily, written to storage, or routed through Azure Monitor.
App Service diagnostics
intermediate
5 commands
Aliases: Azure App Service logs, app service logs
Quick peek
Open full term page
Web
premium
App Service Plan
Microsoft Learn describes an App Service plan as the set of compute resources where App Service apps run. The plan defines region, operating system, pricing tier, instance size, scale capacity, and feature availability for one or more hosted apps within the same compute boundary.
App Service hosting plans
intermediate
5 commands
Aliases: Azure App Service plan, serverfarm, App Service hosting plan
Quick peek
Open full term page
Web
premium
App Service plan scale out
App Service plan scale out increases the number of worker instances running apps in an App Service plan, either manually or through scaling rules where supported.
App Service scaling
intermediate
4 commands
Aliases: Azure App Service plan scale out, app service plan scale out
Quick peek
Open full term page
Web
premium
App Service plan scale up
App Service plan scale up is changing an App Service plan to a larger, smaller, or more capable pricing tier so the hosted apps receive different CPU, memory, feature support, and platform limits. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes.
App Service
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
App Service private endpoint
An App Service private endpoint uses Azure Private Link to give an app a private IP address in a virtual network for inbound client access.
App Service Networking
intermediate
6 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
App Service restore
App Service restore is recovering App Service content and supported configuration from an app backup, usually by overwriting an app or restoring into another app or deployment slot. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes.
App Service Recovery
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
App Service scale rule
App Service scale rule is an autoscale rule or automatic scaling configuration that changes App Service capacity when metric thresholds, schedules, or platform load signals require more or fewer instances. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes.
App Service Scaling
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
App Service SKU
App Service SKU is the pricing tier and size selected for an App Service plan, which determines available compute resources, feature support, scale limits, and billing behavior. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes.
App Service Plans
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
App Service VNet integration
Microsoft Learn describes App Service virtual network integration as the feature that lets an App Service app access resources in or through an Azure virtual network. It affects outbound traffic from the app; inbound private access uses other controls, such as private endpoints and access restrictions.
App Service Networking
intermediate
5 commands
Aliases: App Service virtual network integration, regional VNet integration, Web App VNet integration
Quick peek
Open full term page
Web
premium
App Service Windows worker
App Service Windows worker is a Windows-based worker instance in an App Service plan that runs Windows App Service apps and shares compute with other apps placed in the same plan. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes.
App Service Platform
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
App Service worker count
App Service worker count is the number of worker instances allocated to an App Service plan, which determines how many copies of hosted apps run across the plan capacity. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes.
App Service Scaling
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
ARR affinity
ARR affinity is the sticky-session behavior in Azure App Service that tries to send a user back to the same worker instance after the first request. It can help older stateful web apps that keep session data on the local worker. It can also hurt scaling because traffic may not spread evenly across all.
App Service
intermediate
2 commands
Aliases: ARRAffinity, App Service session affinity, Application Request Routing affinity, sticky sessions
Quick peek
Open full term page
Web
premium
Auto swap
Auto swap is a convenience feature for Azure App Service deployment slots. Instead of a person manually swapping staging into production, App Service can automatically swap a configured source slot into a target slot after a code push. In plain terms, the app moves from “deployed to staging” to “live in the target slot” without another.
App Service
intermediate
4 commands
Aliases: App Service auto swap, deployment slot auto swap, slot auto swap, automatic slot swap
Quick peek
Open full term page
Web
premium
Bandwidth in/out
Bandwidth in/out refers to measured inbound and outbound network traffic or throughput for Azure resources, often reviewed through metrics, diagnostics, and billing data.
App Service metric
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
Binding
An Azure Functions binding declaratively connects a function to another resource as a trigger, input, or output path.
Serverless
fundamentals
2 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
Binding expression
An Azure Functions expression that resolves values from trigger or binding metadata.
Azure Functions
intermediate
3 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
Web
premium
Cold start
A slower first request after an app starts, restarts, scales, or wakes from idle.
App Service
intermediate
3 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
Connections
an App Service monitoring signal that helps operators understand how many active client or platform connections are present for a web application
Web App metric
intermediate
2 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
Consumption plan
the serverless Azure Functions hosting option that scales instances automatically and charges based on executions and resources used while functions run
Azure Functions
intermediate
3 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
CPU percentage
CPU percentage is an Azure glossary term for a platform metric that shows how much processor capacity an app, plan, virtual machine, or scale set is using over time. In practice, it helps teams reason about detecting compute pressure, validating scale rules, investigating latency, and deciding whether code, plan size, or instance count must change using live Azure evidence, documented ownership, and Microsoft Learn guidance. It should be reviewed through security, reliability, operations, cost, and performance lenses before production changes.
Azure Monitor metrics
beginner
3 commands
Aliases: Cpu percentage, CpuPercentage, Percentage CPU, CPU utilization
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
Web
premium
Custom domain
an organization-controlled DNS name bound to an Azure-hosted endpoint instead of the default service hostname.
Domains and TLS
fundamentals
4 commands
Aliases: custom hostname, custom DNS name, application custom domain
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
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
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
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
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
FTP deployment
FTP deployment is an Azure App Service deployment method where application files are uploaded to a web app through FTP or FTPS publishing endpoints. Teams use it to support simple or legacy file-based releases when a full CI/CD pipeline, container image, or ZIP deployment flow is not available. In daily Azure work, it shows up when engineers publish static content, migrate an older web app, recover a small site, rotate deployment credentials, or disable basic publishing after modernization. It is not source control, a build pipeline, a secure secret-management strategy, or the preferred deployment method for regulated production systems.
App Service deployment
intermediate
4 commands
Aliases: FTPS deployment, App Service FTP deployment, FTP/S deployment
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
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 app managed identity
Function app managed identity is a Microsoft Entra identity assigned to a function app so its code and supported bindings can access Azure resources without storing passwords or connection strings. Teams use it to replace secrets in app settings with identity-based access to services such as Storage, Service Bus, Key Vault, Event Hubs, SQL, or monitoring resources. In daily Azure work, it shows up when engineers grant a function app data-plane permissions, remove leaked connection strings, configure identity-based bindings, or investigate why a trigger cannot reach its dependency.
Azure Functions
intermediate
4 commands
Aliases: Azure Functions managed identity, managed identity for Functions, function app identity
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 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
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
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 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
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
premium
Health Check
Health Check is an App Service setting that pings a configured path so Azure can detect unhealthy application instances and route traffic away from them.
App Service
beginner
4 commands
Aliases: App Service health check, health endpoint check, Health Check, health-check
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
Web
premium
Isolated App Service tier
Isolated App Service tier is the App Service pricing tier used for apps running in an App Service Environment with dedicated, isolated workers and advanced networking options.
App Service Environment
advanced
5 commands
Aliases: App Service Isolated tier, IsolatedV2 tier, Iv2 App Service plan, ASE App Service plan, I1v2, I2v2, I3v2
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
Web
premium
Kudu
Kudu is the App Service deployment and diagnostics engine exposed through the SCM site, providing tools for deployment, logs, process inspection, console access, and troubleshooting.
App Service deployment and diagnostics
Intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
premium
Kudu console
Kudu console is the App Service Advanced Tools command console used to inspect runtime files, environment state, processes, logs, and deployment artifacts for a web app or function app.
App Service diagnostics
Intermediate
5 commands
Aliases: Kudu debug console, App Service advanced tools console, SCM console, Kudu Advanced Tools
Quick peek
Open full term page
Web
premium
Local Git deployment
Microsoft Learn describes Local Git deployment for App Service as a method for deploying code from a Git repository on a local computer to an app-hosted Git endpoint. It requires deployment credentials and Source Control Manager basic authentication. Operators should review it with the connected Azure resource settings.
App Service
intermediate
5 commands
Aliases: No aliases yet
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
Managed certificate
A managed certificate in Azure App Service is a platform-created TLS certificate for a supported custom domain. Azure can issue and renew it for basic HTTPS protection, but it has limitations compared with uploaded, Key Vault, or purchased certificates. That context supports safer operational decisions.
TLS
fundamentals
4 commands
Aliases: App Service managed certificate, free managed certificate
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
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
Web
premium
Shared App Service tier
The Shared App Service tier is a base App Service plan option where apps run on shared Azure virtual machines and receive CPU-minute quotas. It is intended for development and testing, not production workloads that need dedicated compute, autoscale, or predictable performance isolation.
App Service plans
intermediate
5 commands
Aliases: App Service Shared tier, Shared App Service plan, D1 App Service plan, shared compute App Service, App Service D1
Quick peek
Open full term page
Web
premium
Web App
A Web App is an Azure App Service application for hosting web applications, REST APIs, or mobile back ends without managing servers. It runs on an App Service plan, supports common language stacks or containers, and integrates with deployment, scaling, networking, identity, and monitoring features.
App Service
intermediate
6 commands
Aliases: Azure Web App, App Service Web App, Microsoft.Web/sites, App Service app
Quick peek
Open full term page
Web
premium
Zip deploy
Zip deploy is an App Service deployment method that pushes a ZIP package to a web app and has Kudu extract or run the package. Microsoft Learn documents ZIP, WAR, JAR, EAR, and individual-file deployment, including the requirement that the deployment archive contain project files at its root.
App Service
intermediate
5 commands
Aliases: ZIP deployment, Kudu ZIP deployment, package deployment, zip push deployment
Quick peek
Open full term page
Web
field-manual-complete
App Service access restriction
App Service access restriction is the rule list that decides which inbound clients are allowed to reach a web app before the request reaches your code.
App Service networking
intermediate
5 commands
Aliases: access restriction, app service access restriction
Quick peek
Open full term page
Web
field-manual-complete
App Service app setting
An App Service app setting is a key-value configuration entry attached to a web app.
App Service configuration
intermediate
5 commands
Aliases: app service app setting, app setting
Quick peek
Open full term page
Web
field-manual-complete
App Service custom domain
An App Service custom domain lets people use your real website name instead of the default azurewebsites.net address. You prove that you own the DNS name, point DNS records at the web app, and add the hostname to App Service. The setting is simple on the surface, but production success depends on DNS propagation, ownership verification, TLS certificates, redirects, and whether traffic also passes through Front Door, Traffic Manager, or another edge service. Plan it like a release.
App Service
intermediate
5 commands
Aliases: app service custom domain, custom domain
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
Web
field-manual-complete
App Service TLS binding
An App Service TLS binding tells App Service which certificate to use for a custom domain. Without it, your app might be reachable by name but still show browser warnings, serve the wrong certificate, or fail HTTPS checks. The binding connects a hostname, a certificate thumbprint, and a binding type such as SNI. For users, it is the difference between a trusted secure site and a launch that looks broken or unsafe. Treat it as launch-blocking configuration.
App Service Security
intermediate
5 commands
Aliases: TLS binding, SSL binding, App Service certificate binding, custom domain HTTPS binding
Quick peek
Open full term page
Web
field-manual-complete
Deployment slot
Microsoft Learn describes App Service deployment slots as live apps with their own host names. You can deploy a web app, API app, mobile backend, or Linux web app to a nonproduction slot, validate it, then swap content and configuration with production.
App Service
intermediate
5 commands
Aliases: App Service deployment slot, Azure App Service slot, Deployment slot, always-on, app-service, app-service-app-setting, app-service-logs, app-service-plan, container-apps-revision, deployment slot, deployment-slot, deployment-slot-swap, github-actions-deployment, production-slot, slot-setting, staging slot, staging-slot, web app slot
Quick peek
Open full term page
Web
field-manual-complete
Deployment slot swap
A deployment slot swap is the App Service release move that trades the roles of two slots, usually staging and production. Instead of deploying directly over the live app, teams deploy to a staging slot, test it, warm it up, and then swap it into production. The old production version remains in the other slot.
App Service
intermediate
5 commands
Aliases: App Service slot swap, swap deployment slots, staging to production swap, Azure slot promotion
Quick peek
Open full term page
Web
field-manual-complete
HTTP trigger
An HTTP trigger is the front door for a function that should run because something made a web request. Instead of waiting for a queue message, timer, or file upload, the function wakes up when a client calls an HTTP route. Teams.
Azure Functions
intermediate
5 commands
Aliases: HTTP trigger, http trigger
Quick peek
Open full term page
Web
verified
OneDeploy
OneDeploy is the Azure App Service publish extension invoked through the Microsoft.Web sites extensions/onedeploy operation and surfaced by deployment tooling such as az webapp deploy. It sends a ZIP, WAR, JAR, EAR, startup script, or file package to an app or slot for publishing.
App Service
intermediate
6 commands
Aliases: App Service OneDeploy, az webapp deploy, Kudu publish API, App Service package deployment, OneDeploy
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
Web
verified
Output binding
An output binding is an Azure Functions binding that writes data from function code to another service, such as Queue Storage, Blob Storage, Service Bus, Event Hubs, Cosmos DB, or HTTP. It lets the runtime handle connection details from binding metadata and app configuration.
Azure Functions
intermediate
4 commands
Aliases: Azure Functions output binding, function output binding, binding output, serverless output integration
Quick peek
Open full term page
Web
field-manual-complete
Premium v3 App Service tier
Premium v3 is a higher App Service plan tier for apps that need more dedicated compute, memory, or scale than lower tiers provide.
App Service plans
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
field-manual-complete
Premium v4 App Service tier
Premium v4 is the App Service tier you choose when a production web app, API, or container needs stronger dedicated workers than older premium tiers provide. It is still App Service, so Azure manages the platform, patching, load balancing, deployment slots, and scale controls. The difference is the worker profile: faster processors, NVMe-backed local storage, and memory-optimized options. Use it when measured CPU, memory, startup, or local I/O pressure justifies a larger plan, not as a blind fix for every slow request.
App Service plans
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
field-manual-complete
Preview environment
A preview environment is a temporary copy of a Static Web Apps site used to review changes before they become production. When a pull request is opened, Azure can build the branch and publish it to a unique URL. Reviewers, testers, designers, and product owners can click through the changed site, run checks, and compare behavior against production. It is not a secret sandbox by default. Anyone who has the preview URL may be able to open it, so sensitive content and test credentials need careful handling.
Static Web Apps
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
field-manual-complete
Private bytes
Private bytes tells you how much memory an app process has allocated for itself and cannot share with other processes. In App Service, it is a useful signal when a web app, Function, WebJob, or container slowly grows until it restarts, slows down, or exhausts the worker. It is not the same as every memory metric, and it does not explain the root cause by itself. Treat it as a warning light: the app may be leaking memory, caching too aggressively, processing oversized payloads, or running on an undersized plan.
Runtime metric
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
field-manual-complete
Private certificate
A private certificate is a certificate your App Service app can use because the private key is available to the platform. Teams bring private certificates when they need to secure a custom domain with their own PFX certificate, use a wildcard certificate, import a certificate from Key Vault, or make the app present a certificate to another system. It is different from a public key certificate and from some managed certificate scenarios. Handle it like a secret: protect the private key, track expiry, and bind the right thumbprint to the right hostname.
App Service
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
verified
Production slot
The production slot is the live home of an App Service app.
App Service
intermediate
6 commands
Aliases: No aliases yet
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
Web
field-manual-complete
Swap with preview
Swap with preview is a safer way to promote an App Service deployment slot. Instead of immediately swapping staging into production, Azure first applies the target slot's relevant configuration to the source slot and lets you verify the app. You can test startup, settings, authentication behavior, warm-up paths, and dependency access before completing the swap. If something looks wrong, you reset the preview and leave production traffic where it was. It is a controlled pause between deployment and commitment.
App Service
intermediate
5 commands
Aliases: App Service swap with preview, deployment slot swap preview, slot swap preview, preview swap
Quick peek
Open full term page
Web
field-manual-complete
Timer trigger
A timer trigger is an Azure Functions trigger that starts a function on a defined schedule, using a CRON expression or TimeSpan where supported. It lets teams run serverless code for recurring jobs without a separate scheduler, VM, or always-on worker.
Azure Functions
intermediate
5 commands
Aliases: scheduled function, Azure Functions timer, timer binding, scheduled trigger, CRON trigger
Quick peek
Open full term page
Web
field-manual-complete
Trigger
In Azure Functions, a trigger causes a function to run and defines how the function is invoked. Every function has exactly one trigger, such as HTTP, timer, queue, Event Grid, or Event Hubs, and the trigger can pass input data into the function.
Serverless
fundamentals
5 commands
Aliases: Azure Functions trigger, function trigger, HTTP trigger, timer trigger, queue trigger, event trigger
Quick peek
Open full term page
Web
verified
Web app runtime stack
A web app runtime stack is the language and framework environment Azure App Service uses to run an application, such as .NET, Java, Node.js, Python, PHP, or a custom container. It affects supported versions, platform patching, startup behavior, and deployment compatibility.
App Service
intermediate
5 commands
Aliases: App Service runtime stack, web app stack, linuxFxVersion, language runtime stack
Quick peek
Open full term page
Web
verified
WebJobs / background work
Azure WebJobs is a built-in App Service feature for running background tasks, scripts, and programs alongside a web, API, or mobile app. Jobs share the App Service plan and can run continuously, on demand, or by schedule, often using the WebJobs SDK for event-driven processing.
App Service
intermediate
6 commands
Aliases: Azure WebJobs, App Service WebJobs, background jobs, continuous WebJob, triggered WebJob
Quick peek
Open full term page
Web
verified
Working set
Working set is an Azure Monitor memory metric for Web Apps and Function Apps that reports the current memory used by the app, while average memory working set reports average usage. It helps operators spot memory pressure, leaks, and plan-sizing problems.
Runtime metric
intermediate
6 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
strict-validated
App Service health check path
An App Service health check path is the URL path App Service probes to determine whether each app instance is healthy enough to receive traffic.
App Service operations
intermediate
5 commands
Aliases: Azure App Service health check path, app service health check path
Quick peek
Open full term page
Web
strict-validated
Basic App Service tier
The Basic App Service tier is a dedicated-compute App Service plan tier intended for lower-scale production, development, or test web apps that need dedicated workers.
App Service plan tiers
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Web
strict-validated
Free App Service tier
The Free App Service tier is an App Service plan SKU for experimentation on shared infrastructure with limited features and no dedicated compute charge.
App Service plan tiers
fundamentals
5 commands
Aliases: App Service Free tier, F1 App Service tier, Free F1 plan
Quick peek
Open full term page
Web
premium field-manual
Master key
A master key is a database-level symmetric key used to protect certificates, private keys, and credentials inside SQL databases. Teams use it when SQL objects need encrypted secrets or credentials for secure database operations. In plain English, it gives operators a named control for structured key protection, credential security, and auditable database encryption dependencies 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 Functions access keys
intermediate
4 commands
Aliases: Master key, _master key, Azure Functions master key, Functions admin key, Functions master key, admin host key, Azure Functions, Azure Functions access keys
Quick peek
Open full term page
Web
premium field-manual
Memory percentage
The memory percentage metric is a memory utilization value that shows how much of a container or workload memory allocation is being used. Teams use it when operators need to detect memory pressure, tune limits, or drive memory-based scaling decisions. In plain English, it gives operators a named control for earlier visibility into memory-bound behavior, restarts, and capacity risk 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.
App Service and Azure Monitor metrics
intermediate
4 commands
Aliases: Memory percentage, MemoryPercentage, memory utilization percentage, memory metric, memory usage percentage, container memory percentage, App Service memory percent, Azure Monitor and Azure App Service, App Service and Azure Monitor metrics
Quick peek
Open full term page
Web
field-manual-ready
Multi-container web app
A multi-container web app is an App Service workload made from multiple cooperating containers rather than one application image.
Azure App Service
intermediate
4 commands
Aliases: Docker Compose web app, App Service multi-container, multi-container web app, App Service sidecar, Docker Compose App Service
Quick peek
Open full term page
Web
template-specs-upgraded
Run from package
Microsoft Learn explains that the WEBSITE_RUN_FROM_PACKAGE app setting makes App Service run application content from a ZIP package. The package is uploaded to the SitePackages location and loaded at runtime instead of being extracted into wwwroot during deployment.
App Service
intermediate
6 commands
Aliases: WEBSITE_RUN_FROM_PACKAGE, run app from package, ZIP package runtime, App Service package mount, package-based deployment
Quick peek
Open full term page
Web
template-specs-upgraded
Scale out
Scale out means adding more running instances of an App Service plan or app so traffic is spread across additional workers.
App Service
intermediate
5 commands
Aliases: horizontal scale, App Service scale out, automatic scaling, instance count, elastic scale
Quick peek
Open full term page
Web
template-specs-upgraded
Scale up
Microsoft Learn describes App Service scale up as changing the pricing tier of an App Service plan. Moving to a larger tier can add CPU, memory, storage, and platform capabilities, while scaling down can remove features, so engineers review app requirements before changing the plan SKU.
App Service
intermediate
4 commands
Aliases: App Service scale up, vertical scaling, scale up App Service plan, pricing tier change, App Service plan SKU
Quick peek
Open full term page
Web
template-specs-upgraded
SCM site
The SCM site is the special App Service endpoint used by deployment and Kudu tooling.
App Service
intermediate
6 commands
Aliases: Kudu site, Advanced Tools site, App Service SCM endpoint, scm.azurewebsites.net, deployment endpoint
Quick peek
Open full term page
No glossary terms matched that search.
Try a service name, acronym, command group, or category such as RBAC , az group , App Service , Application Insights , Databases , or Azure AI Search .
Clear filters and show matches
Reset search