Search Azure terms

Databases premium Azure Managed Redis Azure Managed Redis is a Microsoft-managed in-memory data store based on Redis Enterprise, used for low-latency caching, session storage, messaging, and semantic cache scenarios. Managed cache intermediate 6 commands Aliases: Managed Redis, Redis Enterprise on Azure, Azure Redis Enterprise Quick peek Open full term page

Storage premium Azure HPC Cache Azure HPC Cache was a managed Azure file-caching service for HPC workloads; Microsoft retired the service on September 30, 2025, so current work should focus on migration or historical inventory. Retired HPC caching advanced 5 commands Aliases: HPC Cache, Azure Storage Cache Quick peek Open full term page

Analytics learning-path-anchor Synapse workspace managed identity A Synapse workspace managed identity is the workspace's own identity in Microsoft Entra ID. Instead of saving passwords, keys, or connection strings inside pipelines and notebooks, Synapse can use this identity to ask for tokens and reach trusted Azure resources. It is commonly used for Data Lake Storage, Key Vault, SQL, and linked service... Synapse Analytics intermediate 8 commands Aliases: Synapse managed service identity, Synapse MSI, workspace system-assigned identity, Synapse workspace identity Quick peek Open full term page

Storage premium Azure Managed Lustre Azure Managed Lustre is a managed parallel file system for high-performance computing and AI workloads that need scalable, low-latency file storage in Azure. Parallel file systems advanced 5 commands Aliases: Managed Lustre, Azure Managed Lustre File System, AMLFS Quick peek Open full term page

Analytics premium Kusto cache policy Kusto cache policy controls which Azure Data Explorer data is kept in hot local cache versus colder storage for faster queries and managed cost. Azure Data Explorer policies Advanced 5 commands Aliases: ADX cache policy, hot cache policy, Kusto hot cache, Azure Data Explorer caching policy Quick peek Open full term page

Databases premium Azure Cache for Redis A managed in-memory data store based on Redis that improves application performance by caching frequently accessed data close to workloads. Cache fundamentals 4 commands Aliases: Azure Redis Cache, Redis cache, managed Redis cache Quick peek Open full term page

Identity learning-path-anchor System-assigned managed identity A system-assigned managed identity lets one Azure resource authenticate without a stored password, client secret, or certificate managed by your app team. You turn it on for a resource such as a web app, function, virtual machine, data factory, or automation account. Azure creates an identity for that resource, and the resource can request... Managed identities intermediate 4 commands Aliases: system assigned identity, resource managed identity, SystemAssigned identity, managed service identity Quick peek Open full term page

Databases verified Redis cache A managed in-memory Redis data store on Azure used to improve application latency, throughput, and resilience of frequently accessed data. Azure Managed Redis intermediate 7 commands Aliases: No aliases yet Quick peek Open full term page

Databases verified Redis Enterprise cache A Redis Enterprise cache is an Azure cache instance running on Redis Enterprise rather than basic open-source Redis nodes. In Azure Cache for Redis Enterprise tiers, it provides clustered data nodes, quorum behavior, Enterprise/Enterprise Flash SKUs, modules, persistence, and active geo-replication for demanding workloads. Azure Managed Redis intermediate 5 commands Aliases: Azure Cache for Redis Enterprise, Enterprise Redis cache, Enterprise cache Quick peek Open full term page

Databases verified Redis cache shard A Redis cache shard is a slice of the cache. Instead of forcing every key, session, counter, and hot lookup through one Redis process, the cache can divide data across multiple shards. Each shard owns part of the keyspace, so the workload has more room and more processing capacity. For a learner, the important point is simple: sharding helps a cache grow horizontally, but it also makes key design, client compatibility, monitoring, and operational change control more important. Cache and in-memory data fundamentals 4 commands Aliases: Redis shard, cache shard, Redis partition Quick peek Open full term page

Databases verified Redis cache SKU A Redis cache SKU is the size and capability package you buy for the cache. It answers questions like how much memory the cache has, what performance level it can provide, which high-availability or scaling features are available, and how much it will cost. For Azure teams, SKU is not just a billing label. It is a design decision that affects latency, resilience, migration options, monitoring expectations, and whether the cache can support the application when traffic grows. Cache and in-memory data fundamentals 4 commands Aliases: Redis SKU, cache SKU, Redis size Quick peek Open full term page

Databases verified Redis cache tier A Redis cache tier is the broad class of cache capability, while the SKU is the exact purchasable size inside that class. The tier tells you what kind of workload the cache is meant for: simple development, production high availability, larger scale, flash-backed capacity, or a managed enterprise-style Redis deployment. For learners, tier is the decision that says what features and operating expectations are on the table before anyone argues about the exact memory size. Cache intermediate 4 commands Aliases: Redis tier, cache tier, Redis performance tier Quick peek Open full term page

