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 729 matching terms. Narrow the search to reduce the list.
Storage
field-manual-complete
Storage lifecycle management
Policy-based automation that tiers or deletes Azure Blob Storage data as it ages or changes use.
Storage lifecycle
intermediate
5 commands
Aliases: Azure Blob lifecycle management, storage account lifecycle policy, blob lifecycle management policy, storage retention tiering policy
Quick peek
Open full term page
Storage
field-manual-complete
Storage lifecycle rule
One rule in a Blob Storage lifecycle policy that filters blobs and applies tiering or deletion actions.
Storage lifecycle
intermediate
5 commands
Aliases: blob lifecycle rule, Azure Storage lifecycle rule, lifecycle policy rule, storage tiering rule, lifecycle management policy rule
Quick peek
Open full term page
Storage
complete
Storage account lifecycle management
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
5 commands
Aliases: blob lifecycle management, storage lifecycle policy, Azure Storage management policy, blob tiering policy
Quick peek
Open full term page
Databases
premium
MySQL storage autogrow
MySQL storage autogrow means a MySQL Flexible Server setting that automatically increases storage when used capacity approaches the configured limit. You see it when teams protect databases from running out of storage during growth, imports, reporting, migrations, or seasonal demand. Think of it as automatic storage expansion, not automatic cost or performance optimization. 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
advanced
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
Blob lifecycle rule
A blob lifecycle rule is one rule inside a lifecycle management policy that filters blobs and applies actions such as tiering or deletion after defined conditions are met.
Blob Storage
intermediate
3 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
field-manual-complete
Lifecycle management rule
Microsoft Learn describes lifecycle policy rules as named definitions with filters and actions. A rule selects blobs by type, prefix, or index tags, then transitions or deletes current versions, previous versions, or snapshots according to age and lifecycle conditions.
Azure Storage
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
complete
Storage account soft delete
Storage account soft delete is a data protection configuration that keeps deleted blobs, containers, or shares recoverable for a defined retention period. It helps teams recover from accidental deletion or overwrite without immediately restoring from backup. Retention days determine how long recovery remains possible.
Storage accounts
intermediate
5 commands
Aliases: Storage account soft delete, storage account soft delete, storage-account-soft-delete, storage soft delete, blob soft delete, container soft delete
Quick peek
Open full term page
Storage
field-manual-complete
Lifecycle management
Microsoft Learn describes Azure Blob Storage lifecycle management as policies with automated rules for moving blobs between hot, cool, cold, and archive tiers or deleting data at the end of its lifecycle. Rules help manage cost as access patterns change.
Blob Storage
fundamentals
2 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
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
Analytics
field-manual-complete
Kusto retention policy
A Kusto retention policy controls when data is automatically removed from Azure Data Explorer or Fabric tables and materialized views. It is commonly used for continuously ingested data whose usefulness is age-based, and can be configured at database, table, or view scope.
Azure Data Explorer
intermediate
6 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
field-manual-complete
Last access time tracking
Last access time tracking for Azure Blob Storage records when a blob was last read or written so lifecycle policies can use access age. Microsoft Learn describes the lastAccessTime condition, daily update behavior, billing considerations, and limitations when moving or deleting data based on recent access.
Storage platform
intermediate
6 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
field-manual-complete
Uncommitted block
An uncommitted block is a block uploaded to an Azure block blob but not yet included in a committed block list. It is temporary upload state: the bytes are associated with the blob name, but they do not become readable blob content until the client commits them.
Blob Storage
intermediate
5 commands
Aliases: staged block, uncommitted blob block, Azure Blob uncommitted block, Put Block staging
Quick peek
Open full term page
Storage
complete
Soft delete
Microsoft Learn describes Azure Storage soft delete as protection that retains deleted or overwritten data for a configured retention period. During that period, eligible blobs, containers, file shares, versions, snapshots, or metadata can be restored before permanent deletion occurs after retention expires.
Data protection
fundamentals
5 commands
Aliases: storage soft delete, blob soft delete, container soft delete, recoverable delete
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
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
Immutable storage
Immutable storage is Azure Blob Storage configured to protect data in a write-once, read-many state so it cannot be modified or deleted during a retention period.
Data protection
intermediate
5 commands
Aliases: Immutable storage, immutable storage, immutable-storage
Quick peek
Open full term page
Storage
premium
SFTP for Azure Blob Storage
SFTP for Azure Blob Storage lets clients connect to a storage account through SSH File Transfer Protocol for file access, transfer, and management. It requires a supported storage account with hierarchical namespace enabled, then local users and scoped permissions control access to containers and paths.
Storage platform
intermediate
5 commands
Aliases: Azure Blob Storage SFTP, SFTP support for Azure Blob Storage, storage account SFTP, Blob SFTP endpoint, SFTP for Azure Blob Storage
Quick peek
Open full term page
Storage
premium
Azure Storage Actions
Azure Storage Actions is a fully managed platform for automating data management tasks across Azure Blob Storage and Azure Data Lake Storage objects without provisioning separate compute.
Storage platform
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
Microsoft-managed key for storage
Microsoft-managed key for Storage means the default Azure Storage encryption approach where Microsoft manages the keys that protect stored data at rest. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline.
Storage encryption
advanced
4 commands
Aliases: platform-managed key for storage, PMK for storage, Microsoft managed storage encryption key
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
field-manual-complete
Data Lake Storage Gen2
Data Lake Storage Gen2 is Azure Blob Storage with a hierarchical namespace enabled for analytics workloads. Microsoft Learn describes it as combining file-system style directories, ACLs, and large-scale throughput with Blob Storage durability, security, lifecycle, tiering, and ecosystem compatibility for big data scenarios.
Analytics storage
fundamentals
8 commands
Aliases: ADLS Gen2
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
Storage customer-managed key
A storage customer-managed key is a key in Azure Key Vault or Managed HSM that a customer controls for Azure Storage encryption at rest. Azure Storage still performs encryption, but the customer manages key ownership, access, rotation, purge protection, and lifecycle accountability.
Storage encryption
fundamentals
5 commands
Aliases: Azure Storage customer-managed key, storage CMK, customer-managed key for storage
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
Storage
complete
Storage account
Microsoft Learn describes an Azure storage account as the resource that contains Azure Storage data objects such as blobs, files, queues, and tables. It provides a unique namespace for data accessible over HTTP or HTTPS, with durability, availability, security, and scalability choices.
Storage account
intermediate
5 commands
Aliases: storage-account, Storage account, Azure Storage account, general-purpose storage account, GPv2 storage account, storage account resource
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
field-manual-complete
Customer-managed key for storage
Customer-managed key for storage is an Azure Storage encryption option where the account uses a key stored in Key Vault or Managed HSM to wrap storage encryption keys.
Storage accounts
advanced
4 commands
Aliases: Customer-managed key for storage
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
Service endpoint for Storage
A service endpoint for Storage enables the Microsoft.Storage endpoint on a virtual network subnet and pairs it with storage account network rules. It lets workloads in that subnet reach Azure Storage over the Microsoft backbone while the account firewall allows only approved virtual network sources.
Storage platform
intermediate
6 commands
Aliases: Azure Storage VNet rule, Microsoft.Storage service endpoint, Service endpoint for Storage, Storage service endpoint, service endpoint for storage, service-endpoint-for-storage
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
Containers
premium
Kubernetes StorageClass
A Kubernetes StorageClass defines how persistent storage is dynamically provisioned for persistent volume claims, including the driver, performance tier, reclaim policy, and binding behavior.
Kubernetes storage
Intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
SFTP for Blob Storage
SFTP for Blob Storage is the storage-account feature that exposes blob containers to SFTP clients after hierarchical namespace is enabled. Administrators configure local users, authentication methods, home directories, and permission scopes so external or internal clients can transfer files without custom SFTP infrastructure.
Blob Storage
advanced
5 commands
Aliases: Blob Storage SFTP, SFTP for Blob Storage, SFTP landing zone, storage SFTP local user, SFTP-enabled storage account
Quick peek
Open full term page
Storage
premium
Trusted Microsoft services for storage
Trusted Microsoft services for Azure Storage are specific Azure services that Microsoft documents as eligible for storage firewall exceptions. Depending on the service, access may be based on tenant registration, supported operations, or managed identity authorization combined with Azure RBAC or Data Lake ACLs.
Storage platform
intermediate
5 commands
Aliases: trusted Azure services for Storage, storage trusted services list, Azure Storage trusted services, trusted services storage firewall
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
Azure Container Storage
A cloud-based volume management, deployment, and orchestration service built natively for containers and integrated with Kubernetes persistent volumes.
Container storage
intermediate
4 commands
Aliases: ACS for containers
Quick peek
Open full term page
Storage
premium
Azure Storage Explorer
Azure Storage Explorer is a standalone app for Windows, macOS, and Linux that helps users connect to and manage Azure Storage data and resources through a graphical interface.
Storage tooling
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
Azure Storage Mover
Azure Storage Mover is a fully managed migration service that helps move files and folders from on-premises or AWS S3 sources to Azure Storage while minimizing workload downtime.
Storage migration
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Monitoring and Observability
premium
Diagnostic settings for storage
Diagnostic settings for storage route Azure Storage platform logs and metrics, including service-specific operations where supported, to destinations such as Log Analytics, Event Hubs, or Storage for investigation and compliance.
Data operations
intermediate
4 commands
Aliases: storage diagnostic settings, Azure Storage diagnostic settings, Storage account diagnostic settings, storage platform log routing
Quick peek
Open full term page
Storage
premium
Filesystem in Data Lake Storage
Filesystem in Data Lake Storage is the top-level container-like namespace in Azure Data Lake Storage Gen2 that holds directories and files in Azure.
Data Lake Storage Gen2
intermediate
4 commands
Aliases: Filesystem in Data Lake Storage, filesystem in data lake storage
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
Minimum TLS version for Storage
Minimum TLS version for Storage is a storage account setting that rejects client connections using TLS versions below the configured minimum. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline.
Storage security
intermediate
4 commands
Aliases: TLS minimum for storage, TLS1_2 storage, minimum TLS for Azure Storage, minimumTlsVersion, storage minimum TLS
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
premium
Azure Storage Discovery
Azure Storage Discovery is a fully managed service that provides enterprise-wide visibility into Azure Blob Storage and Azure Data Lake Storage estates for analysis, optimization, security, and operations.
Storage platform
intermediate
3 commands
Aliases: No aliases yet
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
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
complete
Storage account access key
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 access key, account key, shared key, storage key
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