Search Azure terms

Identity premium Microsoft Entra ID Microsoft Entra ID is the cloud identity platform that stores tenant identities and provides authentication, authorization, application registration, and access governance for Azure. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Identity platform fundamentals 4 commands Aliases: Entra ID, Azure Active Directory, Azure AD, AAD Quick peek Open full term page

Databases premium Microsoft Entra admin for SQL Microsoft Entra admin for SQL is the Microsoft Entra identity designated to administer an Azure SQL logical server or SQL Managed Instance through Entra authentication. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Azure SQL identity intermediate 4 commands Aliases: Azure SQL Entra admin, Azure AD admin for SQL, SQL Entra administrator Quick peek Open full term page

Databases premium Microsoft Entra authentication for SQL Microsoft Entra authentication for SQL is the use of Microsoft Entra identities to authenticate to Azure SQL Database, SQL Managed Instance, or related SQL resources. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Azure SQL identity intermediate 4 commands Aliases: Azure SQL Entra authentication, Azure AD authentication for SQL, SQL Entra auth Quick peek Open full term page

Identity premium Microsoft Entra group Entra group means a Microsoft Entra ID group object used to manage membership, access assignments, application permissions, and governance workflows as a unit. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Directory groups intermediate 4 commands Aliases: Entra group, Azure AD group, directory group Quick peek Open full term page

Databases complete SQL Microsoft Entra authentication Microsoft Learn describes Microsoft Entra authentication for Azure SQL as using identities from Microsoft Entra ID to authenticate to Azure SQL Database, Azure SQL Managed Instance, Synapse SQL, and related SQL platforms. It supports users, groups, applications, and managed identities while database permissions still control authorization. Azure SQL security and identity intermediate 5 commands Aliases: Azure SQL Entra authentication, Microsoft Entra authentication for Azure SQL, Azure AD authentication for SQL, Entra ID SQL authentication 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

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 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

Identity premium Object ID An Object ID is the unique ID for a specific thing inside Microsoft Entra ID. That thing might be a user, group, service principal, managed identity, or enterprise application object. It is not the friendly display name, and it is not always the same as an application client ID. In Azure operations, the Object ID is the value people often need when assigning RBAC roles, checking ownership, troubleshooting identity, or proving exactly which principal was granted access. Microsoft Entra fundamentals 5 commands Aliases: No aliases yet 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

Identity premium Client ID A client ID is the application identifier assigned to an app registration by Microsoft Entra ID. Microsoft Learn describes the Application, or client, ID as the value that uniquely identifies an application in the Microsoft identity platform across tenants and clouds. Applications fundamentals 4 commands Aliases: No aliases yet 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 Microsoft 365 group Microsoft 365 group is a collaboration-backed group object in Microsoft Entra ID used for shared membership across Microsoft 365 resources and some Azure access patterns. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Microsoft Entra ID fundamentals 4 commands Aliases: M365 group, Office 365 group, Microsoft 365 collaboration group Quick peek Open full term page

Management and Governance premium Microsoft Purview account Microsoft Purview account is the Azure resource boundary for Microsoft Purview data governance, catalog, scanning, classification, lineage, and policy workflows. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. Data governance intermediate 4 commands Aliases: Purview account, Microsoft Purview governance account, Azure Purview account 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 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

Security top-250-pre130-priority-upgraded Microsoft Sentinel Microsoft Sentinel means Microsoft cloud SIEM and SOAR service for collecting security signals, detecting threats, investigating incidents, and automating response. Teams should manage it with clear ownership, monitoring, rollback evidence, and production change discipline. SIEM and SOAR fundamentals 4 commands Aliases: Sentinel, Azure Sentinel, Microsoft Sentinel SIEM Quick peek Open full term page

Integration premium Service Bus authorization rule Service Bus authorization rule is a shared access policy on a namespace, queue, or topic. It names a key pair and grants Listen, Send, or Manage rights, letting applications create SAS tokens or connection strings scoped to the messaging entity they are allowed to use. Service Bus fundamentals 6 commands Aliases: Service Bus SAS policy, Service Bus shared access policy, Service Bus authorization policy, SAS authorization rule Quick peek Open full term page

Identity premium Service principal A service principal is the local Microsoft Entra identity for an application or automation instance in a tenant. It represents the app for sign-in, consent, and authorization, and it can receive Azure RBAC roles or API permissions without using a human user account. Azure identity fundamentals 6 commands Aliases: Microsoft Entra service principal, Service principal, application service principal, automation identity, service principal, service-principal Quick peek Open full term page

