Perform basic administrative tasks for Copilot and agents
Agent Creation, Approval, Access, and Lifecycle
Create bounded agents, govern publication and audience, and use the right inventory for tenant-wide versus Power Platform-built resources.
What you need to know
- An agent combines instructions with selected knowledge and, when needed, tools or actions.
- Organization-wide publication requires administrative review of ownership, data, capabilities, tools, permissions, and audience.
- Microsoft 365 admin center shows published/shared agents available in the tenant; Power Platform inventory includes Power Platform-built agents and drafts.
- Lifecycle actions include publish, deploy/assign, update approval, block, remove, transfer ownership, and retire.
Objects and administrative surfaces
- Agent creation — Agent Builder for straightforward declarative scenarios or Copilot Studio for richer low-code scenarios.
- Requests, Agent Registry, access, publishing, blocking, and usage — Microsoft 365 admin center.
- Environments, drafts, connectors, ownership, and Power Platform-built inventory — Power Platform admin center.
How it works
- A maker can share within allowed controls or submit an agent for organizational publication; an administrator reviews before broad availability.
- An approved update is a separate lifecycle decision; the prior version can remain available until approval.
When to use it
- Use Microsoft 365 admin center for the available tenant catalog and requests; use Power Platform inventory for environment-aware maker resources and drafts.
- Block or retire an unsafe, unowned, obsolete, or noncompliant agent.
Security and governance implications
- Use a limited audience first, least-privileged connectors/actions, named owners, review dates, and monitoring.
- Approval validates the agent package and scope; it does not certify every future response.
Troubleshooting signals
- Check publication status, audience assignment, agent settings, licensing/metering, owner, environment, and connector permissions.
- Clarify which inventory count is requested because the two admin centers have different scopes.
Exam traps
- Creating or sharing an agent is not the same as publishing it tenant-wide.
- Power Platform inventory and Microsoft 365 Agent Registry can legitimately show different counts.
Key takeaways
- Create → review → publish to a scoped audience → monitor → update or retire.
- Choose the inventory surface that matches the question.
Related objectives
- D3.3.a
- D3.3.b
- D3.3.c
- D3.3.d