3.1.4. Reusable Components and Audience Design
💡 First Principle: The unit of agent development is not the agent — it's the component. Topics, agent flows, custom prompts, connectors, and child agents are all assets that can be designed once and reused across agents; planning for reuse turns your second agent into an assembly job instead of a second build.
Reuse has concrete platform mechanics: components live in solutions (Phase 4's packaging unit), where a topic authored for the HR agent, a flow that files tickets, or a prompt that summarizes complaints can ship to other environments and other agents. Component collections and template-based starts institutionalize the pattern — an organization's "customer service agent" template carrying pre-built topics, tone instructions, and escalation flows that each department then specializes. Connected agents (2.3) are reuse at the largest grain: the whole specialist, shared.
Audience design is the paired planning duty: internal and external audiences differ systematically — auth (Entra ID vs. OAuth/none), channels (Teams vs. web/messaging), knowledge exposure (permission-trimmed internal content vs. curated public content), tone and liability (helpful colleague vs. brand voice with legal review), and billing envelope (per-user licensing vs. consumption-metered Copilot Credits at public scale — a real cost-planning input when the audience is "everyone who visits the website"). Designing one agent for both audiences means satisfying both columns simultaneously; when the columns conflict, that conflict is the argument for two agents sharing components.
⚠️ Exam Trap: When a scenario mentions "multiple departments will need similar agents," the tested instinct is solution-packaged reusable components (or a shared connected specialist) — not copy-paste duplication, and not one mega-agent serving every department's divergent needs.
Reflection Question: Marketing wants the support agent "but for their audience" in six weeks. Name three components you'd reuse as-is, one you'd rebuild per-audience, and the planning artifact that makes the handoff possible.