Analytics premium Synapse SQL administrator A Synapse SQL administrator is the Synapse RBAC role focused on serverless SQL access and SQL artifacts. It grants broad serverless SQL pool permissions plus create, read, update, and delete access to published SQL scripts, credentials, and linked services within a workspace. Synapse Analytics intermediate 6 commands Aliases: Synapse SQL Administrator, Synapse SQL admin, SQL administrator in Synapse, Synapse SQL admin role Quick peek Open full term page

Identity premium App registration An app registration is the identity profile for an application, not the application code itself. It tells Microsoft Entra ID how the app is allowed to sign in users or request tokens. It contains values developers copy into configuration, such as client ID, tenant, redirect URI, credentials, and permissions. When sign-in breaks, consent fails, or tokens contain the wrong audience, the app registration is often where engineers look first. It is the contract between the app, Entra ID, administrators, and downstream APIs. Applications fundamentals 5 commands Aliases: Microsoft Entra app registration, application registration Quick peek Open full term page

Web premium App Service authentication provider An identity provider configured in App Service Authentication, such as Microsoft Entra ID, that handles user sign-in for the app. It helps learners understand where the concept appears in Azure operations and what to verify before changing it. App Service intermediate 5 commands Aliases: app service authentication provider, authentication provider Quick peek Open full term page

Analytics premium Azure Databricks Unity Catalog A unified governance layer in Azure Databricks for data and AI assets, including catalogs, schemas, tables, volumes, models, privileges, and lineage. Data governance intermediate 5 commands Aliases: Unity Catalog Quick peek Open full term page

DevOps premium Azure DevOps organization The top-level Azure DevOps Services container that connects related projects, users, repositories, pipelines, artifacts, permissions, and organization settings. Azure DevOps fundamentals 5 commands Aliases: Azure DevOps org Quick peek Open full term page

Identity premium Azure tenant An Azure tenant is the Microsoft Entra directory that provides identity and access management for users, groups, applications, service principals, devices, and Azure resources associated with an organization. Azure identity fundamentals 5 commands Aliases: tenant, Microsoft Entra tenant, tenant ID Quick peek Open full term page

Integration premium Event Hubs SAS policy An Event Hubs SAS policy is an authorization rule with shared keys and permissions that can produce SAS tokens or connection strings for Event Hubs access. Teams use it to grant time-bound or key-based Event Hubs access when Microsoft Entra ID is not practical for a producer or consumer. It is not a managed identity, RBAC assignment, Key Vault secret by itself, or a safe replacement for least-privilege access review. In production, confirm the namespace, event hub, partitions, identity, network path, consumer groups, checkpoints, metrics, owner, and rollback plan before treating the stream design as healthy. Event Hubs intermediate 5 commands Aliases: shared access signature policy, SAS authorization rule, Event Hubs access policy Quick peek Open full term page

Identity premium Admin consent Admin consent is a Microsoft Entra approval that grants an application requested permissions, often tenant-wide, to access protected resources. In everyday Azure work, teams use it to approve SaaS apps, internal applications, or multi-tenant integrations that need permissions users cannot safely grant themselves. The useful evidence is application ID, service principal, requested scopes or app Microsoft Entra ID intermediate 4 commands Aliases: tenant-wide admin consent, application permission consent, Entra admin consent Quick peek Open full term page

Storage premium AzCopy AzCopy is the Microsoft command-line utility used to move data into, out of, and between Azure Storage services such as blobs and file shares. In Azure, teams encounter it when storage teams migrate data, seed analytics lakes, copy backups, or synchronize large folders without writing a custom transfer program. The useful question is what behavior Blob Storage fundamentals 4 commands Aliases: AzCopy v10, Azure Storage AzCopy, azcopy copy, azcopy sync Quick peek Open full term page

Identity premium Client secret A client secret is a password-style credential added to an app registration so a confidential application can authenticate to Microsoft Entra ID. Microsoft Learn recommends managing credentials carefully and also supports certificates and federated credentials for stronger automation patterns and rotation. Applications fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Storage premium Default ACL A default ACL in Azure Data Lake Storage Gen2 is an ACL entry on a directory that new child files and directories inherit when they are created under that directory. Data Lake Storage Gen2 intermediate 4 commands Aliases: default access control list, ADLS Gen2 default ACL, directory default ACL Quick peek Open full term page

Identity premium Delegated permission A delegated permission is a Microsoft identity platform permission that lets an application act on behalf of a signed-in user, limited by both the granted permission and the user’s own access. Identity operations intermediate 4 commands Aliases: OAuth delegated permission, Microsoft Graph delegated permission, user delegated permission Quick peek Open full term page

