Skip to content
Capabilities

NHI origins in Microsoft Azure tenants

Permafrost classifies collected Entra non-human identities using directory attributes. Origin helps analysts decide what to verify before changing access.

What an NHI is

A non-human identity is any directory principal that signs in without a person attached to it. Microsoft Entra surfaces three flavours.

  • Service principal. The tenant-local representation of an application. Holds credentials, role assignments, and consent grants. Created by an app registration in your tenant or by consenting to an external multi-tenant app.
  • Managed identity. A service principal whose credentials are provisioned and rotated by Azure. A system-assigned identity shares the lifecycle of its Azure resource. A user-assigned identity is a separate resource that can be attached to multiple workloads.
  • Agent identity. A principal provisioned by the Microsoft Entra Agent ID service for AI agents and copilots. Inherits permissions from a blueprint where inheritable permissions are configured.

Why origin matters

Origin helps you find the owner and related resources. Verify workload dependencies, active grants and available activity evidence before disabling an identity.

One concrete shape per identity type:

  • Review unexpected role assignments on Microsoft-owned service principals and check which services depend on them.
  • For a managed identity used by an AKS cluster, check which cluster operations and workloads depend on the identity before removing access.
  • For a third-party app with no recent sign-in observed, check collection coverage and confirm whether workloads still depend on the app before revoking consent.

The seven origin tiers

Permafrost uses the first matching tier for each collected NHI. The tier appears on the inventory row and on the identity detail page Lineage section.

Tier 1

Microsoft-managed

Signal. appOwnerOrganizationId matches Microsoft's tenant GUID and identityType is servicePrincipal.

Action. Leave alone unless the principal holds unexpected role assignments. Sign-in activity is not surfaced through tenant logs; a long-blank sign-in column is not dormancy.

Tier 2

Azure managed identity

Signal. identityType is managedIdentity. The Graph servicePrincipalType is ManagedIdentity.

Action. Use available Azure resource identifiers to check the identity's configuration and workload dependencies.

Tier 3

Entra agent identity

Signal. identityType is agentIdentity. The Graph servicePrincipalType is ServiceIdentity. Provisioned by the Entra Agent ID service.

Action. Treat the parent blueprint as the unit of governance. Sponsor the blueprint, set tier-aware policies, never disable individual agent rows.

Tier 4

Gallery SSO integration

Signal. applicationTemplateId is set on the SP, or the SP carries the Gallery primary tag.

Action. Review the SSO config in Entra Enterprise apps. Disable if the integration is no longer in use.

Tier 5

Registered in your tenant

Signal. appOwnerOrganizationId matches one of your connected tenants. The app registration lives inside your directory.

Action. Locate the app registration owner and review credentials and role assignments. Use the principal risk score to prioritize the review.

Tier 6

Third-party app (consented in)

Signal. appOwnerOrganizationId is set and matches neither Microsoft nor any of your connected tenants.

Action. Review the app's consent and dependencies in Entra Enterprise applications before deciding whether to revoke access.

Tier 7

Legacy / unattributed

Signal. No earlier rule matched. A service principal can fall into this tier when its owning organisation is unavailable.

Action. Investigate the app's origin, activity coverage, role assignments and credentials before changing access.

Examples to review

Use origin alongside observed role assignments, ownership and credentials to decide what to investigate.

  1. Third-party consented apps with privileged ARM RBAC. A multi-tenant app that received Owner or Contributor at the subscription scope. Permafrost surfaces these on the inventory row with the third-party origin badge plus the privileged-role chip. Review the role assignment and consent separately before making a change.
  2. Tenant-registered SPs with no known owner. For a tier 5 principal with no collected owner, check the app registration and verify who is responsible for its credentials.
  3. Legacy SPs with active credentials. For a tier 7 principal with collected credentials, verify who manages them and whether workloads depend on them.

How origin and UPR stay distinct

Origin classification covers the NHI population in Entra. The unused-permission factor of UPR covers ARM RBAC role assignments only, measured against the activity log. Microsoft Graph application permissions are not folded into that factor; they surface as their own first-class findings on the identity detail page, with their own evidence, and those findings feed back into the principal’s UPR. Keeping the unused-permission factor RBAC-scoped means every input to that factor stays defensible to a change board.

Catalog credit

The well-known Microsoft application catalog Permafrost uses to resolve first-party app GUIDs into human-readable names is derived from the public Microsoft Learn list of first-party applications, with the structure inspired by merill/microsoft-info (MIT license). Permafrost bundles a hand-curated subset covering the most common first-party apps an Azure CIEM reviewer encounters.