Skip to content

Update limitations and usage notes for Deep Research tool #587

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update limitations and usage notes for Deep Research tool #587

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion articles/ai-foundry/agents/how-to/tools/deep-research-samples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -574,7 +574,8 @@ with project_client:
:::zone-end

> [!NOTE]
> Limitation: The Deep Research tool is currently recommended only in nonstreaming scenarios. Using it with streaming can work, but it might occasionally time out and is therefore not recommended.
> * Limitation: The Deep Research tool is currently recommended only in nonstreaming scenarios. Using it with streaming can work, but it might occasionally time out and is therefore not recommended.
> * Currently, Azure AI Foundry Agent Playground UI only supports starting runs in streaming mode, and as a result, users might expect connection drops and timeouts. Use the supported methods above through code which uses runs in non-streaming mode.
Copy link

Copilot AI Nov 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammatical issue: 'users might expect' should be 'users might experience' - users don't expect problems, they experience them.

Suggested change
> * Currently, Azure AI Foundry Agent Playground UI only supports starting runs in streaming mode, and as a result, users might expect connection drops and timeouts. Use the supported methods above through code which uses runs in non-streaming mode.
> * Currently, Azure AI Foundry Agent Playground UI only supports starting runs in streaming mode, and as a result, users might experience connection drops and timeouts. Use the supported methods above through code which uses runs in non-streaming mode.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Nov 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The phrase 'through code which uses runs' is awkward. Consider rephrasing to 'Use the code-based methods shown above, which use runs in non-streaming mode.' for better clarity.

Suggested change
> * Currently, Azure AI Foundry Agent Playground UI only supports starting runs in streaming mode, and as a result, users might expect connection drops and timeouts. Use the supported methods above through code which uses runs in non-streaming mode.
> * Currently, Azure AI Foundry Agent Playground UI only supports starting runs in streaming mode, and as a result, users might expect connection drops and timeouts. Use the code-based methods shown above, which use runs in non-streaming mode.

Copilot uses AI. Check for mistakes.

## Next steps

Expand Down