Search Azure terms

Analytics premium Kusto materialized view Kusto materialized view is a managed aggregation over a source table or another materialized view that keeps a continuously updated result for faster queries. Kusto query optimization Advanced 5 commands Aliases: ADX materialized view, Kusto MV, materialized view in Azure Data Explorer Quick peek Open full term page

Analytics field-manual-complete Kusto Query Language Kusto Query Language, or KQL, is the query language used across Azure Data Explorer, Microsoft Fabric, Azure Monitor, and Microsoft Sentinel to explore structured, semi-structured, and text data, filter records, summarize results, detect patterns, and build operational analytics and dashboards. Resource Graph fundamentals 4 commands Aliases: KQL Quick peek Open full term page

Analytics field-manual-complete Kusto query performance Kusto query performance describes how efficiently Azure Data Explorer, Fabric, Azure Monitor, or Sentinel executes KQL, including how much data a query scans, which operators it uses, how resources are consumed, and whether service limits or workload controls affect results. Azure Data Explorer intermediate 4 commands Aliases: No aliases yet 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

Analytics premium Kusto cluster Kusto cluster is the Azure Data Explorer compute resource that hosts databases, ingestion, query processing, scale settings, networking, and monitoring for Kusto workloads. Azure Data Explorer infrastructure Intermediate 5 commands Aliases: Azure Data Explorer cluster, ADX cluster, Microsoft.Kusto cluster Quick peek Open full term page

Analytics premium Kusto continuous export Kusto continuous export periodically runs a Kusto query and writes results to an external table destination such as Azure Storage for downstream processing or archiving. Azure Data Explorer export Advanced 5 commands Aliases: ADX continuous export, Kusto export policy, continuous data export Quick peek Open full term page

Analytics premium Kusto database Kusto database is a logical container inside an Azure Data Explorer cluster that holds tables, functions, policies, permissions, and ingestion/query configuration. Azure Data Explorer database Intermediate 5 commands Aliases: ADX database, Azure Data Explorer database, Kusto DB Quick peek Open full term page

Analytics premium Kusto follower database Kusto follower database is a read-only database attached from another Azure Data Explorer cluster so consumers can query leader data without copying it. Azure Data Explorer data sharing Advanced 5 commands Aliases: ADX follower database, Azure Data Explorer follower database, followed database Quick peek Open full term page

Analytics premium Kusto function Kusto function is a reusable KQL query or query fragment, stored as a database entity or defined ad hoc, that standardizes analytics logic. Kusto query objects Intermediate 5 commands Aliases: Kusto stored function, ADX stored function, KQL function Quick peek Open full term page

Analytics premium Kusto ingestion Kusto ingestion is the process of loading data into Azure Data Explorer tables, where data is validated, mapped, indexed, encoded, and made queryable. Azure Data Explorer ingestion Intermediate 5 commands Aliases: ADX ingestion, Azure Data Explorer ingestion, Kusto data ingestion Quick peek Open full term page

Management and Governance premium Resource Graph query A Resource Graph query is a fast way to ask, “What resources do we have?” across subscriptions. It is useful for inventory, governance, cleanup, tagging checks, security investigations, and finding patterns that would be painful to inspect one resource at a time. Resource Graph intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Analytics field-manual-complete Kusto private endpoint A Kusto private endpoint connects clients on an Azure virtual network to an Azure Data Explorer cluster through Azure Private Link, using private IP addressing so query and ingestion traffic can avoid public internet exposure and follow private DNS and approval controls. Azure Data Explorer advanced 6 commands Aliases: No aliases yet 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

Analytics field-manual-complete Kusto table A Kusto table is a database object in Azure Data Explorer or Fabric that stores ingested records in a named schema. Tables are created, altered, queried, secured, and governed through Kusto management commands, policies, ingestion mappings, and KQL queries in production. Azure Data Explorer intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Analytics field-manual-complete Kusto table policy A Kusto table policy is a management setting on a table that controls behavior such as retention, caching, update processing, ingestion batching, restricted view access, row-level security, or other operational rules supported by Azure Data Explorer and Fabric for governed analytics workloads. Data engineering and analytics intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Analytics field-manual-complete Kusto update policy A Kusto update policy is an automation rule that runs when new data is written to a source table, executes a transformation query, and inserts the transformed results into one or more target tables without requiring separate orchestration inside Kusto. Azure Data Explorer intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Analytics field-manual-complete Kusto workload group A Kusto workload group groups queries and management commands by shared characteristics so Azure Data Explorer or Fabric can apply request limits and rate limits. Workload groups support workload management, concurrency control, prioritization, and protection from resource monopolization across tenants. Azure Data Explorer advanced 4 commands Aliases: No aliases yet Quick peek Open full term page

