Search Azure terms

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

Integration verified Logic Apps Standard Logic Apps Standard is the Azure Logic Apps hosting option where one logic app resource can contain one or more workflows running in a single-tenant runtime, with app-level settings, storage dependency, deployment operations, and scaling controls in governed production environments. Azure Logic Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Integration top-250-pre130-priority-upgraded Logic Apps Consumption Logic Apps Consumption is the Azure Logic Apps hosting option where each logic app resource contains one workflow that runs in the multitenant Azure Logic Apps service and is typically billed by trigger executions, actions, and connector usage in governed production environments. Azure Logic Apps intermediate 4 commands Aliases: Logic Apps Consumption Quick peek Open full term page

Integration top-250-pre130-priority-upgraded Logic App A Logic App is an Azure Logic Apps resource or workflow that automates business and integration processes by connecting a trigger, actions, connectors, data operations, conditions, and monitoring so systems can exchange information without custom glue code everywhere in governed production environments. Azure Logic Apps fundamentals 4 commands Aliases: Azure Logic Apps Quick peek Open full term page

Compute premium Azure Functions Azure Functions is Azure serverless compute for running code from triggers such as HTTP requests, queues, timers, events, and service integrations without managing servers. Serverless compute intermediate 6 commands Aliases: Functions, Function App, serverless functions Quick peek Open full term page

Monitoring and Observability premium Action group An Azure Monitor action group defines who gets notified and which actions run when an alert fires. It can include notification receivers such as email, SMS, and push, plus automation actions such as webhooks, secure webhooks, Azure Functions, Logic Apps, runbooks, ITSM, or Event Hubs. Alerts fundamentals 5 commands Aliases: Azure Monitor action group, alert action group, monitor action group Quick peek Open full term page

Web premium App Service Environment Microsoft Learn describes App Service Environment as a single-tenant App Service deployment that runs in a customer virtual network. It hosts App Service plans and apps with stronger network isolation, dedicated compute boundaries, and high-scale hosting compared with the public multitenant App Service model. App Service isolation intermediate 5 commands Aliases: ASE, Azure App Service Environment, app service environment Quick peek Open full term page

Analytics premium Azure integration runtime Azure integration runtime is the compute infrastructure used by Azure Data Factory and Synapse pipelines to move data, dispatch activities, and connect across network environments. Data integration compute intermediate 5 commands Aliases: Integration Runtime, IR, ADF integration runtime Quick peek Open full term page

AI and Machine Learning premium Document analysis operation A document analysis operation is an asynchronous Document Intelligence request that analyzes a document with a model and returns extracted content, layout, and fields when polling completes. Document Intelligence intermediate 5 commands Aliases: Analyze operation, analyze document operation, Document Intelligence analysis request, async analysis operation Quick peek Open full term page

AI and Machine Learning premium Document classifier A document classifier is a Document Intelligence custom classification model that identifies document types or pages before extraction and routing. Document Intelligence intermediate 5 commands Aliases: custom classifier, Document Intelligence classifier, classification model, page classifier Quick peek Open full term page

Integration premium Event handler An event handler is the destination that receives Event Grid events and takes action, such as Azure Functions, Logic Apps, Event Hubs, Service Bus, Storage Queue, or a webhook. Teams use it to process Event Grid events by running code, starting workflows, buffering messages, streaming telemetry, or invoking a custom endpoint. It is not the event source, topic, filter, or schema that only decides what gets sent. In production, confirm the source, subscription, destination, filters, schema, identity, retry behavior, failure handling, monitoring, and owner before treating the route as safe. Event Grid intermediate 5 commands Aliases: Azure Event Grid handler, event destination Quick peek Open full term page

Integration premium Integration account Integration account controls where Logic Apps stores reusable B2B artifacts that workflows use to translate, validate, sign, decode, encode, or route enterprise messages. Teams see it in logic apps workflows, integration account artifacts. It is not a Logic App workflow, an Azure Storage account, an API connection, an Integration Service Environment, or a general-purpose document repository; confusing them can create failed EDI exchanges, expired certificates. 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. Enterprise integration Intermediate 5 commands Aliases: Logic Apps integration account, enterprise integration account, B2B artifact account, EDI artifact store Quick peek Open full term page

Integration premium Integration service environment Integration service environment controls how older Logic Apps workloads used a dedicated isolated runtime and VNet connectivity, and how teams identify remaining dependencies during migration. Teams see it in legacy logic apps ise resources, vnet integration. It is not Logic Apps Standard, App Service Environment, integration account, private endpoint, or a normal Consumption Logic App workflow; confusing them can create unsupported legacy integrations, missed retirement planning. 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. Logic Apps Advanced 5 commands Aliases: Logic Apps ISE, ISE, Integration Service Environment, dedicated Logic Apps environment 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

