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 687 matching terms. Narrow the search to reduce the list.
Storage
field-manual-complete
Storage redundancy
Azure Storage redundancy stores multiple copies of data to protect against planned and unplanned events. Microsoft Learn describes options for replication within the primary region, geo-replication to a distant secondary region, and read access to replicated data. The choice balances cost, availability, durability, and recovery requirements for operations.
Storage resilience
Intermediate
5 commands
Aliases: Azure Storage redundancy, storage replication, storage account replication, storage redundancy option, storage SKU redundancy
Quick peek
Open full term page
Storage
complete
Storage account redundancy
Storage account redundancy describes how Azure Storage copies data within or across locations to protect against hardware, zone, or regional failure. Options such as LRS, ZRS, GRS, RA-GRS, GZRS, and RA-GZRS trade cost, durability scope, read availability, and recovery behavior.
Storage accounts
advanced
5 commands
Aliases: storage redundancy, storage replication SKU, storage account replication setting, Azure Storage redundancy
Quick peek
Open full term page
Storage
premium
Locally redundant storage
Microsoft Learn describes locally redundant storage as Azure Storage redundancy that replicates data within the primary region in a local storage scale unit. LRS is the lowest-cost redundancy option and provides high durability, but it does not protect against regional disasters.
Azure Storage
intermediate
10 commands
Aliases: LRS
Quick peek
Open full term page
Storage
premium
Zone-redundant storage
Zone-redundant storage (ZRS) is an Azure Storage redundancy option that copies data synchronously across three or more availability zones in the primary region. It keeps storage resources available for reads and writes if a zone becomes unavailable, while staying within the region for governance-sensitive workloads.
Azure Storage
intermediate
5 commands
Aliases: ZRS, ZRS storage, Azure Storage ZRS, zonal storage redundancy
Quick peek
Open full term page
Storage
premium
ZRS redundancy
ZRS redundancy is the storage-account redundancy setting that enables zone-redundant storage. It synchronously replicates data across availability zones in the primary Azure region, so blobs, files, queues, and tables can remain accessible during a zonal outage without relying on asynchronous secondary-region replication.
Storage accounts
fundamentals
5 commands
Aliases: Standard_ZRS, Premium_ZRS, ZRS SKU, zonal redundancy, zone redundant SKU
Quick peek
Open full term page
Storage
premium
Geo-redundant storage
Geo-redundant storage is an Azure Storage redundancy option that protects data by keeping primary-region replicas and asynchronously copying that data to a paired secondary region. Teams use it to reduce the chance that a regional outage destroys blob, file, queue, table, or Data Lake data that must survive a disaster. In daily Azure work, it shows up when engineers choose a storage account replication SKU, review disaster recovery requirements, compare GRS with RA-GRS or GZRS, or investigate why secondary-region reads are unavailable.
Storage redundancy
intermediate
4 commands
Aliases: GRS, Standard_GRS, read-access geo-redundant storage, RA-GRS
Quick peek
Open full term page
Storage
premium
Geo-zone-redundant storage
Geo-zone-redundant storage is an Azure Storage redundancy choice that combines zone redundancy in the primary region with asynchronous replication to a paired secondary region. Teams use it to protect data from zonal failures and regional disasters while keeping one storage account pattern for blobs, Data Lake paths, queues, tables, or files where supported. In daily Azure work, it shows up when engineers select Standard_GZRS or Standard_RAGZRS, compare ZRS with GRS, approve resilient storage standards, or investigate why an account is more expensive than LRS.
Storage redundancy
intermediate
4 commands
Aliases: GZRS, Standard_GZRS, read-access geo-zone-redundant storage, RA-GZRS
Quick peek
Open full term page
Storage
premium
GRS redundancy
GRS redundancy is an Azure Storage replication option that stores data in the primary region and asynchronously replicates it to a paired secondary region for regional disaster protection.
Storage accounts
intermediate
4 commands
Aliases: geo-redundant storage, Standard_GRS, GRS
Quick peek
Open full term page
Storage
premium
GZRS redundancy
GZRS redundancy is an Azure Storage replication option that synchronously replicates data across availability zones in the primary region and asynchronously replicates it to a secondary region.
Storage accounts
intermediate
4 commands
Aliases: geo-zone-redundant storage, Standard_GZRS, GZRS
Quick peek
Open full term page
Storage
premium
LRS redundancy
LRS redundancy, or locally redundant storage, keeps three copies of data inside one Azure datacenter in the primary region. It is the lowest-cost storage redundancy option and protects against local hardware failures, but it does not protect against zone-wide or regional outages.
Storage accounts
fundamentals
4 commands
Aliases: Standard_LRS, locally redundant storage, locally-redundant storage
Quick peek
Open full term page
Storage
verified
Read-access geo-redundant storage
Read-access geo-redundant storage, or RA-GRS, replicates storage account data synchronously within the primary region and asynchronously to a paired secondary region, while exposing a secondary read endpoint. It lets applications read replicated data if the primary region becomes unavailable or secondary-read patterns are intentionally designed.
Storage redundancy
intermediate
10 commands
Aliases: RA-GRS, Standard_RAGRS, read-access GRS, read-access geo redundant storage, secondary read endpoint
Quick peek
Open full term page
Storage
verified
Read-access geo-zone-redundant storage
Read-access geo-zone-redundant storage, or RA-GZRS, combines zone redundancy in the primary region, geo-replication to a secondary region, and a secondary read endpoint. It protects against zonal failures while preserving read access to replicated data when the primary region or application path is impaired.
Storage redundancy
intermediate
5 commands
Aliases: RA-GZRS, Standard_RAGZRS, read-access GZRS, read-access geo-zone redundant storage, zone and geo read access
Quick peek
Open full term page
Storage
complete
Storage account SKU
A storage account SKU is the account’s selected service tier and redundancy option, such as Standard_LRS, Standard_ZRS, Standard_GRS, or Premium_LRS. It influences durability, availability, performance characteristics, regional support, and pricing for the account. Engineers review it before creation, migration, and cost optimization.
Storage accounts
intermediate
5 commands
Aliases: Storage account SKU, storage account sku, storage-account-sku, storage SKU, storage account tier, storage redundancy SKU
Quick peek
Open full term page
Databases
premium
Azure SQL logical server
An Azure SQL logical server is a logical administrative construct for Azure SQL Database and related SQL resources. Microsoft Learn describes it as the central point for managing a collection of databases, including logins, firewall rules, auditing, threat detection policies, and failover groups.
Azure SQL Database
fundamentals
16 commands
Aliases: No aliases yet
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 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
Automatic tuning
Automatic tuning is Azure SQL Database’s built-in assistant for common query performance problems. In plain terms, Azure watches how queries behave and can recommend or apply changes that improve performance, such as index adjustments or plan correction. It is useful when workloads change faster than people can manually tune every query..
Azure SQL
intermediate
4 commands
Aliases: Azure SQL automatic tuning, SQL automatic tuning, automatic plan correction, automatic index tuning
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
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
Long-term backup retention
Long-term backup retention is the Azure SQL feature for keeping selected automated full database backups in redundant Azure Blob storage for months or years, up to supported policy limits, so databases can be restored for compliance, audit, and recovery needs.
Azure SQL
intermediate
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
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
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
Databases
verified
VNet injection for SQL MI
VNet injection for SQL MI means deploying Azure SQL Managed Instance inside a dedicated Azure virtual network subnet that is delegated to Microsoft.Sql/managedInstances, with required network rules so the managed instance has private connectivity and service management access.
Azure SQL Managed Instance
intermediate
6 commands
Aliases: SQL MI VNet injection, SQL Managed Instance subnet integration, SQL MI delegated subnet, managed instance VNet placement
Quick peek
Open full term page
Databases
verified
Query Store
Query Store is a built-in history recorder for SQL query behavior.
Azure SQL
intermediate
5 commands
Aliases: No aliases yet
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 Agent on Managed Instance
Microsoft Learn explains that SQL Server Agent executes SQL Agent jobs for task automation in Azure SQL Managed Instance. A job is a specified series of T-SQL scripts against a database, used to run administrative tasks one or more times and monitor success or failure.
Azure SQL Managed Instance
intermediate
5 commands
Aliases: SQL Agent on Managed Instance, sql agent on managed instance, sql-agent-on-managed-instance
Quick peek
Open full term page
Databases
complete
SQL auditing
Microsoft Learn explains that auditing for Azure SQL Database and Azure Synapse Analytics tracks database events and writes them to an audit log in an Azure storage account, Log Analytics workspace, or Event Hubs. It helps maintain regulatory compliance and understand database activity.
Azure SQL
intermediate
5 commands
Aliases: SQL auditing, sql auditing, sql-auditing
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
Databases
field-manual-complete
vCore model
The vCore model is the Azure SQL purchasing model that separates compute and storage decisions for clearer sizing and cost planning.
Azure SQL
intermediate
4 commands
Aliases: vCore purchasing model, Azure SQL vCore model, vCore-based purchasing model, SQL vCore model
Quick peek
Open full term page
Databases
top-250-pre130-priority-upgraded
Periodic backup
Periodic backup is the scheduled backup option for Azure Cosmos DB.
Cosmos DB
intermediate
4 commands
Aliases: Cosmos DB periodic backup, periodic backup mode, scheduled Cosmos DB backup, backup interval, backup retention period, Azure Cosmos DB periodic backup, periodic backup policy
Quick peek
Open full term page
Databases
premium field-manual
Managed instance link
Managed Instance link is a SQL Managed Instance feature that links SQL Server to Managed Instance for migration, replication, or hybrid continuity scenarios. Teams use it when teams need to move SQL Server databases to Azure with controlled replication and cutover planning. In plain English, it gives operators a named control for migration evidence, replication visibility, and lower-risk transition from on-premises SQL Server 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 link, Azure SQL Managed Instance
Quick peek
Open full term page
Databases
premium field-manual
Managed instance virtual cluster
Managed Instance virtual cluster is an Azure-managed infrastructure grouping that hosts one or more SQL Managed Instances inside a subnet. Teams use it when teams deploy, scale, move, or delete managed instances and need to understand the hidden infrastructure boundary. In plain English, it gives operators a named control for clearer expectations for provisioning time, subnet planning, instance placement, and cleanup behavior 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 virtual cluster, Azure SQL Managed Instance
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
Storage
command-rich
Primary storage region
The primary storage region is the home region for an Azure Storage account. When an application writes blobs, files, queues, or tables under normal conditions, it writes to the primary region. Microsoft Learn anchors this term in Data redundancy - Azure Storage, but this field-manual definition is intentionally wider than an older short glossary entry because the page must teach what to inspect, what can break, who owns the decision, and which evidence proves the Azure environment is behaving as intended. In field use, start with the technical boundary: Technically.
Storage platform
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
command-rich
Secondary storage region
The secondary storage region is the other region involved when an Azure Storage account uses geo-redundant options such as GRS or GZRS. Under normal conditions, applications write to the primary region, and Azure asynchronously copies data to the secondary region. Microsoft Learn anchors this term in Data redundancy - Azure Storage, but this field-manual definition is intentionally wider than an older short glossary entry because the page must teach what to inspect, what can break, who owns the decision, and which evidence proves the Azure environment is behaving as intended..
Storage platform
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
General-purpose v2 storage account
General-purpose v2 storage account is an Azure Storage account resource using the StorageV2 kind to host common storage services under one managed namespace. Teams use it to provide durable storage for applications while centralizing endpoints, redundancy, encryption, lifecycle management, networking, monitoring, and access control. In daily Azure work, it appears when engineers provision blob containers, file shares, queues, tables, static websites, backups, application artifacts, or Data Lake Gen2-enabled storage in a landing zone. It is not a specific blob container, an unlimited performance guarantee, an identity provider, or a safe design unless access, networking, and data protection are configured.
Storage accounts
beginner
5 commands
Aliases: Azure general-purpose v2 storage account, GPv2 storage account, StorageV2 storage account
Quick peek
Open full term page
Storage
premium
Infrastructure encryption for storage
Infrastructure encryption for storage controls how Azure Storage applies optional double encryption to blobs, files, queues, or tables depending on account and scope configuration. Teams see it in storage account creation, encryption blade. It is not blob immutability, soft delete, encryption in transit, customer-managed key rotation, or disabling shared key authorization; confusing them can create storage accounts that cannot meet compliance, rebuild-only remediation. 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 Storage Security
Intermediate
5 commands
Aliases: storage infrastructure encryption, storage account double encryption, require infrastructure encryption, double encryption for Azure Storage
Quick peek
Open full term page
Databases
premium
Azure SQL zone redundancy
Azure SQL zone redundancy places database replicas or storage across multiple availability zones in a supported region to improve resilience against datacenter-level failures.
Azure SQL Database
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
NFS 3.0 for Blob Storage
NFS 3.0 for Blob Storage means an Azure Blob Storage protocol option that lets Linux clients mount blob containers through NFS version 3. You see it when teams connect analytics jobs, HPC workloads, migration tools, or Linux applications that expect mounted file paths. Think of it as a storage protocol choice with account, namespace, and network requirements. 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.
Blob Storage
advanced
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
learning-path-anchor
Table Storage
Table Storage is Azure Storage for simple structured NoSQL records. You create tables, store entities, and identify each entity with a PartitionKey and RowKey. It is useful when the data is large, sparse, inexpensive to keep, and usually accessed by known keys. It is not a relational database, search engine, or analytics warehouse. The best fit is operational data that can be denormalized, read directly, updated independently, and kept cheap without requiring joins, stored procedures, or secondary indexes.
Table Storage
fundamentals
5 commands
Aliases: Azure Table Storage, Storage Tables, Azure Storage Tables, Azure Tables storage
Quick peek
Open full term page
Storage
premium
Blob storage account
A Blob storage account is the Azure Storage account that provides the namespace, security boundary, network configuration, redundancy, and service endpoint for Blob data.
Storage accounts
advanced
3 commands
Aliases: Blob storage account, storage account, blob storage account
Quick peek
Open full term page
Storage
complete
Storage account kind
A storage feature or access model in Storage accounts that helps teams store, protect, move, and govern application or analytics data with clearer ownership, safety, and operational context.
Storage accounts
advanced
10 commands
Aliases: storage account type, account kind, Azure Storage account type, StorageV2 kind
Quick peek
Open full term page
Storage
complete
Storage account failover
Storage account failover is documented by Microsoft as part of the Storage accounts area in Azure.
Storage accounts
advanced
8 commands
Aliases: account failover, storage failover, customer-managed failover, planned storage failover
Quick peek
Open full term page
Storage
field-manual-complete
Blob Storage
Blob Storage is Azure object storage for massive amounts of unstructured data such as documents, images, video, backups, logs, and application files.
Storage
advanced
5 commands
Aliases: Blob Storage, blob-storage, blob, blob-container, blob-access-tier, blob-soft-delete, blob-versioning, storage-account, account-sas, private-endpoint-for-storage, azure-files, data-lake-storage-gen2, queue-storage
Quick peek
Open full term page
Storage
field-manual-complete
Premium storage account
A premium storage account is not just a normal storage account with a fancy name.
Storage accounts
advanced
5 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
Storage
verified
RA-GZRS redundancy
RA-GZRS combines zone-redundant storage in the primary region with asynchronous geo-replication to a secondary region, plus read access to the secondary endpoint. It helps storage workloads remain readable during regional problems while also protecting against zone failures in the primary region.
Storage accounts
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
complete
Standard storage account
Microsoft Learn describes a standard general-purpose v2 storage account as the recommended account type for most Azure Storage scenarios. It provides a namespace for blobs, Azure Files, queues, tables, and Data Lake Storage capabilities, with standard redundancy choices such as LRS, ZRS, GRS, RA-GRS, GZRS, and RA-GZRS.
Storage accounts
intermediate
5 commands
Aliases: standard-storage-account, Standard storage account, standard general-purpose v2 storage account, standard GPv2 storage account, Azure Storage standard account, StorageV2 standard account
Quick peek
Open full term page
Storage
complete
Static website hosting for storage
Microsoft Learn explains that Azure Storage can host static web content from a general-purpose v2 or BlockBlobStorage account. Enabling the feature creates or uses the $web container, where HTML, CSS, JavaScript, and images are served through the account website endpoint.
Storage account
intermediate
5 commands
Aliases: static-website-hosting-for-storage, Static website hosting for storage, Azure Storage static website hosting, storage account static website, Blob service static website, web endpoint for storage
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