Analytics premium Kusto data connection Kusto data connection links Azure Data Explorer to event or storage sources such as Event Hubs, Event Grid, or IoT Hub so data can be ingested into a database table. Azure Data Explorer ingestion Intermediate 5 commands Aliases: ADX data connection, Event Hubs data connection, Event Grid data connection, IoT Hub data connection Quick peek Open full term page

AI and Machine Learning premium Search query key A search query key is an Azure AI Search API key that permits read-only document queries against indexes. It is intended for client applications that need search results but should not manage indexes, data sources, indexers, skillsets, or service configuration. Search fundamentals 5 commands Aliases: Azure AI Search query key, search API query key, read-only search key, query API key, Azure Search query key Quick peek Open full term page

Databases premium Azure SQL Query Store Find the exact query plan regression that appeared after an application deployment or database compatibility-level change.; Compare normal and incident windows before deciding whether a SKU scale-up is justified. Azure SQL Database fundamentals 4 commands Aliases: Azure SQL Query Store Quick peek Open full term page

Databases premium Cosmos DB query Find the high-RU query that causes 429 throttling before increasing provisioned throughput or autoscale limits.; Decide whether a user-facing search should remain a Cosmos DB query, become a point-read pattern, or move t Azure Cosmos DB intermediate 4 commands Aliases: Cosmos DB query, cosmos db query Quick peek Open full term page

Monitoring and Observability template-specs-upgraded Scheduled query alert A scheduled query alert is an Azure Monitor alert built from a KQL query that runs again and again on a defined cadence. Monitoring advanced 6 commands Aliases: log search alert, Azure Monitor scheduled query rule, scheduledQueryRules, KQL alert, Log Analytics alert Quick peek Open full term page

Databases field-manual-complete PostgreSQL Query Store PostgreSQL Query Store is a built-in performance history feature for Azure Database for PostgreSQL flexible server. Instead of guessing why the database became slow, teams can look at recorded query behavior over time: which queries ran often, which took longest, which waited on locks or I/O, and when the pattern changed. It is not a tuning magic button. It is evidence. Developers, DBAs, and operators use it to separate bad SQL, missing indexes, workload spikes, and application changes from general database health complaints. Data platform intermediate 5 commands Aliases: PostgreSQL Query Store, Azure PostgreSQL Query Store, pg_qs, Query Store for PostgreSQL flexible server Quick peek Open full term page

AI and Machine Learning verified Query key A query key is a safer API key for applications that only need to search an Azure AI Search index. Azure AI Search fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases verified Query Store Query Store is a built-in history recorder for SQL query behavior. Azure SQL intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Analytics field-manual-complete Stream Analytics query A Stream Analytics query is the logic that turns incoming events into useful results. It looks like SQL, but it is built for streams, time windows, late events, joins, reference data, and continuous output. The query decides what fields to keep, what events to filter, how to group data, and where each result goes. For operators, a query is not just code; it is production behavior that can change alerts, dashboards, and records within seconds. Streaming analytics fundamentals 5 commands Aliases: Stream Analytics query, ASA query, Stream Analytics SQL query, streaming query, ASAQL query Quick peek Open full term page

Databases complete SQL Query Store Microsoft Learn describes Query Store as a SQL feature that captures a history of queries, execution plans, and runtime statistics for review. It helps troubleshoot performance changes, especially regressions caused by plan changes, and is available across SQL Server, Azure SQL Database, Azure SQL Managed Instance, and related SQL platforms. SQL performance monitoring intermediate 5 commands Aliases: Query Store, Azure SQL Query Store, SQL Server Query Store, query performance history Quick peek Open full term page

Storage verified OData table query An OData table query is a Table Storage query operation that returns tables or entities as an OData entity set. Azure Table Storage supports options such as $filter, $top, and $select, and paged results may include continuation tokens. Clients must preserve options across pages. Table Storage fundamentals 4 commands Aliases: Table Storage query, Query Entities, OData entity query, Azure table query Quick peek Open full term page