Management and Governance premium Policy event A policy event is a record or notification that something changed in Azure Policy evaluation. It can tell you that a resource became compliant, became non-compliant, or had a policy state created or removed. Instead of waiting for someone to refresh a portal report, teams can query policy events or route state-change events through Event Grid. For operators, this makes policy activity visible close to the time it happens, so compliance changes can trigger alerts, tickets, evidence capture, or remediation workflows. Azure Policy intermediate 5 commands Aliases: Policy event, policy-event Quick peek Open full term page

Integration premium Built-in connector A built-in connector is an Azure Logic Apps connector that runs natively with the Logic Apps runtime instead of through a separately hosted managed connector service. Logic Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium Duplicate detection Duplicate detection in Azure Service Bus detects repeated messages by MessageId within a configured history window so a queue or topic can ignore duplicate sends. Messaging intermediate 4 commands Aliases: Service Bus duplicate detection, duplicate message detection 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

Integration premium Connector a prebuilt integration component that lets workflows talk to another service, application, data source, or system through triggers and actions Workflows fundamentals 2 commands Aliases: No aliases yet Quick peek Open full term page

Integration verified Workflow In Azure Logic Apps, a workflow is the trigger-and-action definition that automates a business or integration process. A workflow starts from a trigger, runs actions according to conditions and control flow, connects cloud, on-premises, and partner systems, and records run history for operations. Logic Apps fundamentals 6 commands Aliases: Logic Apps workflow, logic app workflow, workflow definition, integration workflow Quick peek Open full term page

Integration verified Workflow action In Azure Logic Apps, a workflow action is a step that runs after a trigger or another action. Actions can call connectors, transform data, branch, loop, wait, compose values, or invoke services as part of the workflow definition during each run. Logic Apps intermediate 6 commands Aliases: Logic Apps action, workflow step, Logic Apps connector action, action definition Quick peek Open full term page

Integration verified Workflow run A workflow run is one execution instance of an Azure Logic Apps workflow after a trigger fires. The run records status, start and end time, duration, correlation details, trigger result, action history, retries, inputs, outputs, and errors used for troubleshooting. Logic Apps intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Integration verified Workflow trigger A workflow trigger is the first step in an Azure Logic Apps workflow. The trigger starts a run when a schedule, event, request, polling condition, or connector condition is met, and it passes initial data into the workflow and downstream actions. Logic Apps intermediate 6 commands Aliases: No aliases yet Quick peek Open full term page

Integration template-specs-upgraded Run history Microsoft Learn explains that after a Logic Apps workflow runs, you can review trigger history, workflow run history, status, inputs, outputs, performance, and individual step details. Run history lists past, current, and waiting executions for troubleshooting and monitoring. and support incident review. and resolution. Logic Apps intermediate 6 commands Aliases: Logic Apps run history, workflow run history, workflow execution history, Logic App runs history, run status history Quick peek Open full term page

Integration verified Request trigger In Azure Logic Apps, the Request built-in trigger starts a workflow when an HTTPS request reaches its generated endpoint. It can validate an optional JSON schema, expose a callback URL, and pair with a Response action when the workflow needs to behave like an API. securely. Logic Apps intermediate 5 commands Aliases: Logic Apps Request trigger, When an HTTP request is received, HTTP request trigger, request-based trigger, callable workflow endpoint Quick peek Open full term page

Management and Governance verified Actual cost Actual cost is the Cost Management view of charges as they are billed for a period, instead of spreading commitment purchases across future usage. In everyday Azure work, teams use it to reconcile monthly invoices, show subscription spend, and explain what Azure charged now. The useful evidence is billing period, scope, meter, resource, currency, tags, Cost Management fundamentals 4 commands Aliases: Azure actual cost, billing cost, actual charges Quick peek Open full term page

Monitoring and Observability verified Data collection endpoint An Azure Monitor resource that provides regional endpoints used by agents and data collection rules for configuration access and telemetry ingestion. Azure Monitor data collection Intermediate 4 commands Aliases: DCE, Azure Monitor DCE, monitor data collection endpoint Quick peek Open full term page

Monitoring and Observability verified Data collection rule An Azure Monitor resource that defines what telemetry to collect, how to transform it, and where to send it. Azure Monitor data collection Intermediate 4 commands Aliases: DCR, Azure Monitor DCR, monitor collection rule Quick peek Open full term page

