Search Azure terms

Containers premium Container Apps A serverless Azure service for running containerized apps and jobs without directly operating Kubernetes clusters. Serverless containers fundamentals 5 commands Aliases: Azure Container Apps Quick peek Open full term page

Containers premium Container Apps custom domain A custom hostname assigned to a Container App ingress endpoint. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps environment variable An environment variable passed into a Container Apps container. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps ingress The Container Apps setting that controls whether and how HTTP or TCP traffic reaches a container app. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps replica a running instance of a Container Apps revision that is added or removed as Azure Container Apps scales the workload Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps session an isolated, short-lived execution environment from a Container Apps dynamic session pool, often used for sandboxed code or custom runtime tasks Azure Container Apps intermediate 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

Containers premium Container Apps workload profile the Container Apps environment compute profile that controls resource size, scaling model, isolation, and billing behavior for deployed apps Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps job A Container Apps resource for running scheduled, event-driven, or manual containerized tasks to completion. Azure Container Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Containers verified Container Apps certificate A certificate used for TLS on a Container Apps custom domain. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers verified Container Apps exec An interactive command execution feature for a running Container App replica. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

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

Containers field-manual-complete Container Apps managed environment A Container Apps managed environment is the shared home where one or more Azure Container Apps and jobs run. It is not your container image or one app instance; it is the boundary around the runtime, networking, logging, certificates, Dapr settings, and workload profile capacity that those apps use. Teams choose an environment before creating. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers field-manual-complete Container Apps revision Microsoft Learn explains that a Container Apps revision is created at first deployment and whenever revision-scope settings change. Revision mode controls whether one or multiple revisions stay active, enabling traffic splitting, labels, rollbacks, and safer updates without changing the whole container app resource. in controlled production releases. Azure Container Apps intermediate 5 commands Aliases: Container Apps revision, active-revision, container apps revision, container-app-environment, container-apps, container-apps-ingress, container-apps-revision, container-apps-traffic-split, container-image, container-image-digest, deployment-labels, deployment-slot, inactive-revision, keda Quick peek Open full term page

Containers field-manual-complete Container Apps scale rule A Container Apps scale rule tells Azure Container Apps when to run more or fewer replicas of an app revision. Instead of guessing capacity manually, you define a trigger such as HTTP concurrency, CPU, memory, Service Bus messages, Kafka lag, or another KEDA-supported event source. The rule works with minimum and maximum replica limits, so. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers field-manual-complete Container Apps secret Microsoft Learn describes Container Apps secrets as application-scoped values that can be stored directly or referenced from Azure Key Vault. Revisions can use them through environment variables, registry credentials, or scale rules, while managed identity controls access to Key Vault references. during application configuration and rotation. Azure Container Apps intermediate 5 commands Aliases: Container Apps secret, app-service-app-setting, client-secret, container apps secret, container-apps, container-apps-environment-variable, container-apps-revision, container-apps-secret, container-registry, keda, key-vault, key-vault-access-policy, managed-identity, secret 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

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

DevOps premium Container image build the build step that turns source, Dockerfile instructions, dependencies, and metadata into a container image stored in a registry Deployment workflows intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container group the Azure Container Instances unit where containers share scheduling, lifecycle, local network, exposed endpoints, resources, and storage volumes Serverless containers fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Containers field-manual-complete Container App environment Microsoft Learn describes a Container Apps environment as a secure boundary around one or more container apps and jobs. The runtime manages the environment by handling OS upgrades, scale operations, failover procedures, resource balancing, shared networking, and observability settings for the workloads that run inside it. Serverless containers fundamentals 5 commands Aliases: Container App environment, app-service-plan, azure-kubernetes-service, azure-monitor, container app environment, container-app-environment, container-apps, container-apps-ingress, container-apps-managed-environment, container-apps-revision, container-apps-secret, container-apps-workload-profile, managed-identity Quick peek Open full term page

Containers field-manual-complete Container image A container image is the sealed package that a container runtime starts. It contains the application, runtime, libraries, filesystem layers, and metadata needed to create containers the same way each time. Teams push images to a registry and then reference them from. Container images fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers learning-path-anchor Target port A target port tells Azure Container Apps where to deliver traffic inside your container. Public or internal ingress may expose an endpoint, but the app still has to listen on a specific port. If the container listens on 8080 and ingress targets 80, users may see timeouts, failed probes, or gateway errors. The setting is small, but it is often the difference between the app being deployed and the app being reachable. It should match the application startup command, Dockerfile, framework port, and health probes. Azure Container Apps intermediate 5 commands Aliases: container target port, Container Apps target port, ingress targetPort, container ingress port Quick peek Open full term page

