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 50 of 534 matching terms. Narrow the search to reduce the list.
Databases
premium
Geo-replication
Geo-replication is a database disaster recovery pattern where data from a primary database is replicated to one or more secondary databases in other regions. Teams use it to keep a recoverable copy of important data, support read-locality scenarios, and prepare for manual or application-driven failover during a regional outage. In daily Azure work, it shows up when engineers configure Azure SQL active geo-replication, review failover plans, test secondary connectivity, compare it with failover groups, or investigate replication lag.
High availability
intermediate
4 commands
Aliases: active geo-replication, database geo-replication, regional database replication
Quick peek
Open full term page
Databases
verified
Read replica
A read replica is a read-only database copy used to offload read traffic, improve regional access, or support reporting without sending every query to the writable primary. Azure services implement this pattern differently, with asynchronous replication, replica endpoints, lag monitoring, and failover options depending on engine.
Database replication
advanced
2 commands
Aliases: read-only replica, database read replica, replica database, read scale-out replica, reporting replica
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
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
verified
Redis active geo-replication
A multi-region Azure Redis capability that links caches so each participating instance can act as a local primary for reads and writes.
Azure Managed Redis
advanced
7 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
verified
Redis Enterprise database
A Redis Enterprise database is the database resource inside a Redis Enterprise cluster. It defines the actual Redis endpoint, port, clustering policy, modules, eviction policy, persistence settings, access-key behavior, and geo-replication links that applications use after the cluster is provisioned.
Data platform
intermediate
5 commands
Aliases: RedisEnterprise database, Enterprise database, Redis Enterprise DB
Quick peek
Open full term page
Databases
verified
Redis geo-replication
Redis geo-replication connects Redis instances across Azure regions so cache data can be synchronized for regional resilience or lower-latency access. Azure Managed Redis supports active geo-replication groups with multiple writable instances, eventual consistency, configuration requirements, and operational procedures for regional outages.
Cache and in-memory data
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
verified
Redis passive geo-replication
Redis passive geo-replication links two Premium Azure Cache for Redis instances, usually across Azure regions. The primary accepts reads and writes, replicated data flows to a read-only secondary, and failover is an operator-driven disaster recovery action rather than automatic traffic switching.
Azure Managed Redis
advanced
5 commands
Aliases: passive Redis geo-replication, Azure Cache Redis geo replication, Redis server link, read-only Redis secondary
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
Containers
premium
ACR geo-replication
ACR geo-replication keeps container images closer to workloads in multiple regions. Developers push to one registry, and Azure replicates content so regional clusters can pull faster and more reliably, assuming the registry uses the Premium tier.
Azure Container Registry
intermediate
5 commands
Aliases: ACR
Quick peek
Open full term page
Databases
premium
Azure Database for MySQL Flexible Server
A fully managed Azure database service for MySQL workloads with configurable compute, storage, backups, networking, maintenance, and high availability options.
Managed MySQL
intermediate
5 commands
Aliases: MySQL Flexible Server
Quick peek
Open full term page
Databases
premium
Azure Database for PostgreSQL Flexible Server
A fully managed Azure PostgreSQL service with configurable compute, storage, backups, networking, maintenance, extensions, and high availability options.
Managed PostgreSQL
intermediate
5 commands
Aliases: PostgreSQL Flexible Server
Quick peek
Open full term page
Databases
premium
Azure SQL Database
Azure SQL Database is a fully managed relational database service in Azure that provides SQL Server-compatible engines as single databases, elastic pools, and serverless or provisioned compute choices. Microsoft Learn presents it as platform as a service with built-in availability, backups, patching, scaling, and security integration.
Database
intermediate
5 commands
Aliases: Azure SQL DB, Azure SQL Database, Azure SQL pooled database, Azure SQL single database, SQL Database
Quick peek
Open full term page
Databases
premium
Azure SQL database copy
Azure SQL database copy creates a transactionally consistent copy of an Azure SQL Database using portal, PowerShell, Azure CLI, or Transact-SQL.
Azure SQL Database
fundamentals
5 commands
Aliases: Azure SQL copy, Azure SQL database copy, CREATE DATABASE AS COPY OF, SQL database copy, database copy
Quick peek
Open full term page
Databases
premium
Azure SQL Database DTU model
Azure SQL Database DTU model is a purchasing model that bundles compute, storage, and I/O resources into Database Transaction Units for Basic, Standard, and Premium tiers.
Azure SQL Database
fundamentals
5 commands
Aliases: Azure SQL Database DTU model, DTU model, DTU-based purchasing model, Database Transaction Unit, eDTU
Quick peek
Open full term page
Analytics
premium
Kusto database
Kusto database is a logical container inside an Azure Data Explorer cluster that holds tables, functions, policies, permissions, and ingestion/query configuration.
Azure Data Explorer database
Intermediate
5 commands
Aliases: ADX database, Azure Data Explorer database, Kusto DB
Quick peek
Open full term page
Analytics
premium
Kusto follower database
Kusto follower database is a read-only database attached from another Azure Data Explorer cluster so consumers can query leader data without copying it.
Azure Data Explorer data sharing
Advanced
5 commands
Aliases: ADX follower database, Azure Data Explorer follower database, followed database
Quick peek
Open full term page
Databases
premium
PostgreSQL database
A named PostgreSQL catalog inside a flexible server that holds schemas, tables, extensions, permissions, and application data.
Azure Database for PostgreSQL
fundamentals
5 commands
Aliases: PostgreSQL database, postgresql database, Azure Database for PostgreSQL database, database catalog, schema migration, charset, collation
Quick peek
Open full term page
Databases
premium
Serverless SQL database
A serverless SQL database is an Azure SQL Database single database configured with the serverless compute model. It automatically scales compute within configured limits, can auto-pause in supported tiers, resumes on activity, and keeps the managed SQL Database platform features such as backups, patching, monitoring, and security.
Azure SQL Database
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Integration
premium
Service Bus geo-replication
Service Bus geo-replication is a Premium-tier feature that continuously replicates a namespace's metadata and message data from the primary region to a secondary region. It lets operators promote the secondary when the primary region degrades, preserving queues, topics, subscriptions, filters, and message state.
Service Bus
advanced
5 commands
Aliases: Service Bus data replication, Service Bus regional replication, Service Bus secondary region, Service Bus namespace replication, Service Bus Premium geo replication
Quick peek
Open full term page
Databases
premium
Shared database throughput
Shared database throughput in Azure Cosmos DB means RU/s are provisioned at the database level and shared by containers in that database. Microsoft recommends container-level throughput for most workloads because shared throughput can create unpredictable performance and scale behavior across containers.
Azure Cosmos DB
intermediate
5 commands
Aliases: Cosmos DB shared database throughput, database-level throughput, shared RU/s database, Cosmos DB database throughput, shared throughput database
Quick peek
Open full term page
Databases
premium
Cosmos DB database
An Azure Cosmos DB database is a unit of management for one or more containers within an account and acts as a namespace for child resources.
Cosmos DB
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Database compatibility level
A SQL database setting that controls engine behaviors and query-processing compatibility so applications can move versions without every feature changing at once.
Azure SQL
fundamentals
4 commands
Aliases: compatibility level, SQL compatibility level, Azure SQL compatibility level
Quick peek
Open full term page
Monitoring and Observability
premium
Database diagnostic settings
Azure Monitor routing rules that export database logs and metrics to Log Analytics, Storage, Event Hubs, or partner destinations for investigation and governance.
Azure Monitor
intermediate
4 commands
Aliases: SQL diagnostic settings, database diagnostics export, Azure Monitor diagnostic settings for databases
Quick peek
Open full term page
Databases
premium
Database server / account
The Azure resource boundary that owns database instances, authentication, networking, regional placement, and service-wide settings for a database workload.
Database platform
intermediate
4 commands
Aliases: database account, database server, database resource account, logical database server
Quick peek
Open full term page
Databases
premium
Hyperscale database
Hyperscale database is an individual Azure SQL Database configured to use the Hyperscale service tier and its scalable storage and compute architecture.
Azure SQL
intermediate
4 commands
Aliases: Azure SQL Hyperscale database, hyperscale database, Hyperscale database, Hyperscale SQL database
Quick peek
Open full term page
Databases
premium
MySQL database
MySQL database means a named database inside an Azure Database for MySQL server that stores application tables, users, routines, and data objects. You see it when developers create application data boundaries, run migrations, grant access, restore data, or separate tenant and service data. Think of it as the application data boundary inside the managed MySQL server. 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.
Azure Database for MySQL
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Managed instance database
A managed instance database is a database hosted inside Azure SQL Managed Instance with managed platform operations and SQL Server compatibility features. Teams use it when a workload needs managed SQL operations while keeping instance-level features closer to SQL Server. In plain English, it gives operators a named control for database-level ownership, backup evidence, restore planning, and migration clarity within a managed instance 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 database, Azure SQL Managed Instance
Quick peek
Open full term page
Databases
field-manual-complete
Ledger database
Microsoft Learn describes a database ledger as part of SQL ledger, where ledger tables record cryptographic digests and history so organizations can verify protected data was not silently changed and produce evidence of database integrity for audits.
Azure SQL
fundamentals
11 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
field-manual-complete
Object replication policy
An object replication policy is the rule set that tells Azure Blob Storage what to replicate and where to send it. The policy connects a source storage account to a destination storage account, then uses rules to pair containers and optionally filter blobs. It is the configuration behind object replication, not the copied data itself. Operators use the policy to prove intent: which accounts are connected, which containers participate, and which blobs should appear in the destination.
Storage accounts
intermediate
6 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
complete
SQL contained database user
Microsoft Learn describes contained database users as users that authenticate at the database level rather than through a matching login in the master database. In Azure SQL Database, they can support SQL authentication or Microsoft Entra identities, and the database name must be included in the connection string.
Data platform
intermediate
6 commands
Aliases: contained database user, database-contained user, Azure SQL contained user, CREATE USER FROM EXTERNAL PROVIDER
Quick peek
Open full term page
Storage
field-manual-complete
Object replication
Object replication is an Azure Blob Storage feature that copies block blobs from one storage account to another after data is written. It is useful when teams need a second copy in another account, region, or operational boundary without building a custom copy job. It is not the same as account redundancy, backup, or failover. A learner should think of it as policy-driven, asynchronous replication for selected containers and blobs, controlled by storage-account settings and rules.
Azure Storage
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
verified
Redis database
A Redis database is the keyspace and endpoint an application uses to store Redis keys, values, streams, sets, hashes, and other data structures. In Azure Managed Redis and Redis Enterprise, database settings govern clustering, eviction, access, persistence, and client connectivity inside the managed service.
Azure Managed Redis
fundamentals
5 commands
Aliases: Redis keyspace, Redis DB, Redis cache database
Quick peek
Open full term page
Analytics
field-manual-complete
Synapse lake database
Synapse lake database is documented by Microsoft as part of the Synapse Analytics area in Azure.
Synapse Analytics
fundamentals
5 commands
Aliases: Azure Synapse lake database, Synapse database designer, Synapse lake database, lake database, lake-backed database, metadata over data lake, synapse lake database, synapse-lake-database
Quick peek
Open full term page
Databases
complete
Shared throughput database
A Cosmos DB database whose containers share provisioned request units from one database-level throughput pool.
Cosmos DB
intermediate
5 commands
Aliases: Cosmos DB shared throughput database, database-level throughput, shared database throughput, database RU/s pool
Quick peek
Open full term page
Databases
complete
Single database
A fully managed Azure SQL Database with its own compute, storage, backup, and service-tier settings under a logical server.
Azure SQL
fundamentals
5 commands
Aliases: Azure SQL single database, SQL single database, single Azure SQL database
Quick peek
Open full term page
Databases
complete
SQL database
Microsoft Learn describes Azure SQL Database as a fully managed relational database service where a single database is created on a logical server and configured with compute, storage, backup, security, and availability settings. It supports portal, PowerShell, Azure CLI, REST, and Transact-SQL operations for deployment and management.
Azure SQL
fundamentals
5 commands
Aliases: Azure SQL database, single SQL database, Azure SQL DB, SQL DB resource
Quick peek
Open full term page
Databases
complete
SQL database collation
Microsoft Learn explains that database collation defines the default rules for character data comparison, sorting, case sensitivity, accent sensitivity, and Unicode behavior. A database collation can be specified when creating or modifying a database, but existing column-level collations and stored data are not automatically changed.
Data platform
intermediate
5 commands
Aliases: database collation, SQL collation, Azure SQL collation, default database collation
Quick peek
Open full term page
Databases
complete
SQL database copy
Microsoft Learn describes database copy in Azure SQL Database as an operation that creates a new database from an existing database through the portal, Azure CLI, PowerShell, or Transact-SQL. The copy runs asynchronously, creates the target database after acceptance, and can require login remapping across servers.
Azure SQL
intermediate
5 commands
Aliases: database copy, Azure SQL database copy, copy database, SQL DB clone
Quick peek
Open full term page
Databases
complete
SQL database export
Microsoft Learn describes SQL database export as creating a BACPAC file that contains database schema and data and storing it in Azure Storage or local tooling output. Export can be started from the portal, PowerShell, Azure CLI, SqlPackage, SSMS, or supported developer tools.
Azure SQL
fundamentals
5 commands
Aliases: database export, Azure SQL BACPAC export, SQL export, export database to BACPAC
Quick peek
Open full term page
Databases
complete
SQL database firewall rule
Microsoft Learn describes Azure SQL firewall rules as IP allow rules that must permit traffic before clients can reach a logical server or database. Server-level rules can be managed through Azure tools, while database-level rules are scoped to individual databases and managed with Transact-SQL.
Data platform
intermediate
5 commands
Aliases: Azure SQL firewall rule, SQL server firewall rule, database-level firewall rule, SQL IP firewall rule
Quick peek
Open full term page
Databases
complete
SQL database import
SQL database import is the Azure SQL workflow that rebuilds a database from a BACPAC file stored in Azure Storage or supplied through tooling.
Azure SQL
fundamentals
5 commands
Aliases: Azure SQL Database import, BACPAC import, SQL import, database import operation
Quick peek
Open full term page
Storage
complete
Storage account object replication
Microsoft Learn describes object replication for block blobs as asynchronous copying from a source storage account to a destination account. Policies and rules define the source container, destination container, and object selection, with blob versioning and change feed supporting replication behavior.
Storage accounts
advanced
5 commands
Aliases: blob object replication, Azure Storage object replication, OR policy, cross-account blob replication
Quick peek
Open full term page
Storage
complete
Storage account replication
Storage account replication is the background copy behavior behind a redundancy choice. It determines whether data is replicated only inside one datacenter, across availability zones, or to a paired region, and whether a secondary location can be read during normal operations.
Storage accounts
advanced
5 commands
Aliases: storage replication, storage account redundancy replication, account replication model, Azure Storage replication
Quick peek
Open full term page
Analytics
field-manual-complete
Lake database
A lake database in Azure Synapse Analytics combines database design, metadata, and storage layout for data stored in the lake, helping teams describe structure and query files through shared Spark and serverless SQL metadata without turning the data lake into a traditional database.
Analytics platform
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
verified
Database
A named store of application data, tables, indexes, and metadata.
Database
intermediate
2 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
learning-path-anchor
Data Lake storage account
A storage feature or access model in Data Lake Storage Gen2 that helps teams store, protect, move, and govern application or analytics data with clearer ownership, safety, and operational context.
Data Lake Storage Gen2
advanced
19 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Eventual consistency
Eventual consistency is the weakest Azure Cosmos DB consistency level, where reads can return a subset of writes and all writes become available eventually. Teams use it to favor low-latency, high-availability reads for workloads that can tolerate temporarily stale or out-of-order data. It is not strong consistency, session consistency, a conflict-resolution strategy, a cache setting, or permission to ignore user-facing correctness requirements. In production, confirm account consistency setting, client overrides, read region, write region, session tokens, replication latency, stale-read tolerance, conflict policy, and application workflows that read after writes before treating the design as healthy or ready for release.
Azure Cosmos DB
intermediate
6 commands
Aliases: eventual consistency level, Cosmos DB eventual consistency, eventually consistent reads
Quick peek
Open full term page
Migration
premium
Azure Migrate
Azure Migrate helps organizations discover, assess, plan, and migrate servers, databases, web apps, virtual desktops, and other workloads to Azure with reduced risk.
Migration planning
intermediate
5 commands
Aliases: Migrate, Azure Migrate hub, migration assessment
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
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