Search Azure terms

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

Monitoring and Observability premium Search service diagnostic logs Search service diagnostic logs are Azure Monitor resource logs from Azure AI Search that record query, suggest, autocomplete, lookup, indexing, service statistics, and operational events. They are collected in Log Analytics or storage when diagnostic settings are enabled on the search service. Data operations intermediate 5 commands Aliases: Azure AI Search logs, search resource logs, Microsoft.Search diagnostics, search operation logs, Search diagnostic settings Quick peek Open full term page

Storage field-manual-complete Storage analytics logs Storage Analytics logs are classic Azure Storage logs that record details about successful and failed requests for Blob, Queue, and Table services. They help troubleshoot request-level behavior, but Azure Monitor storage logs are generally preferred for modern monitoring, querying, alerting, and centralized retention. Storage monitoring fundamentals 5 commands Aliases: classic storage logs, Azure Storage Analytics logging, storage request logs Quick peek Open full term page

Networking field-manual-complete NSG flow logs NSG flow logs are records of traffic decisions made by Azure network security groups. They show whether flows were allowed or denied, which rule was involved, and where the traffic was headed. In 2026 they are a legacy operational signal: existing logs still matter for investigations, but new NSG flow logs can no longer be created. A learner should understand them as historical evidence and a migration concern, not as the preferred design for new network logging. Diagnostics fundamentals 4 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

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

Storage learning-path-anchor Time-based retention Time-based retention in Azure Blob Storage is an immutability policy that keeps blob data in a write-once, read-many state for a specified retention interval. It can be applied at container or version scope to protect records from modification or deletion until the retention period expires. Blob Storage fundamentals 5 commands Aliases: Time-based retention, time based retention, Azure Time-based retention, Microsoft Learn Time-based retention, immutability policy, WORM retention, immutable blob retention, retention days, container immutability policy Quick peek Open full term page

Databases learning-path-anchor Cosmos DB continuous backup Azure Cosmos DB continuous backup is the backup mode that supports point-in-time restore for supported Cosmos DB resources within a configured retention tier. Azure Cosmos DB fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Identity learning-path-anchor Tenant ID A tenant ID is the globally unique identifier for a Microsoft Entra tenant. Microsoft Entra fundamentals 4 commands Aliases: Tenant ID, tenant id, Azure Tenant ID, Microsoft Entra tenant ID, directory ID, tenantId Quick peek Open full term page

Monitoring and Observability learning-path-anchor Throughput Throughput is the amount of work a system completes over time, such as requests, messages, bytes, events, or transactions per second. In Azure, teams measure it with service metrics, logs, and capacity settings to judge whether an app, database, storage account, or messaging pipeline can sustain demand. Performance intermediate 4 commands Aliases: Throughput, throughput, Azure Throughput, Microsoft Learn Throughput, requests per second, events per second, transactions per second, bytes per second, work completed over time Quick peek Open full term page

Databases premium Conflict resolution policy the container-level Cosmos DB setting that defines how write conflicts are resolved when more than one region can update the same data Cosmos DB intermediate 15 commands Aliases: No aliases yet Quick peek Open full term page

AI and Machine Learning premium Computer Vision the Azure AI capability that helps applications understand images, read text, detect visual features, and return structured insights from pictures or screenshots Azure AI services fundamentals 12 commands Aliases: No aliases yet 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

Databases premium Conflict resolution the way Azure Cosmos DB decides the winning version when concurrent writes from multiple regions change the same item or logical record Data platform intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Event subscription An Event subscription is an Event Grid configuration that selects events from a source and delivers matching events to a destination endpoint. Teams use it to route storage, resource, custom, or partner events to the correct webhook, function, queue, topic, or event handler. It is not the event source itself, an Azure subscription, an Event Hubs consumer group, or proof that the destination successfully processed every event. In production, confirm source scope, event types, filters, endpoint URL or resource ID, authentication method, dead-letter destination, retry settings, diagnostic logs, and receiving application owner before treating the design as healthy or ready. Event Grid intermediate 6 commands Aliases: Event Grid subscription, event routing subscription, event delivery subscription 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

AI and Machine Learning premium Pipeline job In Azure Machine Learning, a pipeline job is a parent job that orchestrates connected command or sweep jobs as steps. It defines inputs, outputs, compute, settings, and step dependencies so reusable training, evaluation, or data-preparation workflows can run repeatably in a workspace. Machine learning intermediate 6 commands Aliases: No aliases yet 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

Networking premium Web Application Firewall Azure Web Application Firewall is a centralized protection service for HTTP applications. It can run with Application Gateway, Front Door, Application Gateway for Containers, or Azure CDN, using managed and custom rules to detect and block common exploits such as SQL injection and cross-site scripting. Application security fundamentals 6 commands Aliases: WAF, Azure WAF, Application Gateway WAF, Front Door WAF Quick peek Open full term page

Containers premium ACR build ACR build lets Azure Container Registry build an image in the cloud from source context or a Dockerfile. It is handy when you do not want a local Docker engine or want a pipeline to build and push directly in Azure. Azure Container Registry intermediate 5 commands Aliases: ACR 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 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