AI and Machine Learning expanded Semantic cache A semantic cache stores previous prompts and responses with vector representations so later requests with similar meaning can reuse a cached response. In Azure, this pattern is used with services such as API Management and Azure Managed Redis to reduce latency, backend load, and LLM calls. Azure Managed Redis and API Management advanced 4 commands Aliases: semantic caching, LLM semantic cache, AI gateway semantic cache, vector response cache Quick peek Open full term page

Analytics premium Databricks managed resource group The Azure resource group created or referenced for Databricks-managed infrastructure that supports a workspace and its classic compute resources. Azure Databricks intermediate 6 commands Aliases: managed resource group, Azure Databricks managed resource group, workspace managed resource group Quick peek Open full term page

Containers premium AKS managed identity An AKS managed identity is a Microsoft Entra identity that an AKS cluster uses to manage Azure resources without stored service principal secrets. AKS identity Intermediate 5 commands Aliases: Azure Kubernetes Service managed identity, aks managed identity Quick peek Open full term page

AI and Machine Learning premium Azure OpenAI managed identity Azure OpenAI managed identity uses Microsoft Entra identities so Azure workloads can call model endpoints without stored keys. Azure OpenAI intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Cosmos DB integrated cache Cosmos DB integrated cache means a dedicated gateway feature that serves cached point reads and queries without consuming request units for repeated reads. It is the practical label operators use when they decide how application data should be modeled, queried, protected, and monitored in Azure Cosmos DB. In plain English, it explains where developers, platform engineers, and support teams meet: the application wants fast data access, while the platform controls scale, cost, security, and recovery. A good glossary entry helps the team know which setting to inspect, which owner to involve, and which symptoms prove the design works. Azure Cosmos DB intermediate 5 commands Aliases: Azure Cosmos DB integrated cache, cosmos db integrated cache Quick peek Open full term page

Integration premium Event Grid managed identity delivery Event Grid managed identity delivery is the pattern where Event Grid uses a managed identity on a topic, domain, or system topic to authenticate event delivery to supported destinations. In Azure, it shows up when teams want to deliver events to Azure destinations without storing destination keys or embedding secrets in event subscription configuration. Teams use it to review system-assigned or user-assigned identity, Event Grid topic or domain identity settings, destination RBAC role assignments, delivery identity settings, dead-letter identity settings, and monitoring before changing production behavior. Event routing advanced 5 commands Aliases: Event Grid managed identity event delivery, managed identity delivery for Event Grid Quick peek Open full term page

Databases premium Integrated cache Integrated cache controls how read-heavy Cosmos DB API for NoSQL applications reduce latency and request-unit consumption by reusing cached point reads and query results. Teams see it in azure cosmos db accounts, dedicated gateway configuration. It is not Azure Cache for Redis, a client-side memory cache, analytical store, a materialized view, or a replacement for correct partitioning; confusing them can create unexpected RU spending, stale reads. 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 Cosmos DB Intermediate 5 commands Aliases: Cosmos DB integrated cache, Azure Cosmos DB integrated cache, dedicated gateway cache, item cache, query cache Quick peek Open full term page

Integration premium Service Bus managed identity Service Bus managed identity means using Microsoft Entra managed identities so Azure-hosted applications can access Service Bus without stored credentials. Applications receive RBAC roles such as Data Sender or Data Receiver, while Service Bus namespace identities may also be assigned for service-managed scenarios such as encryption configuration. Service Bus fundamentals 5 commands Aliases: Service Bus identity-based access, Service Bus Entra authentication, managed identity for Service Bus, Service Bus secretless authentication, Service Bus RBAC identity Quick peek Open full term page

Security premium Customer-managed key rotation Customer-managed key rotation is the planned creation and adoption of new versions of a customer-managed encryption key while Azure services keep accessing protected data safely. Key management advanced 4 commands Aliases: Customer-managed key rotation Quick peek Open full term page

Analytics premium Data Factory managed identity The Microsoft Entra identity assigned to a Data Factory so pipelines and linked services can access Azure resources without embedded passwords. Data integration and orchestration Intermediate 4 commands Aliases: Data Factory managed identity, ADF managed identity, data factory managed identity Quick peek Open full term page

Analytics premium Data Factory managed virtual network A Microsoft-managed network boundary used by Azure Integration Runtime to isolate data integration traffic and connect through managed private endpoints. Data integration and orchestration Intermediate 4 commands Aliases: Data Factory managed virtual network, ADF managed virtual network, data factory managed virtual network Quick peek Open full term page

AI and Machine Learning premium Enrichment cache An enrichment cache stores outputs from document cracking and skill execution in Azure Storage so AI enrichment pipelines can reuse existing processed content. Azure AI Search intermediate 4 commands Aliases: AI Search enrichment cache, incremental enrichment cache, skillset cache Quick peek Open full term page