Containers premium Event-driven job An Event-driven job in Azure Container Apps starts job executions when a configured scale rule detects work from an event source. Teams use it to run finite container work such as queue processing, batch enrichment, report generation, or cleanup only when events or messages are waiting. It is not a continuously running container app, an AKS deployment, a scheduled job, or a guarantee that every event is processed exactly once. In production, confirm job trigger type, scale rule, minimum and maximum executions, polling interval, image version, secret references, managed identity, execution status, logs, retries, and queue depth before treating the. Azure Container Apps intermediate 6 commands Aliases: Container Apps event-driven job, KEDA job, event-triggered container job Quick peek Open full term page

Containers premium Event-driven scale rule An Event-driven scale rule is a Container Apps scaling configuration that uses event-source metrics to decide how many replicas or job executions to run. Teams use it to connect queue length, event backlog, HTTP load, Kafka lag, or other scaler metadata to automatic scaling decisions. It is not the event source itself, a Kubernetes HPA object, a fixed replica count, or a complete guarantee that the application processes events correctly. In production, confirm scaler type, metadata names, authentication method, min and max replicas, polling interval, cooldown behavior, event source metrics, container revision, and downstream capacity before treating the design as. Azure Container Apps intermediate 6 commands Aliases: KEDA scale rule, Container Apps event scale rule, custom scale rule Quick peek Open full term page

Containers premium External ingress External ingress in Azure Container Apps allows traffic from outside the Container Apps environment to reach a container app endpoint. Teams use it to publish a container app to callers outside the environment, including users, APIs, webhooks, partners, or front-end gateways that need a reachable HTTPS or TCP endpoint. It is not internal-only ingress, a custom domain certificate, a network security guarantee, or proof that authentication, authorization, rate limits, and backend health are configured correctly. Azure Container Apps intermediate 6 commands Aliases: external Container Apps ingress, public ingress, internet-facing ingress Quick peek Open full term page

Containers premium Active revision Active revision is the Container Apps revision that is allowed to receive traffic. In everyday Azure work, teams use it to roll out a new container image, keep a rollback candidate warm, or split traffic between versions. The useful evidence is revision mode, active state, replica health, labels, and traffic weight. Treat the term as Azure Container Apps intermediate 5 commands Aliases: Container Apps active revision, revision activation, active Container Apps revision Quick peek Open full term page

DevOps premium Canary deployment Canary deployment is a release approach that sends a small portion of real traffic to a new version before rolling it out broadly. Deployment workflows intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium HTTP scale rule An HTTP scale rule is an Azure Container Apps scaling rule that scales replicas based on concurrent HTTP requests. Azure Container Apps intermediate 5 commands Aliases: HTTP scale rule, http scale rule Quick peek Open full term page

Containers premium Inactive revision Inactive revision is an Azure Container Apps revision that remains in the revision list but is not actively serving traffic or running replicas. Azure Container Apps intermediate 5 commands Aliases: Inactive revision, inactive revision, inactive-revision Quick peek Open full term page

Networking premium Ingress Ingress controls how users, APIs, partners, and internal services can reach a workload and which network controls protect that entry point. Teams see it in container apps ingress settings, kubernetes ingress controllers. It is not egress, a firewall rule alone, a load balancer backend pool, or an application route inside code; confusing them can create public exposure, unreachable apps. 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 Networking Fundamentals 5 commands Aliases: incoming application traffic, inbound app traffic, Container Apps ingress, external ingress, internal ingress Quick peek Open full term page

Containers premium Internal ingress Internal ingress controls whether a Container Apps workload can receive traffic only from internal callers such as APIs, jobs, service meshes, or workloads on connected networks. Teams see it in container apps ingress settings, managed environments. It is not external ingress, private endpoint for another service, App Service VNet integration, Kubernetes ingress, or an Azure Firewall rule; confusing them can create public exposure of internal services, unreachable APIs. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior. Azure Container Apps Intermediate 5 commands Aliases: Container Apps internal ingress, private ingress, internal-only ingress, VNet ingress Quick peek Open full term page

Networking premium Internet egress Internet egress controls how workloads reach public endpoints for updates, APIs, package feeds, SaaS services, telemetry, and other internet-reachable dependencies. Teams see it in virtual networks, nat gateways. It is not inbound internet traffic, private endpoint traffic, ExpressRoute private peering, internal ingress, or Azure service-to-service traffic over private routes; confusing them can create data exfiltration paths, blocked updates. 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. Outbound connectivity Intermediate 5 commands Aliases: outbound internet traffic, egress to internet, public egress, internet-bound traffic Quick peek Open full term page

Containers premium CPU scale rule an autoscale rule that adds or removes running instances when CPU usage crosses a defined threshold for a sustained window. Autoscale intermediate 4 commands Aliases: CPU autoscale rule, Percentage CPU scale rule, Autoscale CPU rule Quick peek Open full term page

Containers premium Dapr Dapr is a distributed application runtime that gives microservices common building-block APIs for service invocation, pub/sub, bindings, state, workflows, and observability. Distributed applications intermediate 4 commands Aliases: Dapr, DAPR Quick peek Open full term page

