azureblog.co.uk
← AB-650 study plan
AB-650 · Manage and secure AI services in Microsoft 365

Implement and manage agents in Microsoft 365 and Agent 365

Agent identity lifecycle with Entra Agent ID, securing agent access, agent owners, agent settings, the agent registry, publishing and blocking agents, and tools in Agent 365.

  • 22 min
  • 8 concepts
  • Try it yourself
  • 4-question check

Learn

Agents are AI assistants that act for users or on their own. Microsoft Agent 365 is the control plane for them: one registry of every agent (Microsoft, partner and custom), with access control, security signals and usage. Microsoft Entra Agent ID gives each agent an identity you can govern.

  1. 1

    Manage the lifecycle workflows for agent identities by using Microsoft Entra Agent ID

    Agent identities are created from agent identity blueprints; some agents also get an agent user account. Govern their lifecycle like employees: assign sponsors accountable for each agent, review and expire access, disable or delete agents that are no longer needed, and handle orphaned agents when owners leave.

    Remember: Every agent needs a sponsor and an end date.

  2. 2

    Secure agent access, including access packages and conditional access

    Give agents access through access packages (entitlement management) with approval and expiry rather than direct grants. Apply Conditional Access for agents: target agent identities or blueprints for app-only access and agent users for their own accounts; block high-risk agents. Policies don't carry across access patterns.

    Remember: Access packages for agents, with expiry.

  3. 3

    Manage agent owners

    Each agent has owners who maintain it. In the agent registry, view ownership, reassign ownership of orphaned agents (for example when a maker leaves), and require owners for published agents. Owners are notified about requests and issues.

    Remember: Reassign orphaned agents from the registry.

  4. 4

    Configure agent settings, including allowed agent types, sharing, templates, and user access

    In Agents > Settings in the Microsoft 365 admin center, control which agent types users can use or create (Microsoft, partner, custom), whether users can share agents they build and with whom, which templates are available, and which users or groups can access agents. Apply standard policy templates to new agents.

    Remember: Control who can build and share agents.

  5. 5

    Discover and manage Microsoft and third-party agents in the agent registry

    The agent registry lists all agents in the organisation with owner, publisher, usage and risk signals from Defender, Entra and Purview. Agent Map visualises agents by platform, and connected platforms bring in agents built on other platforms. Filter to find unused, risky or ownerless agents.

    Remember: One inventory of every agent.

  6. 6

    Review requests and publish or reject agents in the agent registry

    When users submit agents for organisation-wide use, admins review requests: check the agent's purpose, data sources, actions, permissions and publisher, then publish (optionally to specific users or groups) or reject with a reason.

    Remember: Review data sources and actions before publishing.

  7. 7

    Install, block, or control access to agents in the agent registry, including uploading custom agents

    Admins can deploy agents to users or groups, block an agent immediately (for example a risky third-party agent), control availability per user or group, and upload custom agents (app packages) built by internal teams. Partner agents can be deployed from the admin center.

    Remember: Risky agent? Block it at once from the registry.

  8. 8

    Manage tools in Agent 365

    Agents use tools (actions and connectors, including MCP servers) to read data or make changes. In Agent 365, admins control which tools agents can connect to, approve or block tools, and see which agents use each tool, limiting what an agent can do even if it's compromised.

    Remember: Limit tools to limit what an agent can do.

Agent lifecycle

  1. Build or acquireMicrosoft, partner or custom agent.
  2. RequestSubmitted to the registry.
  3. Review and publishAdmin approves to users or groups.
  4. GovernIdentity, access packages, Conditional Access, tools.
  5. MonitorUsage, risk, cost.
  6. RetireBlock or delete; reassign or remove owners.

Try it

A user submits an agent for the whole company. Decide what to do.

This interactive part needs JavaScript.

In the portal

  • Agent registryMicrosoft 365 admin center: Agents > All agents
  • Agent requestsMicrosoft 365 admin center: Agents > Requests
  • Agent settingsMicrosoft 365 admin center: Agents > Settings
  • Agent identitiesEntra admin center: Entra ID > Agent ID > All agent identities

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your AB-650 study plan.

  1. Where are agents published, blocked and reassigned?

  2. How should agents get access to resources?

  3. What should happen to an agent whose maker has left?

  4. What limits what a compromised agent can do?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.