Management and Governance premium Deny assignment A deny assignment is an Azure authorization control that blocks specified actions at a scope even when role assignments would otherwise grant access. Azure RBAC intermediate 4 commands Aliases: Azure deny assignment, RBAC deny assignment, system-protected deny assignment, Authorization deny assignment Quick peek Open full term page

Integration premium Developer portal The developer portal is the Azure API Management portal where API consumers discover APIs, read documentation, sign in, subscribe to products, retrieve subscription details, and test API operations when allowed. Application delivery and API edge intermediate 4 commands Aliases: API Management developer portal, APIM developer portal, developer portal in API Management, API consumer portal Quick peek Open full term page

Identity premium Directory A directory is the Microsoft Entra identity container associated with users, groups, applications, service principals, devices, and tenant-level identity configuration. Tenant identity fundamentals 4 commands Aliases: Microsoft Entra directory, tenant directory, identity directory, Azure AD directory Quick peek Open full term page

Identity premium Directory role A directory role grants permissions to manage Microsoft Entra tenant resources such as users, groups, applications, devices, roles, and security settings. Privileged access intermediate 4 commands Aliases: Microsoft Entra role, administrator role, Entra directory role, tenant administrator role Quick peek Open full term page

Storage premium Disable Shared Key authorization Disable Shared Key authorization is a storage account setting that prevents requests from being authorized with account keys and pushes supported access toward Microsoft Entra authorization. Storage security intermediate 4 commands Aliases: disallow Shared Key, AllowSharedKeyAccess false, prevent Shared Key access, disable storage account key access Quick peek Open full term page

Web premium Easy Auth Easy Auth is the built-in authentication and authorization capability in Azure App Service and Azure Functions for signing in users with identity providers such as Microsoft Entra. App Service security fundamentals 4 commands Aliases: App Service Authentication, App Service built-in authentication Quick peek Open full term page

Identity premium Eligible assignment An eligible assignment grants a user or principal the ability to activate a privileged Microsoft Entra or Azure RBAC role when needed instead of holding it permanently. Privileged access intermediate 4 commands Aliases: PIM eligible assignment, eligible role assignment Quick peek Open full term page

Identity premium Enterprise application Enterprise application properties in Microsoft Entra ID configure the organization-specific service principal settings for an application, including user assignment, single sign-on, provisioning, and ownership. Microsoft Entra applications intermediate 4 commands Aliases: Entra enterprise application, service principal application, enterprise app Quick peek Open full term page

Identity premium Entitlement management Entitlement management uses access packages to govern access to groups, applications, SharePoint sites, and other resources for internal and external identities. Identity Governance intermediate 4 commands Aliases: Microsoft Entra entitlement management, Entra entitlement management, access package governance Quick peek Open full term page

Identity premium Group A Microsoft Entra group is an identity object that collects users, devices, service principals, or other groups so access, collaboration, or administration can be managed together. Microsoft Entra fundamentals 4 commands Aliases: Microsoft Entra group, security group, Microsoft 365 group Quick peek Open full term page

Identity premium Guest user A guest user is an external identity invited into a Microsoft Entra tenant so a partner, contractor, or external collaborator can access approved resources. External identities fundamentals 4 commands Aliases: B2B guest user, external guest user, Microsoft Entra guest Quick peek Open full term page

Identity premium Log Analytics Data Reader A Log Analytics Data Reader assignment is an Azure built-in RBAC role for letting approved users, groups, or workload identities query the Log Analytics logs they are allowed to view across workspaces and tables without granting workspace administration, table management, or broader monitoring control. Azure RBAC fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Identity premium Multifactor authentication Multifactor authentication means a Microsoft Entra sign-in control that requires two or more verification factors before access is granted. You see it when teams protect Azure portal access, privileged roles, risky sign-ins, and sensitive applications from password-only compromise. Think of it as stronger proof of user identity during sign-in, not a replacement for least privilege or role review. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Access control fundamentals 4 commands Aliases: MFA Quick peek Open full term page

Identity premium Break-glass account A break-glass account is an emergency access account reserved for tenant recovery when normal administrative sign-in or Conditional Access paths fail. Privileged access fundamentals 3 commands Aliases: emergency access account Quick peek Open full term page

Identity premium Consent grant the Microsoft Entra permission approval that lets an application call an API with delegated user scopes or application roles Identity operations fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

Analytics field-manual-complete Synapse role A Synapse role is a workspace-level RBAC permission set that controls what users, groups, managed identities, and service principals can do inside Azure Synapse Analytics. Synapse RBAC governs workspace artifacts and actions, while Azure RBAC controls management of the Azure resources. Synapse Analytics intermediate 8 commands Aliases: Azure Synapse role, Synapse RBAC role, Synapse workspace role, Synapse access role Quick peek Open full term page