Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.2.2. Securing Agent Access and Managing Agent Owners

💡 First Principle: Agents should get access the way well-run organizations give people access: requested for a purpose, approved, time-limited and reviewed. Conditional Access then constrains when and how that access can be used — but only if each policy targets the right kind of agent principal.

Access packages (Entra admin center > ID Governance > Entitlement management > Access packages, as at least an Identity Governance Administrator) bundle the access an agent may receive — security group memberships, Microsoft Entra directory roles and OAuth API permissions (delegated and application). Application roles, SAP roles and SharePoint Online site roles aren't supported for agent identities. Adding API permissions or directory roles marks the catalog as privileged. In the package policy, "Who can get access" is set to users, service principals and agent identities in your directory > All agents. Approval can have one to three stages, and the lifecycle settings set expiry. Access can be requested three ways: by the agent identity itself through Microsoft Graph, by its sponsor in the My Access portal, or by an admin assigning it directly. As expiry approaches the sponsor is notified and can request an extension; if the sponsor does nothing, the assignment expires and access is removed.

Conditional Access for agents must target the principal that actually holds the token:

Access patternWhat to target
On behalf of a user (delegated)The users and groups — the signed-in user is the token subject
Autonomous (app-only)The agent identity, or the blueprint to cover every identity created from it, including future ones
As an agent userThe agent user account — under Assignments > Users, agents or workload identities > Agents

Three rules follow, and the exam tests all of them:

  • A policy scoped through the Users assignment (all users, groups, roles) doesn't apply to agent user accounts, and agent users can't be scoped by group membership.
  • A policy on an agent identity doesn't apply to its agent user, and vice versa.
  • A blueprint policy covers only the agent identities created from it, not their agent users.

Policies can block all agent identities or all agent users, use agent risk from ID Protection (high, medium, low), and run in report-only mode. Conditional Access doesn't apply when security defaults are on, or when an agent authenticates with something other than its Entra identity, such as an API key. Licensing: Conditional Access and access packages for agents need Microsoft 365 E7, or Agent 365 with at least Entra ID P1 or Microsoft 365 E3.

Agent owners in the Microsoft 365 admin center:
OwnerSponsor
Required?NoYes — at least one per agent identity and blueprint
PurposeTechnical setup, configuration, credentialsBusiness accountability for purpose and lifecycle
Can beUsers (including guests) or service principals — not groupsUsers or certain groups
Disable and soft-deleteYesYes
Re-enable, restore, hard-deleteYesNo
  • Assign new owner (Agents > All agents > select the agent) works for ownerless or active agents, but only shared Agent Builder and Copilot Studio agents — you can't reassign Microsoft's own agents. The new owner gets full edit and delete rights, and the previous owner loses all access, including read.
  • Add or remove owners applies to Agent Builder agents, which support multiple equal owners. Groups can't be owners, and you can't remove the last owner.
  • Shared agents become ownerless when the creator's account is deleted; the Agents without owners card finds them. Agent management rules can reassign ownerless Agent Builder agents to the creator's manager, or block ownerless agents without usage.

⚠️ Exam Trap: "Create a Conditional Access policy for All users to require compliant devices — this covers our agents too" is wrong. Agent users aren't covered by the Users assignment; you must add a policy that targets Agents.

Reflection Question: An autonomous agent built from a Foundry blueprint, and its paired agent user, both need to be blocked from signing in from outside your network. How many Conditional Access targets do you need, and why can't one policy on the blueprint cover both?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned