Search Azure terms

Management and Governance premium Global resource Global resource is an Azure resource or service configuration whose behavior is global or nonregional instead of being deployed as a normal workload in one Azure region. Teams use it to understand why resources such as Azure Front Door, DNS-related services, or tenant-level identity features do not behave like regional compute or storage resources. In daily Azure work, it shows up when engineers choose a resource group location for metadata, design global routing, review service availability, explain compliance scope, or troubleshoot why a regional outage affects dependencies differently. Azure Resource Manager intermediate 4 commands Aliases: nonregional Azure resource, global Azure resource, Azure global service resource Quick peek Open full term page

Networking field-manual-complete Traffic Manager Azure Traffic Manager is a DNS-based traffic-routing service that directs clients to healthy application endpoints according to a configured routing method. It monitors endpoints and returns DNS answers, but it is not a proxy, so client traffic flows directly to the selected endpoint. Global routing intermediate 5 commands Aliases: Azure Traffic Manager, DNS traffic routing, traffic manager profile, global DNS routing, DNS failover Quick peek Open full term page

AI and Machine Learning field-manual-ready Model deployment type Model deployment type describes the hosting, traffic, region, and billing pattern used when a model is made available for inference. AI platform and search intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Networking premium Application Gateway routing rule the Application Gateway component that connects a listener to a backend pool, backend settings, redirect, or path-based routing decision. Application delivery and API edge intermediate 4 commands Aliases: Application Gateway routing rule, application gateway routing rule Quick peek Open full term page

Analytics premium Data Factory global parameter A factory-level constant that pipelines can reference in expressions and that CI/CD can override per environment. Data integration and orchestration Intermediate 4 commands Aliases: Data Factory global parameter, ADF global parameter, data factory global parameter Quick peek Open full term page

Identity premium Global Administrator Global Administrator is the highest-impact Microsoft Entra administrator role most tenants use, with broad authority over directory settings, users, applications, roles, and cross-service administration. Teams use it to perform rare tenant-level administration, recover from access emergencies, manage privileged identity settings, and approve sensitive directory changes. In daily Azure work, it shows up when engineers review privileged role assignments, configure PIM, investigate tenant takeover risk, elevate access for Azure resource recovery, or audit emergency accounts. Review owner, scope, evidence, dependencies, and rollback before production change. Privileged access advanced 4 commands Aliases: Global Admin, Microsoft Entra Global Administrator, tenant global administrator Quick peek Open full term page

Databases premium Global distribution Global distribution is the Azure Cosmos DB capability that replicates an account across multiple Azure regions so applications can read or write closer to users depending on configuration. Teams use it to improve low-latency access, support regional failover, place replicas near customers, and design globally available NoSQL applications. In daily Azure work, it shows up when engineers add or remove Cosmos DB regions, set failover priorities, enable multi-region writes, tune consistency, or investigate latency by user geography. Azure Cosmos DB advanced 4 commands Aliases: Cosmos DB global distribution, multi-region distribution, globally distributed database Quick peek Open full term page

Analytics premium Global parameter Global parameter is a Data Factory value defined once at the factory level so multiple pipelines can reference the same environment or configuration setting. Teams use it to avoid hardcoding repeated values such as storage containers, environment names, control-table names, feature flags, or standard paths across many pipelines. In daily Azure work, it shows up when engineers author pipeline expressions, promote factories through CI/CD, override values per environment, debug parameterized datasets, or troubleshoot missing deployment parameters. Data Factory beginner 4 commands Aliases: ADF global parameter, Data Factory global parameter, factory global parameter 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

Networking premium Front Door Azure Front Door is Microsoft’s global edge service for modern web applications. Microsoft Learn describes it as a cloud CDN that provides fast, reliable, and secure access to static and dynamic content through Microsoft’s global edge network worldwide. Application delivery and API edge intermediate 5 commands Aliases: Azure Front Door, AFD, Azure Front Door Standard, Azure Front Door Premium, global edge Quick peek Open full term page

Networking premium Front Door profile Front Door profile is the top-level Azure Front Door Standard or Premium resource that groups edge endpoints, routes, origins, domains, rule sets, security associations, and delivery settings. Teams use it to manage a global application entry point without treating each endpoint, route, or origin as a separate product. In daily Azure work, it shows up when engineers review edge architecture, add a new website, tune routing, attach custom domains, configure WAF, or troubleshoot global traffic. It is not the same thing as a single endpoint, DNS name, backend app, CDN cache rule, or web application firewall policy. Application delivery and API edge intermediate 5 commands Aliases: Azure Front Door profile, AFD profile, Front Door Standard/Premium profile Quick peek Open full term page

