Search Azure terms

Databases premium Failover Failover is the process of moving an application, database, or service workload from a primary resource to a secondary resource when the primary is unavailable, unhealthy, or intentionally switched. Teams use it to keep a business service running by directing traffic, reads, writes, or recovery operations to a standby region, zone, replica, failover group, or disaster recovery target. It is not a backup by itself, a promise of zero data loss, automatic repair for every dependency, or proof that clients, DNS, identity, and downstream services will follow correctly. Business continuity intermediate 6 commands Aliases: service failover, regional failover, database failover, planned failover, unplanned failover Quick peek Open full term page

Databases premium Active geo-replication Active geo-replication is an Azure SQL Database business-continuity feature that continuously replicates one primary database to a readable secondary database, often in another Azure region. It supports manual or programmatic geo-failover for individual databases and can also serve read-only workloads from the secondary. Azure SQL continuity advanced 5 commands Aliases: Azure SQL active geo-replication, geo-secondary, geo-replica Quick peek Open full term page

Migration premium Azure Site Recovery Azure Site Recovery helps provide disaster recovery by managing replication, failover, and failback for supported workloads. Disaster recovery fundamentals 5 commands Aliases: ASR, Azure Site Recovery, Azure disaster recovery, Site Recovery Quick peek Open full term page

Databases premium Azure SQL active geo-replication Azure SQL active geo-replication creates readable secondary databases in other regions for database-level disaster recovery and failover. Azure SQL Database intermediate 5 commands Aliases: Azure SQL active geo-replication, SQL geo-replication, active geo-replication, geo-secondary database Quick peek Open full term page

Databases premium Azure SQL failover group Provide a stable listener endpoint for applications that must survive an Azure SQL regional failover.; Coordinate failover for several related user databases instead of managing each geo-replica separately. Azure SQL Database intermediate 5 commands Aliases: Azure SQL failover group, SQL failover group, auto-failover group, failover group, geo-failover group Quick peek Open full term page

Storage premium Backup policy A backup policy defines when Azure Backup runs protection jobs and how long recovery points are retained for a protected workload. Backup and recovery intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Cosmos DB restore Cosmos DB restore means the recovery operation that creates or rebuilds Cosmos DB resources from a supported backup point or restorable resource in Azure Cosmos DB. In plain English, it is the thing developers and operators check when they need to understand how data access really works. It connects the application model to business continuity, recovery drills, accidental-delete response, timestamp selection, and controlled cutover back to production. For a production team, it turns vague database talk into a specific thing to inspect in the portal, SDK code, templates, metrics, and incident notes. Azure Cosmos DB intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Storage verified RA-GRS redundancy RA-GRS, or read-access geo-redundant storage, replicates storage account data to a secondary region and allows read access to that secondary copy. It combines geo-redundant replication with a secondary endpoint applications can use when the primary region is unavailable or degraded. Storage accounts intermediate 5 commands Aliases: read-access geo-redundant storage, read-access GRS, RA GRS Quick peek Open full term page

Databases complete SQL active geo-replication Microsoft Learn describes active geo-replication as a business continuity feature for Azure SQL Database that creates readable geo-secondary databases. If a regional disaster or large outage occurs, you can initiate geo-failover to a secondary database in another Azure region. promptly. quickly. Azure SQL intermediate 5 commands Aliases: SQL active geo-replication, sql active geo replication, sql-active-geo-replication Quick peek Open full term page

Databases premium Azure SQL Business Critical tier Azure SQL Business Critical tier is a vCore service tier for OLTP workloads that need high transaction rates, low-latency I/O, and high resilience through isolated replicas. Azure SQL Database fundamentals 5 commands Aliases: Azure SQL Business Critical tier, Business Critical tier, BusinessCritical, Premium-like vCore tier, SQL Business Critical Quick peek Open full term page

Management and Governance premium Business unit tag A business unit tag is an Azure resource tag that identifies which department, product line, cost center, or operating group owns a resource or its spend. Tags and naming fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL business critical compute MySQL business critical compute means a higher-performance MySQL Flexible Server compute choice for sustained production workloads that need stronger capacity and headroom. You see it when teams support payment, commerce, SaaS, analytics, or other databases with predictable high concurrency and business deadlines. Think of it as premium database capacity selected from measured demand, not from fear or guesswork. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. MySQL flexible server fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Storage learning-path-anchor Sync group A sync group is the container that tells Azure File Sync which cloud file share and which Windows Server folders should stay synchronized. Think of it as one file namespace with a hub in Azure and one or more on-premises or edge locations attached to it. If two groups represent different shares or business... Files, queues, and tables fundamentals 6 commands Aliases: Azure File Sync group, file sync group, sync topology, storage sync group Quick peek Open full term page