Networking premium Front Door cache purge A Front Door cache purge removes selected cached content from Azure Front Door edge locations so future requests retrieve fresh content from the origin. Application delivery and API edge intermediate 4 commands Aliases: Azure Front Door cache purge, AFD cache purge, Front Door purge content Quick peek Open full term page

Web premium Function app managed identity Function app managed identity is a Microsoft Entra identity assigned to a function app so its code and supported bindings can access Azure resources without storing passwords or connection strings. Teams use it to replace secrets in app settings with identity-based access to services such as Storage, Service Bus, Key Vault, Event Hubs, SQL, or monitoring resources. In daily Azure work, it shows up when engineers grant a function app data-plane permissions, remove leaked connection strings, configure identity-based bindings, or investigate why a trigger cannot reach its dependency. Azure Functions intermediate 4 commands Aliases: Azure Functions managed identity, managed identity for Functions, function app identity Quick peek Open full term page

Integration premium Logic Apps managed identity A Logic Apps managed identity is the Microsoft Entra identity assigned to a Logic Apps workflow or Standard logic app resource so the workflow can authenticate to supported Azure resources without storing passwords, shared keys, or long-lived secrets in governed production environments. Azure Logic Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Web premium Managed certificate A managed certificate in Azure App Service is a platform-created TLS certificate for a supported custom domain. Azure can issue and renew it for basic HTTPS protection, but it has limitations compared with uploaded, Key Vault, or purchased certificates. That context supports safer operational decisions. TLS fundamentals 4 commands Aliases: App Service managed certificate, free managed certificate 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

Identity premium Managed identity A managed identity is an automatically managed Microsoft Entra identity assigned to a supported Azure resource. It lets workloads authenticate to services that support Microsoft Entra authentication without storing passwords, certificates, or client secrets in code, configuration, or deployment pipelines. Microsoft Entra workload identity intermediate 3 commands Aliases: Managed identity, system-assigned managed identity, user-assigned managed identity, Azure workload identity, secretless authentication, system-assigned identity, user-assigned identity, Microsoft Entra ID, Microsoft Entra workload identity Quick peek Open full term page

Security premium Managed identity for data access Managed identity for data access is the pattern of using a managed identity to let a workload read or write data without embedded secrets. Teams use it when pipelines, applications, jobs, or analytics services need secure access to storage, databases, or other data services. In plain English, it gives operators a named control for least-privilege data access, reduced secret exposure, and cleaner audit trails 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. Data access security intermediate 3 commands Aliases: Managed identity for data access, Microsoft Entra ID, Data access security Quick peek Open full term page

Databases premium Managed instance database A managed instance database is a database hosted inside Azure SQL Managed Instance with managed platform operations and SQL Server compatibility features. Teams use it when a workload needs managed SQL operations while keeping instance-level features closer to SQL Server. In plain English, it gives operators a named control for database-level ownership, backup evidence, restore planning, and migration clarity within a managed instance instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. Azure SQL Managed Instance intermediate 3 commands Aliases: Managed instance database, Azure SQL Managed Instance Quick peek Open full term page

Databases premium Managed Instance failover group Managed Instance failover group is a disaster-recovery relationship that lets databases in a SQL Managed Instance fail over to a paired managed instance. Teams use it when business-critical databases need cross-region continuity and a managed failover path. In plain English, it gives operators a named control for planned or emergency recovery with clearer listener, replication, and ownership evidence instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear. Azure SQL Managed Instance intermediate 3 commands Aliases: Managed Instance failover group, Azure SQL Managed Instance Quick peek Open full term page

Identity premium Assignment managed identity Assignment managed identity is the identity Azure Policy uses when a policy assignment must change resources during remediation. It matters most for effects such as modify and deployIfNotExists, where Policy is not just reporting non-compliance but attempting to fix or deploy something. The identity needs Azure RBAC permissions at the right scope. Without those. Azure Policy intermediate 2 commands Aliases: Policy assignment identity, Azure Policy managed identity, policy remediation identity, assignment identity Quick peek Open full term page

Management and Governance premium Cache freshness Cache freshness describes how current cached data or a cached response is compared with the origin source. Dashboard operations advanced 2 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Cache hit ratio Cache hit ratio is the percentage of cache lookups that are served from cache instead of going back to the origin system. Database advanced 2 commands Aliases: No aliases yet Quick peek Open full term page

Analytics verified Result set cache Microsoft Learn describes result set caching in Azure Synapse dedicated SQL pool as a feature that stores query results in the user database for reuse. When a repeated query can use cached results, it avoids recomputation, reduces compute use, and does not consume concurrency slots. Synapse Analytics intermediate 7 commands Aliases: result set caching, Synapse result set cache, SET RESULT_SET_CACHING, cached query results, dedicated SQL pool result cache Quick peek Open full term page