Analytics premium Azure Data Explorer A fully managed, high-performance analytics service for near-real-time analysis of large telemetry, log, event, and time-series datasets. Real-time analytics intermediate 5 commands Aliases: ADX, Kusto Quick peek Open full term page

Databases premium Azure SQL auditing Azure SQL auditing tracks database events and writes audit logs to supported destinations such as storage, Log Analytics, or Event Hubs. Azure SQL Database fundamentals 5 commands Aliases: Azure SQL audit logs, Azure SQL auditing, SQL auditing, database auditing Quick peek Open full term page

AI and Machine Learning premium Batch deployment A batch deployment in Azure Machine Learning is the deployment configuration behind a batch endpoint, defining the model or pipeline, compute, environment, and execution behavior for asynchronous inference. Azure Machine Learning intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

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

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

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

AI and Machine Learning premium Confidence score a model-provided certainty value that helps teams judge whether extracted fields, text, tables, or classifications should be accepted automatically or reviewed by a person Document Intelligence fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Connected registry an Azure Container Registry capability that keeps container images available in remote, edge, or intermittently connected environments by syncing with a parent registry Azure Container Registry intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

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

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

Integration premium Event Hubs Azure Event Hubs is a fully managed, real-time data streaming platform for ingesting large volumes of events with low latency and routing them to consumers for processing. Teams use it to collect telemetry, application events, logs, clickstreams, and device data at scale before analytics, functions, or downstream services process them. It is not a queue for command messages, a workflow engine, a database, or an Event Grid routing topic for discrete platform events. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs, Azure Event Hubs service Quick peek Open full term page

Integration premium Event Hubs partition An Event Hubs partition is an ordered sequence of events within an event hub that enables parallel event ingestion and consumption. Teams use it to split a stream into parallel ordered logs so producers and consumers can scale while preserving order within each partition. It is not a separate namespace, a consumer group, a database shard with automatic rebalancing, or a guarantee that all events are globally ordered. 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: partition, Event Hubs stream partition, event stream partition Quick peek Open full term page

Integration premium Event Hubs producer An Event Hubs producer is an application, service, device, or client that sends events to an event hub. Teams use it to identify the workload that publishes telemetry, transactions, logs, or business events into an Event Hubs stream. It is not a consumer, event processor, checkpoint, storage capture destination, or proof that downstream systems processed the event. 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: producer, event publisher, Event Hubs publisher client 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

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

AI and Machine Learning premium Indexer schedule Indexer schedule is the Azure concept that controls how often Azure AI Search refreshes indexed content from a supported data source. Teams see it when working with azure ai search indexer definitions, schedule interval. It is not a Data Factory trigger, an Event Grid subscription, a cron job, or a manual indexer run; that distinction matters because bad assumptions create stale search results, overlapping refresh work. Use the term when reviewing ownership, access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same resource, setting, or behavior. Azure AI Search Intermediate 5 commands Aliases: Azure AI Search indexer schedule, search indexer recurrence, indexing schedule, scheduled indexer run Quick peek Open full term page

AI and Machine Learning premium Inference endpoint Inference endpoint is the Azure concept that controls how applications invoke deployed machine learning models securely, reliably, and measurably in Azure. Teams see it when working with azure machine learning online endpoints, batch endpoints. It is not a model artifact, a training job, an Azure OpenAI deployment, or an application API gateway by itself; that distinction matters because bad assumptions create failed predictions, public exposure. Use the term when reviewing ownership, access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same resource, setting, or behavior. Azure Machine Learning Intermediate 5 commands Aliases: ML inference endpoint, online endpoint, managed online endpoint, batch endpoint, scoring endpoint Quick peek Open full term page

DevOps premium Infrastructure deployment script Infrastructure deployment script controls how deployment teams run imperative setup, validation, or bridge logic inside an otherwise declarative Azure infrastructure deployment. Teams see it in bicep files, arm templates. It is not a local shell script, a DevOps pipeline task, a custom script extension, or normal template declarative resource creation; confusing them can create hung deployments, leaked script output. 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. Infrastructure as Code Intermediate 5 commands Aliases: deployment script, ARM deployment script, Bicep deployment script, deploymentScripts resource, scripted IaC step 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

Security premium Just-in-time VM access Just-in-time VM access is the Microsoft Defender for Cloud control that locks down VM management ports and opens approved inbound access only for a limited time. Defender for Cloud intermediate 5 commands Aliases: JIT VM access, Defender for Cloud JIT, just in time access, JIT network access policy Quick peek Open full term page

Security premium Key Key controls how protected workloads use cryptographic material for encryption, signing, key wrapping, customer-managed keys, and regulated data protection. Teams see it in key vault keys, managed hsm keys. It is not a password, secret value, certificate, storage account key, shared access signature, or application configuration setting; confusing them can create failed encryption operations, accidental key deletion. 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. Secrets and cryptography Fundamentals 5 commands Aliases: Azure Key Vault key, cryptographic key, key object, encryption key Quick peek Open full term page