Search Azure terms

Internet of Things premium Device identity A device identity is the IoT Hub identity registry entry that represents a permitted device or module, including its device ID, authentication material, status, and connection-related metadata. IoT identity fundamentals 4 commands Aliases: IoT Hub device identity, IoT device registry identity, device registry entry, IoT device ID 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

Internet of Things premium IoT Edge IoT Edge is the Azure IoT runtime and deployment pattern that runs cloud-managed container modules on local edge devices while communicating with IoT Hub. Edge computing intermediate 5 commands Aliases: Azure IoT Edge, IoT Edge runtime, edge modules, edgeAgent, edgeHub, edge device Quick peek Open full term page

Internet of Things premium IoT Hub IoT Hub is the managed Azure service that provides secure, bidirectional communication between IoT applications and their connected devices at scale. Device messaging intermediate 5 commands Aliases: Azure IoT Hub, device-to-cloud messaging, cloud-to-device messaging, IoT message hub, IoT Hub endpoint 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

Identity premium Federated identity credential A Federated identity credential is a Microsoft Entra credential object that defines the issuer, subject, and audience trusted for workload identity federation. Teams use it to allow a specific external workload identity to authenticate as an Entra application or user-assigned managed identity without storing a client secret or certificate. It is not a role assignment, token issued by Azure, user sign-in method, broad trust for every workflow in a repository, or evidence that the workload can access resources without RBAC. Workload identity intermediate 6 commands Aliases: Microsoft Entra federated identity credential, FIC, workload identity credential, OIDC federation credential 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

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

Containers premium Kubelet identity Kubelet identity controls how AKS nodes authenticate to Azure resources for node-level tasks, especially pulling container images from registries without embedded secrets. Teams see it in aks identity profile, node pools. It is not cluster control-plane identity, workload identity, pod managed identity, service account token, kubeconfig credential, or container registry admin user; confusing them can create image pull failures, overbroad registry access. 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. AKS identity Intermediate 5 commands Aliases: AKS kubelet identity, node pool kubelet identity, AKS node managed identity, identityProfile kubeletidentity 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

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

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

Identity premium Identity Governance Identity Governance is a Microsoft Entra set of capabilities for managing identity lifecycle, access lifecycle, access reviews, entitlement management, and privileged access. Identity operations intermediate 4 commands Aliases: Entra ID Governance, identity governance, Identity Governance, Microsoft Entra Identity Governance Quick peek Open full term page

Identity premium Identity Protection Identity Protection is a Microsoft Entra capability that detects, investigates, and helps remediate risky users and risky sign-ins. Security intermediate 4 commands Aliases: Entra ID Protection, identity protection, Identity Protection, identity risk protection, Microsoft Entra ID Protection 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

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

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

Identity verified Workload identity A workload identity is an identity assigned to software, such as an application, service, script, or container, so it can authenticate to Microsoft Entra protected resources. In Azure, examples include app registrations, service principals, managed identities, and federated workload identities. Workload identity fundamentals 6 commands Aliases: No aliases yet Quick peek Open full term page

Containers field-manual-complete AKS workload identity AKS workload identity lets a pod sign in to Azure as an approved identity without storing a password, client secret, or long-lived key inside the container. You connect a Kubernetes service account to a Microsoft Entra application or managed identity through federation. When the pod runs, Azure trusts the service account token from the cluster OIDC issuer and issues access tokens for allowed resources. The result is cleaner secret handling for applications running in AKS. AKS Identity intermediate 5 commands Aliases: Microsoft Entra Workload ID for AKS, pod workload identity, AKS OIDC federation Quick peek Open full term page

Identity field-manual-complete Privileged Identity Management Privileged Identity Management, usually called PIM, is the Microsoft Entra feature that keeps powerful access from being permanently active unless someone really needs it. Access control fundamentals 5 commands Aliases: PIM Quick peek Open full term page

Identity verified Resource identity A resource identity is the Azure identity a workload uses when it needs permission to call another service. Most teams see it as a system-assigned or user-assigned managed identity on a VM, App Service, Function, container app, automation account, or data service. Instead of storing a password or client secret, the resource receives a Microsoft Entra identity and uses tokens. Operators then grant that identity roles on Key Vault, Storage, SQL, Cosmos DB, or other dependencies. Identity operations fundamentals 5 commands Aliases: Workload identity for a resource, Managed identity surface 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