Databases complete Slow query Microsoft Learn database guidance uses slow query analysis across Azure SQL, Azure Database for PostgreSQL, Azure Database for MySQL, and related services to find statements whose duration, resource use, waits, or frequency hurt users or capacity. Evidence usually comes from Query Store, diagnostic logs, metrics, or engine-specific views. Database advanced 2 commands Aliases: Long-running query, slow SQL query, query regression, expensive query Quick peek Open full term page

Analytics learning-path-anchor Databricks table A governed Databricks data object, commonly managed, external, or foreign, queried through Unity Catalog and optimized for analytics. Databricks fundamentals 4 commands Aliases: Unity Catalog table, Delta table in Databricks, Databricks managed table Quick peek Open full term page

Analytics premium Azure Data Explorer A fully managed, high-performance analytics service for near-real-time analysis of large telemetry, log, event, and time-series datasets. Real-time analytics intermediate 5 commands Aliases: ADX, Kusto Quick peek Open full term page

Management and Governance premium Azure savings plan An Azure savings plan provides discounted pricing on eligible compute usage when you commit to an hourly spend for one or three years. Cost Management fundamentals 5 commands Aliases: Azure savings plan, Azure savings plans, compute savings plan, savings plan for compute Quick peek Open full term page

Analytics premium Ingestion mapping Ingestion mapping controls how streaming or batch data lands in the correct Kusto columns without corrupting schema, losing values, or forcing manual parsing later. Teams see it in azure data explorer tables, kusto databases. It is not a query projection, update policy, table schema alone, Data Factory mapping data flow, or index projection; confusing them can create null columns, failed ingestion. 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 Data Explorer Intermediate 5 commands Aliases: Kusto ingestion mapping, ADX ingestion mapping, table ingestion mapping, JSON ingestion mapping, CSV ingestion mapping Quick peek Open full term page

Monitoring and Observability premium KQL KQL controls how operators search telemetry, detect incidents, investigate performance, build dashboards, create alerts, and summarize operational evidence across Azure services. Teams see it in log analytics workspaces, azure monitor logs. It is not SQL, PromQL, OData filters, ARM template expressions, Azure Data Factory expression language, or application code; confusing them can create missed incidents, expensive queries. 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. Query language Fundamentals 5 commands Aliases: Kusto Query Language, Kusto query, Azure Monitor query language, Sentinel query language Quick peek Open full term page

Monitoring and Observability premium KQL function KQL function controls how teams reuse common filters, joins, calculations, detections, and normalization logic across monitoring, security, and analytics workloads. Teams see it in azure data explorer databases, microsoft sentinel hunting queries. It is not an Azure Function app, SQL stored procedure, Logic Apps workflow, user-defined scalar operator, or ARM template function; confusing them can create stale detection logic, broken dashboards. 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. Query language Intermediate 5 commands Aliases: Kusto function, user-defined KQL function, stored Kusto function, query-defined function Quick peek Open full term page

Analytics learning-path-anchor Synapse SQL CETAS Synapse SQL CETAS means CREATE EXTERNAL TABLE AS SELECT. It creates external table metadata and exports the result of a T-SQL SELECT statement in parallel to files in Azure Storage or Azure Data Lake Storage Gen2 for later SQL or lake consumption. Synapse Analytics fundamentals 6 commands Aliases: CREATE EXTERNAL TABLE AS SELECT, CETAS, Synapse CETAS, serverless SQL CETAS Quick peek Open full term page

Analytics learning-path-anchor Synapse SQL external table A Synapse SQL external table is database metadata that lets Synapse SQL query files stored outside the database, usually in Azure Storage or ADLS Gen2. It references an external data source, file format, and file location for governed SQL analytics. Synapse Analytics fundamentals 6 commands Aliases: external table in Synapse, Synapse external table, SQL external table, external table over lake files Quick peek Open full term page

Analytics learning-path-anchor Synapse SQL on-demand Synapse SQL on-demand is the serverless SQL pool model in Azure Synapse Analytics. It lets teams run T-SQL queries over data in the lake without provisioning dedicated warehouse capacity, storing only metadata objects while using external data sources, views, functions, and security objects. Synapse Analytics fundamentals 6 commands Aliases: SQL on-demand, Synapse serverless SQL, serverless SQL in Synapse, built-in serverless SQL pool Quick peek Open full term page