Management and Governance learning-path-anchor Tags Tags are labels you attach to Azure things so people and tools can understand what they are for. A tag has a name and a value, such as Owner=DataPlatform or Environment=Prod. Tags do not make a virtual machine faster, secure a database, or change a web app setting. They make the estate easier to organize, report on, govern, and automate. Useful tags answer questions the business actually asks: who owns this, what does it support, what environment is it, and who pays for it? Tags and naming advanced 5 commands Aliases: Azure tags, resource tags, name-value tags, Azure metadata tags 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

Databases premium Managed Instance failover group Managed Instance failover group is a disaster-recovery relationship that lets databases in a SQL Managed Instance fail over to a paired managed instance. Teams use it when business-critical databases need cross-region continuity and a managed failover path. In plain English, it gives operators a named control for planned or emergency recovery with clearer listener, replication, and ownership evidence 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 SQL Managed Instance intermediate 3 commands Aliases: Managed Instance failover group, Azure SQL Managed Instance Quick peek Open full term page

Databases premium Change feed processor A database capability or setting in Azure Cosmos DB that helps teams store, query, scale, secure, and recover application data with clearer ownership, safety, and operational context. Azure Cosmos DB fundamentals 15 commands Aliases: No aliases yet Quick peek Open full term page

Storage verified Recovery point objective Recovery point objective is documented by Microsoft as part of the Backup and recovery area in Azure. Backup and recovery intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

AI and Machine Learning premium Azure OpenAI Azure OpenAI provides OpenAI model capabilities through Azure resources, deployments, identity, networking, quota, and monitoring controls. Azure OpenAI intermediate 8 commands Aliases: Azure OpenAI Service Quick peek Open full term page

AI and Machine Learning premium Scoring profile A scoring profile is an Azure AI Search index setting that boosts ranking for matches that meet business rules. It can weight text fields or apply functions for freshness, distance, magnitude, or tags, and a query chooses one profile to influence returned order. Azure AI Search fundamentals 8 commands Aliases: Azure AI Search scoring profile, search relevance profile, relevance scoring profile, scoringProfiles, boosting profile Quick peek Open full term page

Databases premium Cosmos DB TTL Cosmos DB TTL is the time-to-live setting that lets Cosmos DB automatically delete items after a configured number of seconds. It turns data expiration into a database policy instead of a manual cleanup job. You see it when containers store sessions, events, temporary search data, soft-delete markers, or records with explicit retention windows. The production check is whether container-level TTL, item overrides, change-feed behavior, and recovery expectations match the business retention rule. Document the decision in code, templates, metrics, and runbooks. Azure Cosmos DB intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Data Lake analytics workload A production analytics workload that stores, transforms, governs, and serves large data sets from a data lake using Azure services such as ADLS Gen2, Data Factory, Databricks, Synapse, or Fabric. Data Lake Storage Intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Data Lake bronze layer The raw ingestion layer in a lakehouse or medallion architecture where source data first lands with minimal transformation and strong traceability. Data Lake Storage Gen2 Intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Data Lake curated zone The governed, consumer-ready area of a data lake where cleaned, conformed, and documented datasets are served for reporting, analytics, AI, or downstream applications. Data Lake Storage Gen2 Intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Analytics premium Databricks catalog The top-level Unity Catalog namespace that organizes schemas, tables, views, volumes, models, functions, permissions, lineage, and governed data ownership. Azure Databricks fundamentals 6 commands Aliases: Unity Catalog catalog, Azure Databricks catalog, catalog object Quick peek Open full term page

Databases premium Foreign key A foreign key is a column or set of columns that links rows in one table to key values in another table and helps enforce referential integrity. Teams use it to keep child records such as orders, invoices, payments, devices, or claim lines tied to valid parent records instead of allowing orphaned data to silently enter the database. It is not an index by itself, a security boundary, a substitute for business validation, or an enforced guarantee in every Azure analytics engine that can store a declared relationship. Relational database intermediate 6 commands Aliases: FK, foreign key constraint, referential constraint, SQL foreign key Quick peek Open full term page