Containers premium Dapr binding Dapr binding is a Dapr building block that lets an application trigger from or send data to external systems through configured input and output components. Azure Container Apps intermediate 4 commands Aliases: Dapr binding, DAPR binding Quick peek Open full term page

Containers premium Dapr pub/sub Dapr pub/sub is a Dapr building block that lets services publish messages to topics and subscribe to them through a configured broker component. Azure Container Apps intermediate 4 commands Aliases: Dapr pub/sub, DAPR pub/sub Quick peek Open full term page

Containers premium Dapr service invocation Dapr service invocation is a Dapr building block for calling another application by Dapr app ID instead of hard-coding its network address in the caller. Azure Container Apps intermediate 4 commands Aliases: Dapr service invocation, DAPR service invocation Quick peek Open full term page

Containers premium Dapr sidecar Dapr sidecar is a production Azure concept tied to Azure Container Apps. Azure Container Apps intermediate 4 commands Aliases: Dapr sidecar, DAPR sidecar Quick peek Open full term page

Containers premium Dedicated workload profile A dedicated workload profile in Azure Container Apps provides dedicated compute resources in a workload profiles environment, with billing based on profile instances rather than only per-app consumption. Azure Container Apps intermediate 4 commands Aliases: Container Apps dedicated workload profile, dedicated profile, workload profile dedicated plan Quick peek Open full term page

Containers premium Minimum replicas Minimum replicas is the lowest number of running replicas a scale controller or platform should maintain for a workload. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Azure Container Apps intermediate 4 commands Aliases: Container Apps minimum replicas, min replicas, minReplicas, scale floor Quick peek Open full term page

Containers premium Consumption workload profile the Azure Container Apps workload profile for serverless container workloads that should scale based on demand and incur cost only while running Azure Container Apps intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Containers template-specs-upgraded Revision Microsoft Learn describes Azure Container Apps revisions as immutable snapshots created when revision-scope changes are applied to a container app. Operators can list, show, copy, activate, deactivate, restart, label, and route traffic to revisions depending on revision mode and ingress configuration. Azure Container Apps fundamentals 5 commands Aliases: container app revision, Azure Container Apps revision, active revision, inactive revision, revision suffix Quick peek Open full term page

Containers template-specs-upgraded Revision mode Microsoft Learn describes Azure Container Apps revision mode as the setting that controls whether one revision or multiple revisions can be active at the same time. Single mode is the default; multiple mode enables traffic splitting, labels, blue-green testing, and manual deprovisioning control. Azure Container Apps intermediate 5 commands Aliases: container app revision mode, activeRevisionMode, single revision mode, multiple revision mode, revisions mode Quick peek Open full term page

Analytics top-250-pre130-priority-upgraded Integration runtime Integration runtime controls which compute, region, and network path data integration workloads use when moving data or executing pipeline activities. Data Factory intermediate 4 commands Aliases: ADF integration runtime, Azure integration runtime, self-hosted integration runtime, SSIS integration runtime, IR, Azure Data Factory integration runtime 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

Containers premium field-manual Maximum replicas The maximum replicas setting is the upper bound that prevents an autoscaled workload from creating more replicas than the configured limit. Teams use it when teams need scale-out capacity but also need to protect budgets, downstream services, and quota. In plain English, it gives operators a named control for bounded scaling, predictable cost exposure, and safer dependency protection during traffic spikes 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 scaling intermediate 4 commands Aliases: Maximum replicas, max replicas, maxReplicas, replica cap, replica ceiling, maximum replica count, Azure Container Apps, Azure Container Apps scaling 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

Containers premium field-manual Memory scale rule A memory scale rule is a Container Apps scale rule that uses memory utilization to add or remove running replicas within configured limits. Teams use it when a container workload becomes memory-bound before HTTP traffic, CPU, or queue length fully explains pressure. In plain English, it gives operators a named control for pressure-based scaling for memory-sensitive services while keeping replica bounds visible 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 scaling intermediate 4 commands Aliases: Memory scale rule, memory autoscale rule, KEDA memory trigger, Container Apps memory scale, memory utilization scale rule, KEDA memory rule, memory based scale rule, KEDA memory scaler, Container Apps memory scaling, Azure Container Apps and KEDA autoscaling, Azure Container Apps scaling Quick peek Open full term page

Containers template-specs-upgraded Scheduled job Microsoft Learn explains that an Azure Container Apps scheduled job is a job resource with trigger type Schedule and a cron expression. It starts containerized work at planned times, then uses job settings such as replica timeout, retry limit, parallelism, and completion count to control execution. Azure Container Apps intermediate 4 commands Aliases: Container Apps scheduled job, ACA scheduled job, scheduled container job, cron job in Container Apps, Schedule trigger type Quick peek Open full term page