Search Azure terms

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

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

Storage premium Azure Site Recovery vault An Azure Site Recovery vault is a Recovery Services vault used to manage replication, failover, and recovery metadata for Site Recovery. Backup and recovery intermediate 5 commands Aliases: ASR vault, Azure Site Recovery vault, Recovery Services vault, Site Recovery Recovery Services vault 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 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

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

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

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

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

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

Integration premium Event Hubs dedicated cluster An Event Hubs dedicated cluster is a single-tenant Dedicated tier Event Hubs deployment that provides reserved capacity for enterprise-scale streaming workloads. Teams use it to run high-volume, low-latency event streaming workloads with isolated capacity instead of sharing a multitenant namespace tier. It is not a single event hub entity, a consumer group, a Kafka cluster you manage yourself, or a small development namespace. 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: Dedicated Event Hubs cluster, Event Hubs Dedicated tier cluster, Event Hubs cluster Quick peek Open full term page

Integration premium Event Hubs namespace An Event Hubs namespace is the management container for one or more event hubs and controls shared settings such as network access, SKU, capacity, and authorization. Teams use it to group event hubs under one managed Azure resource boundary for scale, networking, authorization, monitoring, and operational ownership. It is not an individual event hub stream, a consumer group, a storage account, or a generic directory folder. 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: Azure Event Hubs namespace, namespace, Event Hubs resource container Quick peek Open full term page

Integration premium Event Hubs private endpoint An Event Hubs private endpoint is a Private Link network interface that lets clients reach an Event Hubs namespace through a private IP address in a virtual network. Teams use it to keep Event Hubs traffic on private network paths and restrict namespace access from public internet routes. It is not an outbound connection from Event Hubs into your subnet, a substitute for authentication, or a guarantee that every Azure service can still reach the namespace. Event Hubs intermediate 5 commands Aliases: Private Link for Event Hubs, Event Hubs Private Link, private endpoint connection Quick peek Open full term page

Management and Governance premium Policy notScope Policy notScope is the list of places where an Azure Policy assignment should not apply. Think of it as a surgical exclusion inside a larger assignment. A governance team might assign a location policy to an entire management group, then exclude a disaster recovery resource group or migration subscription that needs temporary freedom. The assignment still exists at the parent scope, but Azure Policy skips the excluded child scope during evaluation, so those resources do not appear as non-compliant for that assignment. Azure Policy intermediate 5 commands Aliases: notScopes, Policy notScope, policy-not-scope Quick peek Open full term page

Management and Governance premium Quota Microsoft Learn describes Azure quotas as adjustable limits applied to Azure resources and services within a subscription, region, or provider scope. Each subscription receives default quota values, and teams can review usage or request increases before planned scale, migration, or recovery work consumes available capacity. Capacity management fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Server endpoint A server endpoint in Azure File Sync represents a registered Windows Server path that participates in a sync group. It connects local files to an Azure file share through a cloud endpoint and can use settings such as cloud tiering, free-space policy, and offline sync behavior. Azure File Sync intermediate 5 commands Aliases: Azure File Sync server endpoint, file sync server endpoint, storage sync server endpoint, sync group server endpoint Quick peek Open full term page

Compute premium Availability zone strategy An availability zone strategy answers a practical question: if part of a region has a problem, what keeps the workload alive? Azure availability zones are separate groups of datacenters inside a supported region, and they are designed with independent power, cooling, and networking. That does not mean every resource automatically becomes zone-resilient. Microsoft Learn anchors this term in What are Azure availability zones?, 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. Operational hygiene fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Azure File Sync Azure File Sync syncs Azure file shares with Windows Server file servers so users keep familiar local access while data is centralized in Azure Files. It helps infrastructure teams modernize branch and data center file services without forcing every user and application to change paths on day one. You see it when Windows file server migrations, branch caching, cloud tiering, disaster recovery staging, or phased moves to Azure Files. 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. Hybrid file services intermediate 4 commands Aliases: File Sync, Storage Sync Service 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

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

Management and Governance premium Bicep conditional resource A Bicep conditional resource is a resource or module declaration that deploys only when its if expression evaluates to true. Bicep fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Cosmos DB consistency level A Cosmos DB consistency level defines the read guarantee between replicated writes and later reads. Microsoft Learn describes five levels—strong, bounded staleness, session, consistent prefix, and eventual—so teams can choose the right trade-off among latency, availability, throughput, and application correctness. Azure Cosmos DB intermediate 4 commands Aliases: Azure Cosmos DB consistency level, consistency model, session consistency 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