Compute verified VM system-assigned identity VM system-assigned identity is a Microsoft Entra managed identity created directly on an Azure virtual machine. Azure manages its credentials, ties its lifecycle to that VM, and lets the guest request tokens for authorized Azure resources without storing secrets in code. Virtual Machines intermediate 5 commands Aliases: VM system-assigned identity, vm system-assigned identity Quick peek Open full term page

Compute verified VM user-assigned identity VM user-assigned identity is a reusable managed identity resource attached to a virtual machine so software on that VM can request Microsoft Entra tokens without stored credentials. Its lifecycle and permissions are managed separately from the VM across rebuilds and fleets. Virtual Machines intermediate 5 commands Aliases: VM user-assigned managed identity, user-assigned managed identity for virtual machines, virtual machine user-assigned identity, managed identity attached to VM Quick peek Open full term page

Identity verified Workload identity federation Workload identity federation lets an external workload exchange a trusted token for Microsoft Entra access tokens without storing long-lived secrets. Microsoft Entra validates the issuer, subject, and audience in a federated credential, then allows automation such as GitHub Actions, Kubernetes, or other platforms to access protected resources. Identity operations fundamentals 5 commands Aliases: Federated workload identity, OIDC federation for workloads, Federated identity credential, Secretless workload authentication Quick peek Open full term page

Analytics learning-path-anchor Synapse Spark pool A Synapse Spark pool is the workspace compute definition Azure Synapse uses to start Apache Spark sessions. It records node size, node count, autoscale behavior, runtime version, packages, and idle timeout so notebooks, Spark jobs, and pipelines get repeatable distributed processing. Synapse Analytics fundamentals 8 commands Aliases: Apache Spark pool, Spark pool, Synapse Apache Spark pool, serverless Spark pool 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

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

Integration premium Event Grid system topic An Event Grid system topic represents one or more events published by an Azure service for a specific Azure resource or scope. Teams use it to subscribe to events emitted by Azure services such as Storage, Event Hubs, IoT Hub, Key Vault, or Resource Manager. It is not a custom topic where an application publishes its own events or a partner topic from an external provider. 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 system topic, system topic Quick peek Open full term page

Integration premium Event Hubs Azure Event Hubs is a fully managed, real-time data streaming platform for ingesting large volumes of events with low latency and routing them to consumers for processing. Teams use it to collect telemetry, application events, logs, clickstreams, and device data at scale before analytics, functions, or downstream services process them. It is not a queue for command messages, a workflow engine, a database, or an Event Grid routing topic for discrete platform events. In production, confirm the namespace, event hub, partitions, capacity, identity, network path, consumer group, checkpoint behavior, monitoring, and owner before treating the stream as safe. Event Hubs intermediate 5 commands Aliases: Azure Event Hubs, Azure Event Hubs service 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

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 learning-path-anchor Synapse Studio Synapse Studio is the browser-based workspace experience for Azure Synapse Analytics. It exposes hubs for data, development, integration, monitoring, and management, letting users author notebooks and SQL scripts, build pipelines, configure connections, review access, and work with Git-backed or live artifacts. Synapse Analytics fundamentals 6 commands Aliases: Azure Synapse Studio, Synapse web workspace, Synapse workspace UI, Synapse authoring experience Quick peek Open full term page

Analytics learning-path-anchor Synapse workspace firewall A Synapse workspace firewall is the IP allowlist around a Synapse workspace when it accepts public network traffic. It decides which client IPv4 ranges can attempt to connect before identity permissions are evaluated. It does not grant access by itself; a user or service still needs the right Azure, Synapse, or SQL permissions. It... Synapse Analytics intermediate 6 commands Aliases: Synapse IP firewall rule, workspace firewall rule, Synapse workspace IP allowlist, Synapse public endpoint firewall Quick peek Open full term page

Internet of Things premium Device Provisioning Service Device Provisioning Service is an Azure IoT helper service that enables zero-touch, just-in-time provisioning of devices to one or more linked IoT hubs using enrollments and allocation policies. IoT provisioning fundamentals 4 commands Aliases: Azure IoT Hub Device Provisioning Service, IoT DPS, DPS, zero-touch device provisioning Quick peek Open full term page

Internet of Things premium Device twin A device twin is the IoT Hub JSON document that stores device metadata, tags, desired properties, and reported properties so cloud applications and devices can synchronize configuration and state. Device state fundamentals 4 commands Aliases: IoT Hub device twin, device twin properties, twin desired properties, twin reported properties Quick peek Open full term page

