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 971 matching terms. Narrow the search to reduce the list.
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
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
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
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
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
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
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
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
field-manual-complete
Private endpoint for Storage
A private endpoint for Storage is the private network entry point to one storage account service, such as Blob, Files, Queue, Table, Data Lake Storage, or static website content.
Storage platform
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
field-manual-complete
Storage endpoint
A storage endpoint is the service URL used to reach an Azure Storage account data service, such as Blob, Data Lake Storage, File, Queue, Table, or static website hosting. Endpoints identify where clients connect, while authorization, firewall rules, DNS, and private endpoints determine whether access succeeds.
Storage platform
intermediate
5 commands
Aliases: storage service endpoint, Azure Storage endpoint, storage account endpoint, storage URL
Quick peek
Open full term page
Storage
complete
Storage account key
A shared secret that can authorize broad access to a storage account.
Storage platform
intermediate
5 commands
Aliases: storage key, storage account shared key, Azure Storage key, account key
Quick peek
Open full term page
Storage
learning-path-anchor
Table service endpoint
A Table service endpoint is the address your application uses when it talks to Azure Table Storage. For a normal Azure Storage account, it looks like an account-specific table URL. That address is not just a string in a connection setting; it determines DNS resolution, firewall evaluation, private endpoint routing, TLS, SDK configuration, and what operators test during an outage. If the endpoint is wrong, the table might exist and credentials might be valid, but clients still fail to connect.
Table Storage
intermediate
5 commands
Aliases: Azure Table endpoint, Table Storage endpoint, storage table endpoint, Table data-plane endpoint
Quick peek
Open full term page
Storage
command-rich
Table partition key
A Table partition key is the value that groups related entities in Azure Table Storage. Think of it as the first address line for a record. Entities with the same PartitionKey sit in the same logical partition and can be queried together more efficiently. The PartitionKey combines with RowKey to uniquely identify one entity. Choosing it well is a design decision, not just a...
Storage platform
intermediate
5 commands
Aliases: Azure Table PartitionKey, Table Storage PartitionKey, Table partition key value, PartitionKey property
Quick peek
Open full term page
Storage
command-rich
Table row key
A Table row key is the unique name of an entity inside one Azure Table partition. PartitionKey gets you to the right group; RowKey identifies the exact record in that group. Together they form the entity primary key. RowKey design often carries an order ID, device ID, timestamp pattern, sequence number, or composite value. It matters because point reads, updates, deletes, duplicate detection, and...
Storage platform
intermediate
5 commands
Aliases: Azure Table RowKey, Table Storage RowKey, Table row key value, RowKey property
Quick peek
Open full term page
Storage
premium
Large file share
Migrate a file server or NAS volume that has grown beyond small-share limits without splitting every application path immediately.; Set a quota large enough for migration staging while still preserving cost ownership and
Storage platform
intermediate
5 commands
Aliases: Large file share, large file share
Quick peek
Open full term page
Storage
premium
NFS file share
Migrate Linux applications that expect NFS paths without standing up and patching a self-managed file server.; Provide AKS pods, batch jobs, or HPC workers with a shared managed file system reachable through private netw
Azure Files
intermediate
4 commands
Aliases: Azure Files NFS share, NFS Azure file share, NFSv4.1 file share, NFS file share, nfs file share
Quick peek
Open full term page
Storage
premium
Blob index tags
Blob index tags are key-value attributes on blob data that Azure Storage indexes and exposes for querying across containers in a storage account.
Blob Storage
fundamentals
3 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
Blob service endpoint
Blob service endpoint is the address used to reach a storage account’s Blob service and is also the network target controlled by firewall, private endpoint, or service endpoint rules.
Storage platform
intermediate
3 commands
Aliases: Blob service endpoint, service endpoint, blob service endpoint
Quick peek
Open full term page
Storage
premium
Container access level
the Blob Storage container setting that decides whether anonymous clients can read no data, individual blobs, or container listings and blobs
Storage platform
intermediate
3 commands
Aliases: No aliases yet
Quick peek
Open full term page
Storage
premium
Archive rehydration
Archive rehydration is the restore process for data that was placed in Azure Blob Storage archive tier. Until rehydration finishes, the blob is offline and cannot be read like a normal file. Teams use rehydration when auditors, analysts, applications, or recovery teams need archived data back online. The decision is not just technical; it.
Blob Storage
intermediate
2 commands
Aliases: Blob rehydration, Rehydrate archived blob, Archive restore, Rehydration priority
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
verified
Queue poison message
Queue poison message is a Storage Queue message that failed processing enough times to require quarantine or manual handling. In Azure Functions queue triggers, failed messages can move to a <queue>-poison queue after configured retries so teams can inspect, repair, replay, or discard them safely.
Queue Storage
intermediate
5 commands
Aliases: Queue poison message
Quick peek
Open full term page
Storage
verified
Queue service endpoint
Queue service endpoint is the base URL used to reach the Queue service for a storage account, commonly shaped like https://<account>.queue.core.windows.net. Clients, SDKs, CLI commands, private endpoints, and firewall rules use this endpoint to send authenticated Queue Storage data-plane requests.
Queue Storage
intermediate
5 commands
Aliases: Queue service endpoint
Quick peek
Open full term page
Storage
verified
Rehydration priority
Rehydration priority controls whether archived Blob Storage data is restored with Standard or High urgency when moving back to an online tier.
Storage platform
intermediate
5 commands
Aliases: archive rehydration priority, blob rehydrate priority, high-priority rehydration, standard-priority rehydration
Quick peek
Open full term page
Storage
field-manual-complete
Secure transfer required
Secure transfer required means the storage account refuses insecure HTTP traffic.
Storage platform
intermediate
4 commands
Aliases: HTTPS-only storage, enableHttpsTrafficOnly, secure transfer to storage accounts
Quick peek
Open full term page
Storage
template-specs-upgraded
SAS expiry
SAS expiry is the time limit that decides how long a shared access signature can authorize storage access before it becomes invalid.
Storage platform
intermediate
4 commands
Aliases: SAS expiration, shared access signature expiry, SAS validity interval, SAS expiration policy, signed expiry
Quick peek
Open full term page
Storage
template-specs-upgraded
SAS permissions
SAS permissions are the operation rights encoded into a shared access signature, such as read, write, create, list, delete, or tag access.
Storage platform
intermediate
4 commands
Aliases: shared access signature permissions, SAS permission string, signed permissions, SAS rights, sp parameter
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
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
Monitoring and Observability
premium
Platform metrics
Platform metrics are numeric measurements that Azure resources emit and Azure Monitor collects at regular intervals. They describe resource health, capacity, utilization, latency, throughput, failures, and dimensions over time, helping operators chart behavior, create alerts, and diagnose service conditions quickly.
Monitoring
fundamentals
5 commands
Aliases: Azure platform metrics, Azure Monitor platform metrics, resource metrics
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
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
complete
Storage account diagnostic settings
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: storage diagnostics, storage logging, Azure Monitor diagnostic settings for storage, resource logs for storage
Quick peek
Open full term page
Storage
complete
Storage account infrastructure encryption
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: storage infrastructure encryption, Azure Storage double encryption, double encryption for storage, infrastructure-level encryption
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
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
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
Management and Governance
premium
Platform baseline
A platform baseline is the minimum set of governance, security, identity, networking, monitoring, and cost controls an Azure environment should inherit before workloads deploy. It sets standard expectations for subscriptions, landing zones, policy assignments, RBAC, logging, tags, and operational ownership across the estate.
Governance operations
fundamentals
5 commands
Aliases: Azure platform baseline, governance baseline, enterprise platform baseline
Quick peek
Open full term page
Management and Governance
premium
Platform landing zone
A platform landing zone is the shared Azure foundation that hosts common services for workload landing zones. It commonly includes connectivity, identity integration, management groups, policy, security monitoring, private DNS, logging, and automation so application teams can build on consistent enterprise guardrails.
Governance operations
fundamentals
5 commands
Aliases: Azure platform landing zone, shared platform landing zone, enterprise-scale platform landing zone
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
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
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
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
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