Integration verified Recurrence trigger A Logic Apps trigger that starts a workflow on a schedule. Logic Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Management and Governance verified Cost allocation Cost allocation is an Azure glossary term for the Cost Management practice of splitting shared Azure charges across the subscriptions, resource groups, or tags that should financially own them. In practice, it helps teams reason about chargeback, showback, shared platform costs, central services, and fair business accountability for cloud spend using live Azure evidence, documented ownership, and Microsoft Learn guidance. It should be reviewed through security, reliability, operations, cost, and performance lenses before production changes. Cost Management intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

Integration premium field-manual Managed connector A managed connector is a Microsoft-managed connector that provides workflow triggers and actions for SaaS applications, Azure services, and supported systems. Teams use it when a workflow must integrate with another service without custom hosting code. In plain English, it gives operators a named control for reliable integration, authentication reuse, and clearer workflow ownership 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. Logic Apps connectors intermediate 3 commands Aliases: Managed connector, Azure Logic Apps, Logic Apps connectors Quick peek Open full term page

Databases premium Azure SQL logical server An Azure SQL logical server is a logical administrative construct for Azure SQL Database and related SQL resources. Microsoft Learn describes it as the central point for managing a collection of databases, including logins, firewall rules, auditing, threat detection policies, and failover groups. Azure SQL Database fundamentals 16 commands Aliases: No aliases yet Quick peek Open full term page

Web complete Static Web Apps managed functions Built-in Azure Functions APIs deployed and managed with an Azure Static Web Apps site. Static Web Apps intermediate 5 commands Aliases: static-web-apps-managed-functions, Static Web Apps managed functions, SWA managed functions, managed Functions API, Static Web Apps built-in API, Static Web Apps /api functions Quick peek Open full term page

Databases premium Cosmos DB logical partition Cosmos DB logical partition means the group of items in a container that share the same partition key value. 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 6 commands Aliases: Azure Cosmos DB logical partition, cosmos db logical partition Quick peek Open full term page

Containers premium Container Apps A serverless Azure service for running containerized apps and jobs without directly operating Kubernetes clusters. Serverless containers fundamentals 5 commands Aliases: Azure Container Apps Quick peek Open full term page

Containers premium Container Apps custom domain A custom hostname assigned to a Container App ingress endpoint. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps environment variable An environment variable passed into a Container Apps container. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps ingress The Container Apps setting that controls whether and how HTTP or TCP traffic reaches a container app. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps replica a running instance of a Container Apps revision that is added or removed as Azure Container Apps scales the workload Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps session an isolated, short-lived execution environment from a Container Apps dynamic session pool, often used for sandboxed code or custom runtime tasks Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps traffic split percentage-based Container Apps ingress routing that sends traffic to active revisions or labels for canary, blue-green, or A/B releases Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps workload profile the Container Apps environment compute profile that controls resource size, scaling model, isolation, and billing behavior for deployed apps Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Container Apps job A Container Apps resource for running scheduled, event-driven, or manual containerized tasks to completion. Azure Container Apps intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Logical partition A logical partition in Azure Cosmos DB is the group of items that share the same partition key value inside a container, forming the unit Azure uses to organize storage, route requests, and enforce important scale limits in governed production environments. Azure Cosmos DB intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Containers verified Container Apps certificate A certificate used for TLS on a Container Apps custom domain. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers verified Container Apps exec An interactive command execution feature for a running Container App replica. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers verified Container Apps log stream A live log stream for a Container App replica or revision. Azure Container Apps intermediate 5 commands Aliases: No aliases yet 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

Containers field-manual-complete Container Apps revision Microsoft Learn explains that a Container Apps revision is created at first deployment and whenever revision-scope settings change. Revision mode controls whether one or multiple revisions stay active, enabling traffic splitting, labels, rollbacks, and safer updates without changing the whole container app resource. in controlled production releases. Azure Container Apps intermediate 5 commands Aliases: Container Apps revision, active-revision, container apps revision, container-app-environment, container-apps, container-apps-ingress, container-apps-revision, container-apps-traffic-split, container-image, container-image-digest, deployment-labels, deployment-slot, inactive-revision, keda Quick peek Open full term page

Containers field-manual-complete Container Apps scale rule A Container Apps scale rule tells Azure Container Apps when to run more or fewer replicas of an app revision. Instead of guessing capacity manually, you define a trigger such as HTTP concurrency, CPU, memory, Service Bus messages, Kafka lag, or another KEDA-supported event source. The rule works with minimum and maximum replica limits, so. Azure Container Apps intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page