Agent identities and blueprint principals have assigned technical owners and no disabled agents remain in the directory

Overview

Microsoft Entra Agent ID introduced two identity types: agent identities and agent identity blueprint principals. These identity objects derive from service principals, and so carry the same requirements and best practices for ownership, lifecycle management, and cleanup as any service principal. Blueprint principals are the provisioning surface from which agent identities are created and can hold grants that propagate to child agents. Having a designated owner for these objects helps in two important areas of agent identity management:

• Risks are contained and investigated by a responsible party
• Disabled objects don’t introduce dormant privileges

The owners relationship on each agent identity object designates the human users responsible for technical operations and incident response, distinct from the sponsors relationship that carries business accountability for lifecycle and access decisions. So when ID Protection flags an agent identity as risk or anomalous resource access patterns emerge, the security operations team can route to a responsible party for containment and investigation. If there’s no owner designated, a threat actor who compromises an ownerless agent or blueprint principal (through credential theft, blueprint exploitation, or malicious delegated consent) operates against a principal with no designated human for immediate containment. This issue can extend dwell time from minutes to the next manual directory audit cycle.

When an agent identity or agent identity blueprint is disabled, it can’t acquire new tokens so it can’t access resources. The object still exists in the directory, so its app role assignments, group memberships, and OAuth2 permission grants persist. If an administrative error or a threat actor with directory write access re-enables the object, every permission snaps back without reapproval. If a disabled blueprint principal is re-enabled, it also restores the provisioning surface for all child agent identities. The combination of ownerless objects and stale disabled objects creates a standing-privilege accumulation pattern that proper ownership and cleanup are designed to prevent.

Remediation

• Administrative relationships in Microsoft Entra Agent ID
• Manage agent identities in your organization
• Governing agent identities
• Manage agents in end-user experience

Run it

The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:

Install-Module ZeroTrustAssessment -Scope CurrentUser
Connect-Maester
Invoke-Maester -Pack ZTA -SkipBuiltIn

Leave out -SkipBuiltIn to run Maester’s own checks in the same run.

About this check

Severity	High
Effort to fix	Medium
Impact on users	Medium
Pillar	AI
Category	Agent Lifecycle
Product	Entra ID
Feature	Agent identities
Area	AI and agents
Licence	AAD_PREMIUM
Tenant	Workforce

Product, feature, area and ATT&CK are Maester’s: the assessment does not record them, so Maester keeps them in the pack’s taxonomy.json.

A Microsoft check, part of the Zero Trust Assessment pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, MIT licence.