Storage premium File share soft delete File share soft delete is a data protection setting that retains deleted Azure file shares for a configured recovery period before permanent deletion in Azure. Azure Files intermediate 4 commands Aliases: File share soft delete, file share soft delete 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

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

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

Databases premium MySQL high availability MySQL high availability means a MySQL Flexible Server configuration that keeps standby capacity available to reduce downtime during maintenance or failures. You see it when teams protect production databases for commerce, healthcare, finance, SaaS, and internal systems from planned or unexpected outages. Think of it as database resilience built into the server, not a complete disaster-recovery plan. 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

Databases premium MySQL zone-redundant HA MySQL zone-redundant HA means a MySQL Flexible Server high-availability option that places standby capacity in another availability zone for stronger zonal resilience. You see it when teams protect production databases from zone-level failures while accepting the design and latency tradeoffs. Think of it as cross-zone server resilience, not a full multi-region disaster-recovery plan. 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

Management and Governance premium Paired region strategy A paired region strategy means you do not choose a second Azure region by guesswork. You check whether the primary region has a Microsoft-defined pair, whether the service you are using actually relies on that pair, and whether your workload still needs its own failover design. Microsoft Learn anchors this term in Azure region pairs and nonpaired regions, 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. Management scopes fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance premium Region pair A region pair is Azure's planned partner region for resilience within a geography. It helps with disaster recovery thinking, platform update sequencing, and data residency planning, but you still need to confirm whether each service actually supports paired-region replication. Management scopes fundamentals 4 commands Aliases: No aliases yet 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

Storage complete Storage account endpoint Storage account endpoint is documented by Microsoft as part of the Storage accounts area in Azure. Storage accounts fundamentals 8 commands Aliases: storage endpoint, blob endpoint, dfs endpoint, storage service URL 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 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 read replica A PostgreSQL read replica is a second flexible server that follows a primary PostgreSQL server and accepts read-only traffic. Writes still go to the primary. The replica is useful when reporting, analytics, search indexing, or distant users are putting too much read pressure on the main database. Because replication is asynchronous, the replica can lag behind current writes. That lag matters. Learners should remember that a read replica is for read scale, regional reach, and recovery options, not for splitting ordinary writes across two active databases. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL replica, PostgreSQL read-only replica, Azure PostgreSQL read replica, Read replica for PostgreSQL flexible server Quick peek Open full term page

Management and Governance verified Quota increase request A quota increase request asks Azure to raise a service limit for a subscription, provider, region, or resource family. Teams use it when current usage or planned deployment capacity exceeds available quota and Azure must approve or apply a higher limit. Azure Quotas intermediate 5 commands Aliases: Azure quota request, quota limit increase, service limit increase 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

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

Management and Governance field-manual-complete Region Region is the Azure geography you choose when you deploy a resource, such as East US, Sweden Central, or West Europe. Azure geography and resiliency fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance verified Resource delete protection Resource delete protection uses Azure management locks, usually CanNotDelete, to stop critical resources or resource groups from being deleted by ordinary control-plane operations. Management locks fundamentals 5 commands Aliases: Azure delete protection, management lock delete protection, CanNotDelete lock, delete lock, protected Azure resource Quick peek Open full term page

Management and Governance verified Resource mover Azure Resource Mover helps move supported Azure resources to another region through a controlled workflow. Instead of manually rebuilding every VM, disk, network, and dependency, you create a move collection, add resources, resolve dependencies, prepare the target, initiate the move, and then commit or discard. It is useful when a workload must leave one region for compliance, latency, capacity, feature availability, or disaster-recovery readiness. It does not magically move every service, so support matrices and dependency validation matter. Azure Resource Manager fundamentals 5 commands Aliases: Azure Resource Mover, Move collection workflow Quick peek Open full term page

Management and Governance field-manual-complete Service limit A service limit is Azure’s boundary for how much of something you can use or create. It might be a number of cores, public IP addresses, storage accounts, database throughput, API requests, or service-specific resources. Some limits protect the platform, some control regional capacity, and some reflect your subscription or SKU. Operators care because a. Capacity management fundamentals 5 commands Aliases: No aliases yet 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