… 3 unchanged lines …
  ## Key facts
  - Built with Agent Builder (no-code), Copilot Studio, or Teams Toolkit and the agent manifest.
  - Knowledge can point at SharePoint/OneDrive, Graph connectors, web content, and embedded files.
- - Actions come from API plugins (OpenAPI), connectors, or MCP servers.
+ - Actions come from API plugins (OpenAPI), connectors, or MCP servers. Microsoft now frames an agent as one component a plugin can include or reference, alongside skills, Copilot connectors and MCP-based tools.
+ - An agent is defined by identity and behaviour (name, purpose, instructions, conversation starters, constraints), knowledge, capabilities, and the host and distribution metadata that surfaces it.
  - Instruction text has a character ceiling (thousands of characters, not unlimited) — keep prompts tight.
  - Needs a Microsoft 365 Copilot licence to run; packaged and distributed as an M365 app.
  
    … 1 unchanged line …
  Use for the vast majority of "Copilot that knows about X and can do Y" asks. Skip only when you need a different model, custom orchestration, or a fully standalone chat surface outside Copilot.
  
  ## Configuration decisions
+ - Whether you need a new agent at all. Microsoft's guidance is to check for an existing approved agent you can reuse, copy, configure or extend first.
  - Which knowledge sources, and whether they're already indexed.
  - Instruction scope — how tightly you constrain behaviour.
  - Which actions to expose, and their auth.
    … 2 unchanged lines …
  - Grounding is only as good as the underlying index; unindexed SharePoint content simply won't surface.
  - Users still need access rights to the source content — the agent doesn't bypass permissions, and it shouldn't.
  - Instruction length limits bite once you try to encode complex logic.
+ - Reuse needs an owner. Before you copy someone else's agent, confirm they support your users, data, sharing scope and lifecycle, or you inherit an orphan.
+ - National cloud availability differs, so check the government cloud note before promising it to a public-sector client.
  
  ## Consultant notes
  
  - This is the default recommendation. Cheap to build, easy to govern, no model hosting.
  - Grounding cost sits with the connectors and Copilot licensing, not the agent itself — but connector item counts add up.
  - Approval to publish tenant-wide goes through the admin centre, so agree the sign-off route early.
+ - Write down the dependencies before building: target users, knowledge, required connectors or skills, permissions and consent, licensing, owner and success measures. It's dull, and it's what stops a pilot stalling at security review.
  
  ---
  
- *Review if the manifest schema or instruction limits change.*
+ *Review if the manifest schema, instruction limits or the plugin framing change.*