Your team has built a specialized 'IT Helpdesk' Copilot Studio agent in a development environment. You want to reference this agent as a child agent from a new 'Company Portal' agent in the same production environment. What is the prerequisite for the Company Portal agent to invoke the IT Helpdesk agent?

Copilot Studio supports multi-agent architectures where a parent (orchestrator) agent can route conversations to specialized child agents. To invoke a child agent, the child must be: 1) Published (not in draft state), 2) Present in the same Power Platform environment as the parent agent, and 3) Added to the parent agent's configuration as a child agent reference.

The parent agent, when using generative orchestration, can automatically detect when a user's request matches the child agent's purpose and route the conversation there. Alternatively, explicit topic actions can invoke child agents.

Option A (same topic template) has no bearing on agent communication — templates are starting points for authoring, not runtime communication prerequisites.

Option C (ZIP file import as embedded component) is not how child agent references work. Child agents remain separate, independently deployed agents — they are referenced by connection, not embedded.

Option D (same Teams channel) — child agent invocation is an internal agent-to-agent capability; it doesn't depend on channel configuration. The parent agent's channel handles the user-facing communication.

Key exam steps: publish the child agent → in parent agent configuration, add child agent reference → generative orchestration routes to child when appropriate. Both agents must be in the same environment.