Analytics learning-path-anchor Databricks metastore The top-level Unity Catalog container for catalogs, schemas, tables, volumes, models, functions, and governance permissions. Databricks intermediate 4 commands Aliases: Unity Catalog metastore, Databricks Unity Catalog metastore, metastore Quick peek Open full term page

Analytics learning-path-anchor Databricks secret scope A named Databricks collection of secrets used to store credentials and grant controlled read or manage access to workloads. Databricks fundamentals 4 commands Aliases: Databricks secrets scope, secret scope, Azure Databricks secrets Quick peek Open full term page

Storage learning-path-anchor Table schema-less design Table schema-less design means the table gives you a consistent place to store entities, but it does not force every entity to have the same application fields. One record can have Status and ExpirationUtc while another has RetryCount and Region. The required identity fields still matter, especially PartitionKey and RowKey. The design freedom is helpful, but it is not permission to ignore data contracts. Teams still need naming rules, versioning, validation, and reader behavior for missing or older properties. Table Storage fundamentals 4 commands Aliases: schema-less Table design, schemaless table design, Azure Table sparse schema, Table Storage flexible properties 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

AI and Machine Learning learning-path-anchor Text to speech Text to speech in Azure AI Speech converts written text or SSML into synthesized audio using neural voices, custom voice options, language support, and APIs. Teams use it to add spoken responses to apps, contact centers, accessibility tools, devices, and media workflows while governing region, keys, networking, and quota. Azure AI services fundamentals 4 commands Aliases: Text to speech, text to speech, Azure Text to speech, Microsoft Learn Text to speech, TTS, speech synthesis, Azure AI Speech synthesis, neural voices, SSML speech 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

Analytics command-rich Synapse workspace A Synapse workspace is the main container where a team builds and operates Azure Synapse Analytics. It gives the team one named place for SQL pools, Spark pools, pipelines, notebooks, linked services, access rules, monitoring, and the connection to the default data lake. The workspace is not just a folder in the portal; it... Analytics platform fundamentals 9 commands Aliases: Azure Synapse workspace, Synapse Analytics workspace, workspace in Azure Synapse, Synapse analytics boundary Quick peek Open full term page

AI and Machine Learning command-rich Search admin key A search admin key is one of the generated API keys for an Azure AI Search service that allows full read-write data-plane access. It can create, update, or delete indexes, indexers, data sources, and documents, so it must be protected, rotated, and replaced with role-based access when possible. Azure AI Search fundamentals 5 commands Aliases: Azure AI Search admin key, search service admin key, Azure Search API admin key, primary admin key, secondary admin key Quick peek Open full term page

Storage command-rich Table row key A Table row key is the unique name of an entity inside one Azure Table partition. PartitionKey gets you to the right group; RowKey identifies the exact record in that group. Together they form the entity primary key. RowKey design often carries an order ID, device ID, timestamp pattern, sequence number, or composite value. It matters because point reads, updates, deletes, duplicate detection, and... Storage platform intermediate 5 commands Aliases: Azure Table RowKey, Table Storage RowKey, Table row key value, RowKey property Quick peek Open full term page

Analytics field-manual-complete Stream Analytics job A Stream Analytics job is the thing that actually runs your real-time processing. You give it input sources, a SQL-like query, optional functions, output destinations, and capacity settings. When the job starts, it continuously reads events, applies the query logic, and pushes results somewhere useful. For a learner, think of the job as the streaming application container. For an operator, it is the Azure resource you start, stop, scale, monitor, troubleshoot, secure, and include in deployment automation. Streaming analytics fundamentals 5 commands Aliases: Stream Analytics job, Azure Stream Analytics job, ASA job, streaming job, real-time analytics job Quick peek Open full term page

Analytics verified Window function A window function in Azure Stream Analytics groups streaming events into time-based windows so queries can aggregate data across bounded periods. Tumbling, hopping, sliding, session, and snapshot windows let jobs calculate counts, averages, or patterns over event-time intervals rather than treating every event as isolated. Stream Analytics intermediate 5 commands Aliases: Stream Analytics window function, windowing function, temporal window, TumblingWindow, HoppingWindow Quick peek Open full term page

Databases command-rich Cosmos DB for Apache Gremlin Azure Cosmos DB for Apache Gremlin is a managed graph database service for storing, querying, and traversing graph data with the Gremlin language. Data platform intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page