Networking premium Front Door endpoint A Front Door endpoint is a logical grouping of one or more routes associated with domain names in an Azure Front Door profile. Application delivery and API edge intermediate 4 commands Aliases: Azure Front Door endpoint, AFD endpoint, azurefd.net endpoint 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

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

Identity learning-path-anchor Tenant ID A tenant ID is the globally unique identifier for a Microsoft Entra tenant. Microsoft Entra fundamentals 4 commands Aliases: Tenant ID, tenant id, Azure Tenant ID, Microsoft Entra tenant ID, directory ID, tenantId Quick peek Open full term page

Management and Governance learning-path-anchor Tenant root group The tenant root group is the highest management group scope associated with a Microsoft Entra tenant. Management groups fundamentals 4 commands Aliases: Tenant root group, tenant root group, Azure Tenant root group, root management group, root group Quick peek Open full term page

Databases learning-path-anchor Cosmos DB dedicated gateway Azure Cosmos DB dedicated gateway is provisioned server-side compute that fronts an account and enables the integrated cache for supported NoSQL workloads. Azure Cosmos DB fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

App platform complete Static Web App Microsoft Learn describes Azure Static Web Apps as a service that automatically deploys full-stack web apps from a source repository. It serves static assets from globally distributed locations, integrates optional APIs, supports GitHub or Azure DevOps workflows, and provides routing, authentication, staging environments, and CLI support. Static Web Apps intermediate 5 commands Aliases: static-web-app, Static Web App, Azure Static Web Apps, SWA, static web app resource, staticwebapp Quick peek Open full term page

App platform complete Static Web Apps configuration Microsoft Learn describes Static Web Apps configuration as the staticwebapp.config.json file used to control routing and application behavior. It defines route rules, authorization requirements, response overrides, custom headers, navigation fallback, networking settings, and other global behavior for an Azure Static Web Apps site. Static Web Apps advanced 5 commands Aliases: static-web-apps-configuration, Static Web Apps configuration, staticwebapp.config.json, Static Web Apps config file, SWA configuration, routes configuration Quick peek Open full term page

Databases command-rich Cosmos DB for Apache Cassandra Azure Cosmos DB for Apache Cassandra is a managed NoSQL database service that supports Cassandra workloads using CQL, drivers, and compatible tooling. Data platform intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases command-rich Cosmos DB for Table Azure Cosmos DB for Table is a managed NoSQL key-value and table API compatible with Azure Table storage SDKs and tools. Data platform intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Integration complete API Management policy An API Management policy is a rule the gateway runs while handling an API call. Policies can validate tokens, add or remove headers, rewrite URLs, limit rates, cache responses, transform payloads, choose a backend, or return a custom response. They are written as ordered XML statements and can. Application delivery and API edge intermediate 4 commands Aliases: APIM policy, API policy in API Management Quick peek Open full term page

Integration premium Event subscription An Event subscription is an Event Grid configuration that selects events from a source and delivers matching events to a destination endpoint. Teams use it to route storage, resource, custom, or partner events to the correct webhook, function, queue, topic, or event handler. It is not the event source itself, an Azure subscription, an Event Hubs consumer group, or proof that the destination successfully processed every event. In production, confirm source scope, event types, filters, endpoint URL or resource ID, authentication method, dead-letter destination, retry settings, diagnostic logs, and receiving application owner before treating the design as healthy or ready. Event Grid intermediate 6 commands Aliases: Event Grid subscription, event routing subscription, event delivery subscription Quick peek Open full term page

Networking premium ExpressRoute ExpressRoute lets organizations extend on-premises networks into Microsoft cloud services over private connectivity provided through a connectivity provider. Teams use it to connect datacenters, branches, or colocation environments to Azure with predictable private paths for workloads that need stronger latency, bandwidth, and routing control than public internet connections. It is not a VPN tunnel, a private endpoint, an internet performance guarantee, or proof that every connected application is secure, redundant, or correctly routed. In production, confirm circuit state, provider state, peering configuration, BGP routes, gateway SKU, connected virtual networks, bandwidth, metrics, DNS path, firewall path, and provider escalation details before. Hybrid connectivity intermediate 6 commands Aliases: Azure ExpressRoute, ExpressRoute circuit, private Microsoft cloud connectivity Quick peek Open full term page

Integration premium Service Bus Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. It helps decouple applications and services, load-balance work across competing consumers, route data across boundaries, and coordinate transactional workflows that require reliable messaging, ordering, sessions, duplicate detection, and dead-letter handling. Messaging fundamentals 6 commands Aliases: Azure Service Bus, Service Bus Messaging Quick peek Open full term page

Networking premium Web Application Firewall Azure Web Application Firewall is a centralized protection service for HTTP applications. It can run with Application Gateway, Front Door, Application Gateway for Containers, or Azure CDN, using managed and custom rules to detect and block common exploits such as SQL injection and cross-site scripting. Application security fundamentals 6 commands Aliases: WAF, Azure WAF, Application Gateway WAF, Front Door WAF 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