AI and Machine Learning premium Foundry Agent A Foundry Agent is an AI agent built or hosted in Microsoft Foundry Agent Service with instructions, model selection, tools, knowledge, and runtime execution evidence. Teams use it to automate business tasks that require model reasoning, tool calls, enterprise knowledge, workflow steps, retrieval, approvals, and observable runs inside a governed Azure AI platform. It is not a magic autonomous worker, a security principal by itself, a replacement for process controls, or a safe production feature without tool permissions, evaluation, monitoring, and human escalation. Microsoft Foundry intermediate 6 commands Aliases: Microsoft Foundry agent, Foundry Agent Service agent, AI agent in Foundry, agent service agent Quick peek Open full term page

Integration premium Service Bus subscription Service Bus subscription is a named receiver under a Service Bus topic. It behaves like a virtual queue: messages published to the topic are copied into the subscription when its rules match, and receivers read, lock, complete, defer, or dead-letter those subscription messages. Messaging fundamentals 6 commands Aliases: Azure Service Bus subscription, topic subscription, Service Bus topic subscription, subscription entity Quick peek Open full term page

Integration premium Service Bus topic Service Bus topic is a publish-subscribe entity inside a Service Bus namespace. Publishers send one message to the topic, and matching subscriptions receive their own copies. Topics are used when several downstream systems need the same business event without coupling the publisher to every receiver. Messaging fundamentals 6 commands Aliases: Azure Service Bus topic, Service Bus pub-sub topic, topic entity, broker topic Quick peek Open full term page

Web premium Service Bus trigger Service Bus trigger is an Azure Functions binding that starts function execution when a message arrives on a Service Bus queue or topic subscription. It connects the Functions runtime to Service Bus, supports queue, topic, and session scenarios, and uses app settings or identity-based connections for access. Azure Functions intermediate 6 commands Aliases: Azure Functions Service Bus trigger, ServiceBusTrigger, Service Bus queue trigger, Service Bus topic trigger Quick peek Open full term page

AI and Machine Learning verified Prompt flow Prompt flow is a way to build and test an AI application as a flow instead of a single prompt. A flow can connect prompts, Python logic, tools, inputs, outputs, variants, and evaluation steps. In Microsoft Foundry classic and Azure Machine Learning, it helped teams prototype, debug, compare, deploy, and monitor LLM-based applications. In 2026, it is also a migration topic because Microsoft announced that feature development ended and full retirement is planned for April 20, 2027. Azure Machine Learning advanced 18 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium AKS maintenance window An AKS maintenance window is a planned maintenance configuration that controls when AKS starts certain cluster and node image upgrade operations. It helps teams align automatic upgrades and maintenance-sensitive changes with approved business windows, while Azure platform maintenance for underlying infrastructure remains separate. AKS operations Intermediate 5 commands Aliases: Azure Kubernetes Service maintenance window, aks maintenance window Quick peek Open full term page

DevOps premium Azure DevOps organization The top-level Azure DevOps Services container that connects related projects, users, repositories, pipelines, artifacts, permissions, and organization settings. Azure DevOps fundamentals 5 commands Aliases: Azure DevOps org Quick peek Open full term page

Storage premium Azure file share An Azure file share is a managed cloud share hosted by Azure Files. It behaves like a network file share, but Microsoft runs the storage service instead of your team maintaining file servers, disks, operating systems, and failover. Files, queues, and tables fundamentals 5 commands Aliases: Azure Files share Quick peek Open full term page

Management and Governance premium Azure Lighthouse Azure Lighthouse enables secure delegated management of Azure resources across customer tenants, supporting service providers and central teams with scalable cross-tenant governance. Delegated resource management advanced 5 commands Aliases: Lighthouse, delegated resource management, Microsoft Managed Services delegation Quick peek Open full term page

Databases premium Azure SQL General Purpose tier Azure SQL General Purpose tier is a vCore service tier for common workloads that need balanced compute and storage at budget-oriented pricing. Azure SQL Database fundamentals 5 commands Aliases: Azure SQL General Purpose tier, GP tier, General Purpose tier, GeneralPurpose, SQL General Purpose Quick peek Open full term page

Identity premium B2B collaboration Microsoft Entra B2B collaboration lets organizations invite external users and business partners to access applications and resources while keeping control of corporate data and access policies. External identities 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

Analytics premium Data Factory pipeline A logical grouping of Data Factory activities that performs a coordinated data movement, transformation, or control-flow process. Data integration and orchestration Intermediate 5 commands Aliases: Data Factory pipeline, ADF pipeline, data factory pipeline Quick peek Open full term page

Storage premium Data Lake gold layer The Data Lake gold layer is the business-ready medallion layer where curated, aggregated, and governed data is published for analytics, reporting, and decision support. Medallion lakehouse architecture intermediate 5 commands Aliases: gold layer, gold zone, curated business layer, trusted reporting layer Quick peek Open full term page

