Entra ID: Non-Human Identity Risks
Microsoft Entra
8. Sept 2025 12:44

Entra ID: Non-Human Identity Risks

von HubSite 365 über Merill Fernando

Product Manager @ Microsoft 👉 Sign up to Entra.News my weekly newsletter on all things Microsoft Entra | Creator of cmd.ms & idPowerToys.com

Microsoft Entra ID app governance warns of nonhuman IDs and principals, secure apps with Entra and Azure

Key insights

  • Non-human identities (NHIs): NHIs include service principals, managed identities, API keys, and AI agents used for automation and workloads.
    They often outnumber human accounts and frequently hold high privileges, making them prime targets for attackers who can bypass user-based defenses.
  • Microsoft Entra Agent ID: A 2025 capability that gives each AI agent a unique, verifiable identity.
    This lets organizations authenticate, authorize, and audit AI agents like human users, improving control and traceability across AI-driven workflows.
  • Least privilege: Apply least-privilege access and strict lifecycle rules to NHIs to limit damage from credential compromise.
    Regularly rotate or remove unused identities and prefer managed identities to avoid manual secret handling.
  • Conditional Access: Extend Conditional Access policies to non-human accounts using real-time risk signals.
    This reduces unauthorized access by enforcing multifactor checks, device constraints, or session controls for suspicious NHI activity.
  • Entra ID Protection: Uses large-scale signals to detect sign-in anomalies and compromised credentials for both humans and NHIs.
    Integrate these alerts with automations and tools like security copilots to speed remediation and enforce safer policies.
  • App governance: Strong app governance prevents incidents like real-world breaches discussed in the episode and avoids risky cleanup mistakes (the “giraffe” story).
    Key actions: inventory NHIs, automate onboarding/offboarding, educate developers and ops, and adopt App Governance practices to reduce your attack surface.

Non-human identities in enterprise tenants

In a recent YouTube episode hosted by Merill Fernando, experts Jay Gundotra and Sander Berkouwer discuss the rising security challenge posed by non-human accounts in enterprise tenants. The episode explores real-world incidents, practical solutions, and the governance needed to manage machine identities across cloud environments. Importantly, the discussion frames these accounts as both enablers of automation and as potential attack vectors when unmanaged. Consequently, the video calls for new controls and clear operational practices to reduce risk.

What the video covers

The episode opens by defining the scope of the problem and then moves into concrete examples that highlight the stakes. The guests recount dramatic breaches such as the so-called Midnight Blizzard and lighter anecdotes like the theme-park cleanup that went wrong to show how small oversights lead to big consequences. After that, the conversation turns technical, explaining how service principals, managed identities, API keys, and AI agents operate inside a tenant and why they often escape traditional identity controls. Overall, the video balances storytelling with practical guidance to keep viewers engaged while educating them on core concepts.

Why non-human identities matter now

As organizations increase automation and adopt AI, machine accounts proliferate and can outnumber human users by large margins, which expands the attack surface. Consequently, attackers who compromise these accounts can access sensitive resources without needing to escalate privileges, which makes detection difficult. The speakers emphasize that lack of visibility, credential sprawl, and overly broad permissions combine to create systemic risk, especially when developers or DevOps teams create accounts without security oversight. Therefore, recognizing these identities as first-class security objects is a critical shift in thinking for defenders.

New tools and the evolving Microsoft approach

The guests highlight recent platform changes that aim to make governance more practical, including the introduction of the Microsoft Entra Agent ID which gives AI agents distinct, verifiable identities. In addition, enhancements in Microsoft Entra ID and identity protection tools now allow conditional access, lifecycle controls, and risk detection to apply to non-human accounts much like they do for people. These measures increase auditability and enable enforcement of least-privilege principles at scale, but they also introduce new management tasks and integration work. Thus, organizations must weigh the benefits of tighter control against the effort required to adopt and operate these capabilities.

Tradeoffs and operational challenges

While tighter governance reduces risk, it also raises practical challenges around discovery, change control, and business continuity, so teams face tradeoffs between security and agility. For example, locking down permissions can break automated workflows if teams do not coordinate changes or if lifecycle automation is incomplete, a point underscored by the “giraffe” cleanup story in the episode where remediation caused unintended outages. Furthermore, organizations must invest in inventorying all machine identities and in automating policy enforcement to avoid manual bottlenecks and errors. In short, the path to safer non-human identity management requires investment in tooling, clear processes, and ongoing education to prevent disruption while improving security.

Practical steps for IT leaders

The conversation closes with a set of practical recommendations that leaders can act on immediately, such as conducting an inventory of non-human accounts, applying least-privilege principles, and automating lifecycle actions for onboarding and offboarding. Moreover, the speakers recommend building cross-team governance processes so developers, security, and operations coordinate changes and own risks together, which reduces the likelihood of surprise failures. Ultimately, the episode argues that combining people, process, and platform—while taking advantage of agent identities and conditional access—creates a durable defense. Therefore, leaders should prioritize visibility and automation as the foundation for long-term improvement.

Microsoft Entra - Entra ID: Non-Human Identity Risks

Keywords

Entra ID non-human identities, service principal security, managed identity risks, app registration vulnerabilities, tenant identity governance, shadow identities detection, least privilege Entra ID, Azure AD automation security