Databases premium Active geo-replication Active geo-replication is an Azure SQL Database business-continuity feature that continuously replicates one primary database to a readable secondary database, often in another Azure region. It supports manual or programmatic geo-failover for individual databases and can also serve read-only workloads from the secondary. Azure SQL continuity advanced 5 commands Aliases: Azure SQL active geo-replication, geo-secondary, geo-replica Quick peek Open full term page

Containers premium AKS ingress controller Microsoft Learn explains AKS ingress through Kubernetes ingress resources and controllers that route HTTP or HTTPS traffic to services in a cluster. AKS application routing options can configure ingress controllers, DNS integration, TLS handling, and related networking components for production applications. AKS networking intermediate 5 commands Aliases: AKS ingress, Ingress controller for AKS, Kubernetes ingress controller Quick peek Open full term page

Web premium App Service VNet integration Microsoft Learn describes App Service virtual network integration as the feature that lets an App Service app access resources in or through an Azure virtual network. It affects outbound traffic from the app; inbound private access uses other controls, such as private endpoints and access restrictions. App Service Networking intermediate 5 commands Aliases: App Service virtual network integration, regional VNet integration, Web App VNet integration Quick peek Open full term page

AI and Machine Learning premium Batch deployment A batch deployment in Azure Machine Learning is the deployment configuration behind a batch endpoint, defining the model or pipeline, compute, environment, and execution behavior for asynchronous inference. Azure Machine Learning intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

DevOps premium Canary deployment Canary deployment is a release approach that sends a small portion of real traffic to a new version before rolling it out broadly. Deployment workflows 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

Databases premium Cosmos DB account Design the account boundary for a global application before choosing databases, containers, regions, consistency, and backup mode.; Separate regulated, tenant-specific, or production workloads into dedicated Cosmos DB ac Database intermediate 5 commands Aliases: Cosmos DB account, cosmos db account Quick peek Open full term page

Databases premium Cosmos DB partition key value Cosmos DB partition key value means the actual value stored on an item for the configured partition key path in Azure Cosmos DB. In plain English, it is the thing developers and operators check when they need to understand how data access really works. It connects the application model to routing items into logical partitions, enabling efficient point reads, transactional scope, and balanced throughput. For a production team, it turns vague database talk into a specific thing to inspect in the portal, SDK code, templates, metrics, and incident notes. Azure Cosmos DB intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Cosmos DB Table API Cosmos DB Table API is the Cosmos DB API that supports applications written for Azure Table Storage-style key-value tables with Cosmos DB capabilities. It lets teams keep a familiar table model while using Cosmos DB account management, global distribution, throughput, and monitoring. You see it when applications use PartitionKey and RowKey entities, Azure Table SDKs, or migrations from Azure Table Storage. The production check is whether the table access pattern, partition key, throughput model, and consistency expectations fit Cosmos DB rather than basic storage tables. Document the decision in code, templates, metrics, and runbooks. Azure Cosmos DB intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Analytics premium Databricks workspace VNet injection Databricks workspace VNet injection is the deployment model that places Azure Databricks compute resources into customer-managed virtual network subnets so network security, routing, and private connectivity controls can be applied. Databricks advanced 5 commands Aliases: VNet-injected Databricks workspace, customer-managed VNet workspace, Databricks VNet injection, workspace in customer VNet Quick peek Open full term page

Analytics premium Dataset parameter A dataset parameter is a named value on a Data Factory or Synapse dataset that lets pipelines pass runtime information such as folder, file, schema, table, or partition values into a reusable dataset definition. Data engineering and analytics intermediate 5 commands Aliases: ADF dataset parameter, Data Factory dataset parameter, parameterized dataset, dataset runtime value 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 Grid custom topic Event Grid custom topic is a user-created Azure Event Grid topic that gives custom applications an endpoint for publishing business or application events. In Azure, it shows up when custom applications publish shipment, order, payment, device, or workflow events that subscribers need to process independently. Teams use it to review topic name, region, access keys or managed identity options, input schema, event subscriptions, filters, retry policy, dead-letter destination, and monitoring before changing production behavior. It is not an Azure system topic, Event Grid domain, Event Hub, or Service Bus topic. Event routing intermediate 5 commands Aliases: Azure Event Grid custom topic, custom Event Grid topic Quick peek Open full term page

Integration premium Event Grid dead-letter destination Event Grid dead-letter destination is a storage destination used by Azure Event Grid for events that cannot be delivered after retry or configuration handling. In Azure, it shows up when an event subscription needs a recoverable place for undelivered events instead of silently losing operational evidence. Teams use it to review event subscription dead-letter settings, storage account, blob container, identity or access method, retry policy, monitoring, retention, and processing runbook before changing production behavior. It is not a Service Bus dead-letter queue, handler retry loop, poison-message table, or general logging sink. Event routing intermediate 5 commands Aliases: Event Grid dead letter destination, Event Grid dead-letter storage Quick peek Open full term page