Storage premium Data Lake partition folder A Data Lake partition folder is a directory pattern, often key=value, that groups files by values such as date, region, tenant, or business domain for efficient reads. Data Lake Storage Gen2 intermediate 5 commands Aliases: partition folder, Hive-style partition folder, date partition folder, lake partition path Quick peek Open full term page

AI and Machine Learning premium Document Intelligence custom model A Document Intelligence custom model is a trained model built from representative labeled documents to extract fields from organization-specific document types. Document Intelligence intermediate 5 commands Aliases: custom extraction model, custom neural model, custom template model, trained custom document model Quick peek Open full term page

Integration premium Event Grid custom topic Event Grid custom topic is a user-created Azure Event Grid topic that gives custom applications an endpoint for publishing business or application events. In Azure, it shows up when custom applications publish shipment, order, payment, device, or workflow events that subscribers need to process independently. Teams use it to review topic name, region, access keys or managed identity options, input schema, event subscriptions, filters, retry policy, dead-letter destination, and monitoring before changing production behavior. It is not an Azure system topic, Event Grid domain, Event Hub, or Service Bus topic. Event routing intermediate 5 commands Aliases: Azure Event Grid custom topic, custom Event Grid topic Quick peek Open full term page

Integration premium Event Grid delivery schema Event Grid delivery schema is the event format Azure Event Grid uses when sending an event to a subscriber endpoint. In Azure, it shows up when publishers and handlers must agree on whether delivered events use Event Grid schema, CloudEvents v1.0, or a custom input schema shape. Teams use it to review event subscription delivery schema, publisher input schema, handler parser, API contract, sample payloads, validation tests, filters, and compatibility monitoring before changing production behavior. It is not the handler destination type, the event source, a JSON schema registry, or the business data model itself. Event routing intermediate 5 commands Aliases: Event Grid event delivery schema, event delivery schema Quick peek Open full term page

Integration premium Event Grid event handler Event Grid event handler is the destination endpoint or Azure service that receives matching events from an Event Grid event subscription and acts on them. In Azure, it shows up when an event-driven workflow needs a function, logic app, webhook, queue, topic, event hub, storage queue, relay connection, or namespace topic to process events. Teams use it to review handler type, endpoint URL or resource ID, authentication method, validation handshake, managed identity permissions, retry behavior, dead-lettering, monitoring, and scaling plan before changing production behavior. It is not the event publisher, Event Grid topic, event schema, or the business event itself. Event routing fundamentals 5 commands Aliases: Event Grid handler, Event Grid destination Quick peek Open full term page

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

Integration premium Event Hubs batch An Event Hubs batch is a client-side group of events prepared for sending or processing together while respecting Event Hubs size, partition, and producer constraints. Teams use it to send or process multiple events efficiently instead of making every event a separate network operation. It is not an Azure resource, a Capture file, a partition, or a guarantee that every event in business logic was processed exactly once. 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: Event Hubs event batch, EventDataBatch, batch send to Event Hubs Quick peek Open full term page

Integration premium Event Hubs checkpoint An Event Hubs checkpoint is a consumer-maintained record of progress, usually an offset or sequence number per partition, used to resume processing without rereading every event. Teams use it to remember how far a consumer has processed in each partition so stream processing can restart, scale, or fail over without losing its place. It is not the event data itself, a retention policy, a capture archive, or a guarantee that every downstream business action succeeded exactly once. Event Hubs intermediate 5 commands Aliases: Event Hubs consumer checkpoint, Event Hubs offset checkpoint, EventProcessor checkpoint Quick peek Open full term page

Integration premium Event Hubs consumer An Event Hubs consumer is an application or service instance that reads events from partitions of an event hub through a consumer group. Teams use it to read and process events from an Event Hub stream for analytics, automation, storage, monitoring, or business applications. It is not a producer, a consumer group definition by itself, a Capture archive, or proof that the application processed events correctly. 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 consumer, Event Hubs reader, event stream consumer Quick peek Open full term page

Integration premium Event Hubs consumer offset An Event Hubs consumer offset is the position a consuming application uses to continue reading events within a specific partition, usually captured through checkpoint state. Teams use it to understand where a reader stopped, resumed, replayed, or skipped within a retained Event Hubs partition. It is not a global cursor for the whole event hub, a Service Bus dequeue count, or proof that downstream business processing succeeded. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: consumer offset, Event Hubs reader offset, stream consumer position Quick peek Open full term page