Analytics premium ADX dashboard ADX dashboard is an Azure Data Explorer dashboard made of KQL-backed tiles and visuals for exploring telemetry or time-series data. In everyday Azure work, teams use it to turn Kusto queries into shared operational views for incidents, trends, business metrics, or engineering reviews. The useful evidence is dashboard owner, data source, base query, tile query, Azure Data Explorer intermediate 4 commands Aliases: Azure Data Explorer dashboard, Kusto dashboard, ADX visualization dashboard Quick peek Open full term page

Management and Governance premium Azure Resource Graph Azure Resource Graph is the fast inventory search engine for Azure resources. Microsoft Learn anchors this term in What is Azure Resource Graph?, 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, Azure Resource Graph extends Azure Resource Management by maintaining queryable resource data across the subscriptions available to the signed-in. Fleet discovery fundamentals 4 commands Aliases: ARG Quick peek Open full term page

Management and Governance premium Chargeback Chargeback bills internal teams or business units for their Azure consumption. Cost Management fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Analytics learning-path-anchor Synapse SQL script A Synapse SQL script is a saved T-SQL authoring artifact in Synapse Studio. Users create or import scripts in the Develop hub, connect them to a dedicated or serverless SQL pool, run queries, review tabular results, export output, and organize scripts into folders. Synapse Analytics fundamentals 5 commands Aliases: SQL script in Synapse, Synapse Studio SQL script, T-SQL script artifact, Synapse query script Quick peek Open full term page

AI and Machine Learning learning-path-anchor Synonym map A synonym map helps Azure AI Search understand that different words can mean the same thing for search. Users may type laptop, notebook, ultrabook, or a product nickname, while the indexed document uses only one of those terms. The synonym map teaches the search service to expand or rewrite the query so relevant documents... Azure AI Search intermediate 5 commands Aliases: AI Search synonym map, search synonyms, synonymMaps, equivalent terms map 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 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

Governance learning-path-anchor Tag inheritance Tag inheritance is the controlled reuse of tags from a higher Azure or billing scope. Cost Management can apply higher-scope tags to usage records for reporting, while Azure Policy can copy selected parent tag values onto resources for governance at scale. Resource tagging fundamentals 5 commands Aliases: inherited tags, Azure tag inheritance, billing tag inheritance, policy tag inheritance Quick peek Open full term page

Governance learning-path-anchor Tag name A tag name is the label key in an Azure tag. In Environment=Prod, Environment is the tag name and Prod is the value. The name tells people and tools what question the tag answers: who owns this, what cost center pays for it, what environment is it, or what application does it support? Good tag names are short, consistent, boring, and governed. Bad tag names create duplicate categories like CostCenter, cost-center, CostCentre, and BillingCode that fracture reports. Resource tagging fundamentals 5 commands Aliases: tag key, Azure tag key, resource tag name, metadata tag name Quick peek Open full term page

Management and Governance learning-path-anchor Tag value A tag value is the answer attached to a tag name. If the tag name is Environment, the value might be Production, Test, or Sandbox. If the name is CostCenter, the value might be a finance code. Values are where governance becomes meaningful, because they separate one owner, workload, data class, or lifecycle state from another. A good value is standardized, approved, and easy to query. A bad value is free-text chaos: prod, production, PROD, live, and critical all trying to mean the same thing. Tags and naming fundamentals 5 commands Aliases: tag values, Azure tag value, resource tag value, tag metadata value Quick peek Open full term page

Management and Governance learning-path-anchor Tagging strategy A tagging strategy is the playbook for using tags without making a mess. It answers simple but important questions: which tags are required, who owns the list, which values are allowed, where tags are applied, and what happens when a resource is missing one. Without a strategy, tags become random notes. With a strategy, tags become a dependable system for cost allocation, ownership, lifecycle cleanup, compliance evidence, and operational routing. The best strategies are small enough to follow and strict enough to m Tags and naming fundamentals 5 commands Aliases: Azure tagging strategy, tag governance strategy, tag taxonomy, resource tagging standard Quick peek Open full term page

Management and Governance learning-path-anchor Tags Tags are labels you attach to Azure things so people and tools can understand what they are for. A tag has a name and a value, such as Owner=DataPlatform or Environment=Prod. Tags do not make a virtual machine faster, secure a database, or change a web app setting. They make the estate easier to organize, report on, govern, and automate. Useful tags answer questions the business actually asks: who owns this, what does it support, what environment is it, and who pays for it? Tags and naming advanced 5 commands Aliases: Azure tags, resource tags, name-value tags, Azure metadata tags Quick peek Open full term page