Integration premium Event Grid delivery retry Event Grid delivery retry is the Event Grid behavior that retries event delivery when a subscriber endpoint temporarily fails or returns retryable responses. In Azure, it shows up when handlers may be unavailable, slow, throttled, or temporarily blocked, but events still need controlled redelivery before dead-lettering or expiration. Teams use it to review maximum delivery attempts, event time-to-live, endpoint response behavior, dead-letter destination, subscription filters, monitoring, and handler readiness before changing production behavior. It is not application-level retry code, Service Bus lock renewal, Event Hubs checkpointing, or a guaranteed infinite replay mechanism. Event routing intermediate 5 commands Aliases: Event Grid retry policy, Event Grid event retry Quick peek Open full term page

Integration premium Event Grid delivery schema Event Grid delivery schema is the event format Azure Event Grid uses when sending an event to a subscriber endpoint. In Azure, it shows up when publishers and handlers must agree on whether delivered events use Event Grid schema, CloudEvents v1.0, or a custom input schema shape. Teams use it to review event subscription delivery schema, publisher input schema, handler parser, API contract, sample payloads, validation tests, filters, and compatibility monitoring before changing production behavior. It is not the handler destination type, the event source, a JSON schema registry, or the business data model itself. Event routing intermediate 5 commands Aliases: Event Grid event delivery schema, event delivery schema Quick peek Open full term page

Integration premium Event Grid domain Event Grid domain is an Event Grid resource that provides one publishing endpoint for many related domain topics in a large or multi-tenant event solution. In Azure, it shows up when a platform needs to manage thousands of related topics, tenant-specific subscriptions, or application-specific event streams without creating unrelated standalone topics. Teams use it to review domain endpoint, domain topics, access keys or identity controls, event subscriptions, RBAC, filters, publishing application logic, metrics, and tenant ownership model before changing production behavior. It is not a DNS custom domain, Event Grid namespace custom hostname, single custom topic, or Service Bus namespace. Event routing advanced 5 commands Aliases: Azure Event Grid domain, event domain Quick peek Open full term page

Integration premium Event Grid event handler Event Grid event handler is the destination endpoint or Azure service that receives matching events from an Event Grid event subscription and acts on them. In Azure, it shows up when an event-driven workflow needs a function, logic app, webhook, queue, topic, event hub, storage queue, relay connection, or namespace topic to process events. Teams use it to review handler type, endpoint URL or resource ID, authentication method, validation handshake, managed identity permissions, retry behavior, dead-lettering, monitoring, and scaling plan before changing production behavior. It is not the event publisher, Event Grid topic, event schema, or the business event itself. Event routing fundamentals 5 commands Aliases: Event Grid handler, Event Grid destination Quick peek Open full term page

Integration premium Event Grid event schema Event Grid event schema is the JSON structure used to describe an Event Grid event, including metadata and the event data payload sent to subscribers. In Azure, it shows up when publishers, subscribers, filters, and handlers need a shared contract for fields such as id, subject, event type, event time, data, and versioning. Teams use it to review publisher payload format, custom topic input schema, subscription delivery schema, event type names, subject conventions, dataVersion, sample payloads, and handler parser tests before changing production behavior. It is not a database schema, full OpenAPI definition, handler endpoint, or Event Grid subscription. Event routing fundamentals 5 commands Aliases: Azure Event Grid schema, Event Grid schema Quick peek Open full term page

Integration premium Event Grid filter Event Grid filter is the matching configuration on an Event Grid event subscription that decides which events are delivered to a handler. In Azure, it shows up when subscribers should receive only relevant events based on event type, subject prefix or suffix, or advanced fields inside the event payload. Teams use it to review included event types, subject begins-with and ends-with filters, advanced filters, case sensitivity, schema field names, test payloads, and monitoring for matched events before changing production behavior. It is not a firewall rule, diagnostic query, handler-side if statement, or Azure Policy filter. Event routing intermediate 5 commands Aliases: Event Grid subscription filter, Event Grid event filter 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

Integration premium Event Grid MQTT broker An Event Grid MQTT broker is the MQTT publish-subscribe capability in Event Grid namespaces that authenticates clients, authorizes publish and subscribe requests, and routes MQTT messages between interested clients. Teams use it to connect MQTT clients, devices, and services through managed publish-subscribe messaging without running a separate broker platform. It is not a general Event Grid custom topic or an IoT Hub device registry replacement. 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 MQTT broker, MQTT broker in Event Grid namespaces Quick peek Open full term page