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 1,985 matching terms. Narrow the search to reduce the list.
Storage
premium
Backup job
A backup job is an Azure Backup operation record for work such as protecting, backing up, restoring, stopping protection, or validating recovery activity in a vault.
Backup and recovery
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Backup retention
Backup retention is the period or rule set that determines how long recovery points are kept before Azure Backup expires or prunes them according to policy.
Backup and restore
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Hyperscale
Hyperscale is an Azure SQL Database service tier built for large databases, fast scale, high availability, and separated compute and storage architecture.
Azure SQL
intermediate
4 commands
Aliases: Azure SQL Hyperscale, hyperscale, Hyperscale, Hyperscale service tier
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
Backup / point-in-time restore
Backup point-in-time restore lets Azure database services restore a protected database or server to a specific earlier timestamp within the configured backup retention period.
Database continuity
advanced
4 commands
Aliases: PITR, point in time restore, point-in-time restore
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
Web
premium
App Service backup
An App Service feature for creating on-demand or scheduled backups of app content and supported configuration, with restore to an app or slot. It helps learners understand where the concept appears in Azure operations and what to verify before changing it.
App Service
intermediate
5 commands
Aliases: app service backup, backup
Quick peek
Open full term page
Web
premium
App Service restore
App Service restore is recovering App Service content and supported configuration from an app backup, usually by overwriting an app or restoring into another app or deployment slot. Use it to reason about App Service behavior, validate configuration with CLI, and prevent hidden production impact from networking, scaling, recovery, security, or observability changes.
App Service Recovery
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Azure SQL automated backup
Azure SQL automated backup automatically protects databases and supports point-in-time restore using service-managed backup chains.
Azure SQL Database
fundamentals
5 commands
Aliases: Azure SQL automated backup, Azure SQL automatic backups, SQL automated backups, point-in-time restore backups
Quick peek
Open full term page
Databases
premium
Azure SQL geo-restore
Azure SQL geo-restore uses geo-replicated backups to restore a database to any logical server in any Azure region when primary-region access is unavailable.
Azure SQL Database
fundamentals
5 commands
Aliases: Azure SQL geo-restore, SQL geo restore, geo-replicated backup restore, geo-restore, regional backup restore
Quick peek
Open full term page
Storage
premium
Backup item
A backup item is a protected data source or backup instance in Azure Backup that is associated with a vault, policy, retention settings, and recoverable restore points.
Backup and recovery
intermediate
5 commands
Aliases: No aliases yet
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
Point-in-time restore
Point-in-time restore means choosing a time before something went wrong and restoring a database from backup history to that moment. It is not a magic undo button for every application issue; it usually creates a new database or restored instance that teams must verify, reconnect, or copy from. Operators use it after accidental deletes, bad migrations, data corruption, or failed releases. The important parts are the retention window, the restore target, the timestamp, and the validation work after restore.
Azure SQL
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
PostgreSQL backup retention
Azure Database for PostgreSQL automatically backs up flexible servers and retains the files and transaction logs for a configured window. The retention period defines how far back point-in-time restore can recover, with seven days as the default and up to thirty-five days configurable.
PostgreSQL flexible server
fundamentals
5 commands
Aliases: Azure PostgreSQL backup retention, Flexible Server backup retention, PostgreSQL PITR retention
Quick peek
Open full term page
Storage
premium
Azure Files backup
Azure Files backup protects Azure file shares using Azure Backup policies, recovery points, snapshots, and supported vaulted backup options. It helps backup and platform teams recover shared file data after accidental deletion, ransomware, or operator mistakes without managing separate backup servers or unreviewed snapshot scripts. You see it when business file shares need retention, recovery testing, policy enforcement, ransomware recovery, or evidence for data protection audits. It still needs ownership, network design, monitoring, and recovery planning. Operators need repeatable evidence for deployment, protection, troubleshooting, and reviews, not screenshots or tribal knowledge.
Backup and recovery
intermediate
4 commands
Aliases: Azure file share backup, Azure Backup for Azure Files
Quick peek
Open full term page
Databases
premium
Cosmos DB backup policy
Account-level Cosmos DB setting that controls backup mode, restore behavior, retention expectations, and recovery options for databases and containers.
Azure Cosmos DB
intermediate
4 commands
Aliases: Azure Cosmos DB backup policy, Cosmos DB periodic backup, Cosmos DB continuous backup policy
Quick peek
Open full term page
Databases
premium
Cosmos DB point-in-time restore
Cosmos DB point-in-time restore means the ability to restore supported Cosmos DB resources to a selected timestamp when continuous backup is enabled 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 recovering from bad writes, accidental deletes, corruption events, or deployment mistakes without guessing which backup to use. 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
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
premium
Cross-region restore
an Azure Backup capability that lets teams restore protected backup data into the paired secondary region when the vault is configured for it.
Backup and recovery
intermediate
4 commands
Aliases: Azure Backup Cross Region Restore, CRR, secondary region restore
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
MySQL backup retention
MySQL backup retention means the configured recovery window for automated backups on Azure Database for MySQL Flexible Server. You see it when teams decide how long production database backups must remain available for restore, compliance, and incident response. Think of it as a recovery promise measured in days, not a paperwork checkbox. 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
Databases
premium
MySQL point-in-time restore
MySQL point-in-time restore means a recovery operation that creates a new MySQL Flexible Server from backups at a selected time within the retention window. You see it when teams recover from accidental deletes, failed migrations, data corruption, ransomware impact, or bad application releases. Think of it as a new-server recovery workflow, not an undo button on the original database. 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
Storage
verified
Restore point
Microsoft Learn describes a VM restore point as an Azure resource that stores VM configuration and point-in-time snapshots of attached managed disks. Restore points are kept in restore point collections and can be application-consistent or crash-consistent, depending on workload and operating system support.
Backup and recovery
intermediate
7 commands
Aliases: VM restore point, virtual machine restore point, disk restore point, restore point collection, pre-change restore point
Quick peek
Open full term page
Databases
field-manual-complete
PostgreSQL point-in-time restore
PostgreSQL point-in-time restore means bringing a flexible server back to what it looked like at a specific earlier time, but Azure does this by creating a new server. It is used after accidental deletes, bad deployments, data corruption, or to clone production for validation. The restore must be inside the server’s backup retention period. It is not a single-table undo button and it does not overwrite production. After the new server exists, teams compare data, redirect applications, export recovered rows, or keep it for testing.
PostgreSQL flexible server
fundamentals
5 commands
Aliases: PostgreSQL PITR, PostgreSQL restore point, flexible server point-in-time restore
Quick peek
Open full term page
Management and Governance
top-250-pre130-priority-upgraded
Instant restore
Instant restore controls how quickly Azure Backup can restore VM disks or files by keeping recent snapshots close to the protected workload. Teams see it in recovery services vaults, vm backup policies. It is not point-in-time restore for databases, cross-region restore, soft delete, backup retention alone, or an unmanaged manual snapshot; confusing them can create slow recovery, unexpected snapshot storage cost. 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 Backup
Intermediate
5 commands
Aliases: Azure Backup instant restore, instant recovery snapshot, VM instant restore, instant recovery point, Instant restore
Quick peek
Open full term page
Storage
complete
Soft delete for backup
Microsoft Learn describes soft delete for Azure Backup as a protection that keeps deleted backup data in a soft-deleted state for a configured retention period. Enhanced soft delete can extend retention and make the setting always on, helping recover from accidental or malicious deletions.
Backup and recovery
intermediate
5 commands
Aliases: Azure Backup soft delete, backup soft delete, enhanced soft delete, soft-deleted backup data
Quick peek
Open full term page
Databases
top-250-pre130-priority-upgraded
Continuous backup
Continuous backup is the Azure Cosmos DB backup mode that keeps restore points available over time instead of relying only on periodic snapshots.
Azure Cosmos DB
intermediate
4 commands
Aliases: Azure Cosmos DB continuous backup, Cosmos DB point-in-time restore, continuous backup mode
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
Azure SQL point-in-time restore
A database capability or setting in Azure SQL Database that helps teams store, query, scale, secure, and recover application data with clearer ownership, safety, and operational context.
Azure SQL Database
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Migration
premium
Backup vault
A Backup vault is an Azure Backup storage and management entity that stores backups, recovery points, and backup policies for supported newer workloads.
Backup and recovery
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Bicep restore
Bicep restore downloads external modules referenced by a Bicep file into the local module cache before build or deployment.
Bicep
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
complete
SQL managed instance backup retention
Microsoft Learn explains that automated backups for Azure SQL Managed Instance let teams restore a managed database to a specific point in time within the configured retention period, up to 35 days, while long-term retention policies can preserve selected backups for years when compliance requires it.
SQL Managed Instance
intermediate
5 commands
Aliases: SQL MI backup retention, managed instance PITR retention, MI short-term retention, SQL MI restore window
Quick peek
Open full term page
Integration
verified
Receive and delete
Receive and delete is an Azure Service Bus receive mode where the broker considers a message settled as soon as it sends the message to the receiver. If transfer or processing fails afterward, the message is lost instead of being redelivered.
Azure Service Bus
intermediate
5 commands
Aliases: ReceiveAndDelete, receive-and-delete mode, destructive read, at-most-once receive
Quick peek
Open full term page
Integration
verified
Receive-and-delete mode
A integration pattern or service capability in Messaging that helps teams connect services reliably without tightly coupling every component with clearer ownership, safety, and operational context.
Messaging
fundamentals
5 commands
Aliases: No aliases yet
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
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
Flexible server
A flexible server is the Azure Database deployment model for managed PostgreSQL or MySQL servers with configurable compute, storage, availability, maintenance, backup, and networking options. Teams use it to host managed relational databases with more control over maintenance windows, compute tiers, backup retention, high availability, private networking, stop-start behavior, and performance settings. It is not a self-managed VM database, a single-server compatibility promise, a free unlimited database tier, or proof that schema design, indexes, failover, and application connection pooling are correct.
Azure managed databases
intermediate
6 commands
Aliases: Azure Database flexible server, PostgreSQL flexible server, MySQL flexible server, managed flexible database server
Quick peek
Open full term page
Databases
premium
Azure SQL hyperscale
Azure SQL Database Hyperscale is a service tier built for very large databases, fast storage scaling, rapid backups and restores, and high throughput. Microsoft Learn describes its distinct architecture, including separated compute and storage, page servers, log service, and optional replicas.
Azure SQL Database
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Analytics
premium
Delta time travel
Delta time travel is the ability to query or restore earlier versions of a Delta table by using the table history stored in the Delta transaction log.
Delta Lake
intermediate
5 commands
Aliases: Delta Lake time travel, table version query, query previous Delta version, restore Delta table version
Quick peek
Open full term page
Integration
premium
Event Hubs geo-disaster recovery
Event Hubs geo-disaster recovery pairs namespaces and uses an alias so applications can fail over namespace metadata access to a secondary namespace during a regional disaster. Teams use it to keep a stable connection endpoint for disaster recovery planning when an Event Hubs namespace must move to a paired secondary region. It is not automatic failover, a backup of retained event data in standard metadata Geo-DR, or a replacement for application-level replay and regional processing design.
Event Hubs
intermediate
5 commands
Aliases: Event Hubs Geo-DR, Event Hubs disaster recovery alias, Geo-recovery alias
Quick peek
Open full term page
Storage
premium
Hot access tier
The hot access tier is an Azure Blob Storage tier optimized for data that is actively used and read frequently.
Azure Blob Storage
fundamentals
5 commands
Aliases: Hot access tier, hot access tier
Quick peek
Open full term page
Storage
premium
Share snapshot
A share snapshot is a point-in-time copy of an Azure file share. Azure Files supports snapshots for SMB and NFS shares, letting administrators view, restore, or copy previous versions of files while existing snapshots remain until explicitly deleted or managed by policy.
Files, queues, and tables
fundamentals
5 commands
Aliases: Azure Files share snapshot, file share snapshot, share snapshot, Azure file share point-in-time copy, snapshot share
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
File share snapshot
File share snapshot is a point-in-time copy of an Azure Files share that can help recover earlier versions of files and directories in Azure.
Azure Files
intermediate
4 commands
Aliases: File share snapshot, file share snapshot
Quick peek
Open full term page
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
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
MySQL major version upgrade
MySQL major version upgrade means the process of moving Azure Database for MySQL Flexible Server to a newer major MySQL version. You see it when teams modernize database engines, gain feature support, reduce technical debt, or prepare for support lifecycle changes. Think of it as a database-engine migration that needs testing, not a routine patch. 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
intermediate
4 commands
Aliases: No aliases yet
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
Storage
premium
Blob versioning
Blob versioning is an Azure Storage data protection feature that automatically keeps previous versions of block blobs when they are modified or deleted. Microsoft Learn explains that version IDs let teams list, read, restore, or manage prior blob states alongside soft delete and lifecycle policies.
Blob Storage
fundamentals
3 commands
Aliases: Blob versioning, versioning, blob versioning
Quick peek
Open full term page
Storage
premium
Container soft delete
the Blob Storage protection feature that lets teams restore deleted containers during a configured retention window
Blob Storage protection
intermediate
3 commands
Aliases: No aliases yet
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