Preventing Child Agent from Reformatting User Queries in Orchestrated (Parent–Child) Scenarios

(3) Share

Report

Posted on by SR-24020711-0

Hi Community,

I am working with a parent–child agent setup in Microsoft Copilot Studio and facing an inconsistency in how user queries are handled.
When a user submits a question to the parent (orchestrator) agent, the query is passed to a child agent, but it gets reformatted or altered (as shown in the attached screenshot). However, when the same original question is asked directly to the child agent, the response differs.
This results in inconsistent outputs between:

Parent → Child agent flow
Direct interaction with the child agent

Issue:
The child agent appears to modify or reinterpret the incoming query when invoked via the parent agent, leading to different responses for the same user intent.
Ask:
How can I prevent the child agent from reformatting or altering the original user query when it is invoked by the parent (orchestrator) agent, so that the responses remain consistent across both interaction paths?

Issue-SS.png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Haque 3,382 on at

Like (0)

Report
Copy link

Link copied!

Hi @SR-24020711-0,

Can you please embed (copy from the screenshot and paste directly in the question body) the screenshot in the question body - updating again?

The attachement takes a lot of time becuse of scanning (It shows - Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.)

Was this reply helpful? Yes No
Suggested answer

SpongYe 5,903 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @SR-24020711-0 ,

Make use of variables.
In the parent agent, immediately store the original user message. Activity.Text is the current/latest user message and is commonly used as the input for generative answer or search nodes in Copilot Studio.

Then define an explicit input on the child agent/topic. Multi-agent guidance emphasizes that inputs/outputs define the data flow and partly define what the child agent is being asked to do.

After that Map the parent variable to the child input.

Last but not least, update the agents instructions. Add something like this to the child agent:

When invoked by a parent agent, use the input variable `variableName` as the user’s exact request. Do not rewrite, reformat, summarize, expand, or reinterpret `variableName`. Use it as the input for retrieval, search, knowledge grounding, and answer generation. If conversation history conflicts with `variableName`, prioritize `variableName`.

This will not necessarily stop the parent orchestrator from internally reasoning about the request, but it gives the child agent a deterministic, verbatim input to use. That is the practical way to make Parent → Child behavior match direct child-agent interaction as closely as possible.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,102 on at

Like (1)

Report
Copy link

Link copied!

Hi @SR-24020711-0,

SpongYe is correct. The parent orchestrator rewrites the query before passing it to the child that's by design in generative orchestration.

To keep it consistent:

1. In the parent, capture the original query: Set(varOriginalQuery, Activity.Text)
2. Pass varOriginalQuery as an explicit input parameter to the child agent
3. In the child agent's instructions add: "When called by a parent agent, use the input variable as the user's exact original request. Do not rewrite or reinterpret it."

This won't fully stop the orchestrator's internal reasoning but it gives the child a verbatim input to ground its response on, which closes the consistency gap significantly.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 2,661 on at

Like (0)

Report
Copy link

Link copied!

If your requirement is response consistency between direct child-agent interactions and parent-to-child interactions, the most reliable approach is to pass the

original user query as an explicit input parameter to the child agent and minimize any parent-agent summarization or prompt transformation. Then verify through

diagnostics that the child agent is receiving the same text in both scenarios.

If you're using the newer Copilot Studio Agent Orchestration (agent-to-agent handoff), some degree of prompt rewriting is currently part of the platform

behavior, and complete prevention may not be possible in all scenarios. In that case, reviewing the orchestration configuration and inspecting the child agent's

received prompt is the best next step.

Was this reply helpful? Yes No