Analytics field-manual-complete Synapse result-set cache Synapse result-set cache is a dedicated SQL pool feature that persists eligible query results in the user database so repeated executions can return from cache instead of recomputing. It improves response time, reduces compute usage, and lets cached queries avoid consuming concurrency slots. Synapse Analytics fundamentals 7 commands Aliases: Azure Synapse result set caching, result set cache in dedicated SQL pool, Synapse SQL result-set cache, dedicated SQL pool cached results Quick peek Open full term page

App Hosting field-manual-complete App Service managed certificate An App Service managed certificate is a free certificate that Azure App Service can issue for an eligible custom domain on a web app or function app. App Service TLS Intermediate 5 commands Aliases: Azure App Service managed certificate, app service managed certificate Quick peek Open full term page

Containers field-manual-complete Container Apps managed environment A Container Apps managed environment is the shared home where one or more Azure Container Apps and jobs run. It is not your container image or one app instance; it is the boundary around the runtime, networking, logging, certificates, Dapr settings, and workload profile capacity that those apps use. Teams choose an environment before creating. Azure Container Apps intermediate 5 commands Aliases: No aliases yet 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

Analytics field-manual-complete Synapse managed private endpoint A Synapse managed private endpoint is a private endpoint that Azure Synapse creates inside a workspace managed virtual network to reach a specific Azure resource over Private Link. It supports approved, resource-scoped connectivity for storage, databases, Cosmos DB, and other targets without opening public network paths. Synapse Analytics intermediate 5 commands Aliases: Azure Synapse managed private endpoint, Synapse MPE, managed private endpoint in Synapse, Synapse Private Link endpoint Quick peek Open full term page

Analytics field-manual-complete Synapse managed virtual network A Synapse managed virtual network is the Azure-managed network boundary associated with a Synapse workspace. It isolates workspace data integration and Spark resources, enables managed private endpoints, and can restrict outbound connectivity to approved targets when data exfiltration protection is enabled at workspace creation. Synapse Analytics intermediate 5 commands Aliases: Azure Synapse managed virtual network, Synapse managed VNet, managed workspace virtual network, Synapse workspace managed VNet Quick peek Open full term page

Identity field-manual-complete User-assigned managed identity A standalone managed identity that can be attached to one or more Azure resources. Managed identities fundamentals 5 commands Aliases: UAMI, user managed identity, reusable managed identity Quick peek Open full term page

Databases complete SQL Agent on Managed Instance Microsoft Learn explains that SQL Server Agent executes SQL Agent jobs for task automation in Azure SQL Managed Instance. A job is a specified series of T-SQL scripts against a database, used to run administrative tasks one or more times and monitor success or failure. Azure SQL Managed Instance intermediate 5 commands Aliases: SQL Agent on Managed Instance, sql agent on managed instance, sql-agent-on-managed-instance Quick peek Open full term page

Databases complete SQL Managed Instance Microsoft Learn describes Azure SQL Managed Instance as a fully managed PaaS database engine with near complete SQL Server compatibility, native virtual network deployment, automated patching and backups, and instance-scoped features that help teams lift and shift SQL Server workloads with fewer application or database changes. Azure SQL fundamentals 5 commands Aliases: SQL MI, Azure SQL MI, Azure SQL Managed Instance, managed SQL instance 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

Databases complete SQL managed instance distributed transaction Microsoft Learn describes DTC for Azure SQL Managed Instance as support for distributed transactions in mixed environments, including managed instances, SQL Server, other relational databases, custom applications, and transaction participants that can establish network connectivity to Azure and coordinate transaction outcomes safely. SQL Managed Instance intermediate 5 commands Aliases: SQL MI distributed transaction, managed instance DTC, Azure SQL MI DTC, distributed transaction coordinator Quick peek Open full term page

Databases complete SQL managed instance failover group Microsoft Learn describes failover groups for Azure SQL Managed Instance as a way to manage geo-replication and coordinated failover of all user databases from one managed instance to another managed instance in a different Azure region, with stable listener endpoints for application connectivity. SQL Managed Instance intermediate 5 commands Aliases: SQL MI failover group, managed instance failover group, instance failover group, SQL Managed Instance FOG Quick peek Open full term page

Databases complete SQL managed instance link Microsoft Learn describes the Managed Instance link as near real-time data replication between SQL Server and Azure SQL Managed Instance, enabling hybrid flexibility, database mobility, read-only workload offload, analytics in Azure, disaster recovery patterns, and migrations with planned or forced failover. SQL Managed Instance intermediate 5 commands Aliases: Managed Instance link, SQL MI link, Azure SQL MI link, MI link Quick peek Open full term page