Repo sync for protected branch#410
Open
learn-build-service-prod[bot] wants to merge 92 commits into
Open
Conversation
Foundry Branding - Images
* Add sections for vector store integration * Fix links * Fix broken links * Fix titles * Apply suggestion from @SergeyMenshykh Co-authored-by: SergeyMenshykh <68852919+SergeyMenshykh@users.noreply.github.com> --------- Co-authored-by: SergeyMenshykh <68852919+SergeyMenshykh@users.noreply.github.com>
* Update AG-UI code samples to current Python and .NET SDK APIs Source issue: microsoft/agent-framework#5178 * Address review feedback for #969: review comment fixes * Address review feedback for #969: review comment fixes --------- Co-authored-by: MAF Dashboard Bot <maf-dashboard-bot@users.noreply.github.com>
Merge main to live
* Add skeleton and llm fundamentals * Add from llm to agent * Add adding-tools * Add adding skills * Add adding middleware * Add context providers * Add agents as tools * Add A2A * Add workflows * Fixes * Fixes 2 * Move down * Minor fix * Comments 1 * Comments 2
… safety, and Python parity (#940) Source issue: microsoft/agent-framework#4894 Co-authored-by: MAF Dashboard Bot <maf-dashboard-bot@users.noreply.github.com>
Merge main to live
…-docs Python: Add Cosmos DB checkpoint docs
…stricted deserialization (#973) Source issue: microsoft/agent-framework#5200 Co-authored-by: MAF Dashboard Bot <maf-dashboard-bot@users.noreply.github.com>
Merge main to live
…tories/ResourceDirectories Sync documentation with agent-framework PR #5205 which standardizes file skills terminology from 'folder' to 'directory' for consistency with the agentskills.io specification and .NET conventions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sync sills documentation with latest changes
merge main to live
* Add evaluation documentation for Agent Framework Document the agent evaluation feature covering local evaluators, Azure AI Foundry evaluators, conversation split strategies, workflow evaluation, and mixed evaluator patterns for both C# and Python. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update agent-framework/agents/evaluation.md Co-authored-by: Roger Barreto <19890735+rogerbarreto@users.noreply.github.com> * Update agent-framework/agents/evaluation.md Co-authored-by: Roger Barreto <19890735+rogerbarreto@users.noreply.github.com> --------- Co-authored-by: alliscode <bentho@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Roger Barreto <19890735+rogerbarreto@users.noreply.github.com>
* Fix Python structured output docs: use options dict for response_format
The Python code samples incorrectly showed response_format as a direct
parameter to agent.run(). The correct API requires passing it via the
options dict: options={"response_format": ...}. Updated all affected
code samples and prose in the structured output guide.
Fixes microsoft/agent-framework#5332
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address review feedback for #980: review comment fixes
* Fix redirect_document_id conflict and update markwallace author references
- Set redirect_document_id to false for tutorials/agents/structured-output.md
to resolve redirection-url-conflict warning (only one redirect per URL can
have redirect_document_id: true)
- Update author to moonbox3 and ms.author to evmattso in running-agents.md,
hosted-mcp-tools.md, local-mcp-tools.md, and overview/index.md
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: MAF Dashboard Bot <maf-dashboard-bot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add evaluation documentation for Agent Framework (#978)
added hyperlight docs (#983)
Docs: Add Foundry Toolbox docs
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…rning Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add A2A agent provider and A2A hosting documentation
Document FIDES (Flow Integrity Deterministic Enforcement System), the information-flow control middleware in agent_framework.security, as a new page under agents/. - New agents/security.md with reference-style coverage of labels, per-item labeling, tool annotations (accepts_untrusted, max_allowed_confidentiality), the full SecureAgentConfig option set, policy enforcement modes (block / approval / dry run), variable indirection, the quarantined LLM, an end-to-end walkthrough of a GitHub issue triage attack, and current limitations. - Python zone pivot carries the content; C# zone pivot shows 'coming soon' since FIDES is currently Python-only. - Cross-link added to agents/safety.md (TIP at the top, security.md promoted as next step and first related-content item). - TOC entry placed immediately after Agent Safety. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Source issue: microsoft/agent-framework#5943 Co-authored-by: MAF Dashboard Bot <maf-dashboard-bot@users.noreply.github.com>
Source issue: microsoft/agent-framework#5547 Co-authored-by: MAF Dashboard Bot <maf-dashboard-bot@users.noreply.github.com>
Merge main -> live
Clarify in the Microsoft Foundry provider page what does and doesn't work when using FoundryAgent versus Agent(client=FoundryChatClient(...)): - Tools: only FunctionTool callables already declared on the Foundry agent are invoked (locally), and no new tools can be added at construction time. - Context providers: message/observability providers work; tool-adding providers like SkillsProvider do not unless the tools are part of the Foundry agent definition. - Run options: many options on default_options and agent.run are silently ignored. Documents which are stripped/overridden vs forwarded for Prompt Agents, and notes that Hosted Agent behavior depends on the agent. Based on the discussion in microsoft/agent-framework#5883. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ementation (#1032)
Merge main to live
docs: Update Magentic Orchestration Docs to include .NET
Source issue: microsoft/agent-framework#5700 Co-authored-by: MAF Dashboard Bot <maf-dashboard-bot@users.noreply.github.com>
…sponses primary for OpenAI/Azure OpenAI (#1029)
* Document tools per provider client and new FoundryChatClient tools
- Add a stable `## Tools` section to every provider page in
agents/providers/ so the Tools overview matrix and per-tool detail
pages have a consistent anchor to link to.
- Rebuild the Provider Support Matrix in agents/tools/index.md:
- Column headers link to each provider page's `#tools` anchor.
- Add rows for tool types only available on the Python clients
(image generation, hosted shell, Bing variants, Azure AI Search,
SharePoint, Microsoft Fabric, Memory Search, Computer Use,
Browser Automation, A2A).
- Split the OpenAI `get_shell_tool` row from the GitHub Copilot
CLI's built-in shell/file/URL runtime tools.
- Mark Copilot Studio cells as `server-side` (configured in the
portal) and A2A cells as `remote` (lives on the remote agent).
- Document the new FoundryChatClient (Python) hosted tool factories on
microsoft-foundry.md, including a per-factory table and a short
inline example for each: image generation, Bing grounding,
Bing custom search, Azure AI Search, SharePoint, Microsoft Fabric,
memory search, computer use, browser automation, and agent-to-agent.
Mark experimental and preview factories accordingly.
- Note that Foundry toolboxes are consumed from `FoundryChatClient`
over MCP via `MCPStreamableHTTPTool` (the existing toolbox section
in the Python zone has details), and attached server-side on
`FoundryAgent`.
Known limitation: pages that have a `## Tools` H2 in both the C# and
Python zones share the same anchor namespace under DocFX zone pivots,
so cross-page deep-links to `#tools` resolve to the first occurrence
(C# zone). This mirrors the existing behavior of the duplicate
`## Toolboxes` headings on microsoft-foundry.md and is left
unchanged in this PR.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix duplicate H2 warnings and broken tab group
- anthropic.md: restore the C#-to-Python zone transition that was
accidentally removed when inserting the new `## Tools` section. The
collapsed zones caused DocFX to treat the entire file as a single
zone, which produced `pivot-id-unused` and `duplicate-h2s`
warnings for the (correctly zone-pivoted) duplicate headings such
as `## Configuration`, `## Getting Started`, and `## Tools`.
- ollama.md: restore the `# [Native Ollama](#tab/ollama-native)` tab
header that was accidentally removed when inserting `## Tools`,
fixing the `invalid-tab-group` warning.
Rebased on main to pick up the FoundryAgent capabilities heading from
#1028 so the cross-page bookmark links to
`#what-works-and-what-doesnt-with-foundryagent` resolve.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update broken OpenAI Chat Completions API link
The Learn build validator flagged the link to the OpenAI Chat
Completions API reference as broken (it returns 403 from the
platform.openai.com docs). Update to the new developers.openai.com
URL that OpenAI now uses for the Chat Completions overview.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Make Responses primary on OpenAI/Azure OpenAI; drop Assistants docs
- openai.md and azure-openai.md: reorder so Responses is the
recommended primary client, with Chat Completion second. Intro
table, client sections, and the per-page Tools matrix all lead
with Responses.
- Replace the Assistants client section with a short deprecation
note pointing to the migration guides. The Agent Framework no
longer documents an Assistants client.
- agents/tools/index.md: remove the Assistants column from both the
C# and Python provider support matrices; reorder Responses
before Chat Completion.
- Update broken OpenAI Responses API reference link
(platform.openai.com is 403'd by the Learn validator):
- openai.md and integrations/openai-endpoints.md now point at
developers.openai.com/api/reference/responses/overview.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Don't point C# Assistants notes to the Python migration guide
The Python significant changes guide is Python-specific. Remove it
from the C# Assistants Client deprecation notes in openai.md and
azure-openai.md, and reframe the top-of-page intro notes so the
Python guide is presented as a Python-only follow-up rather than
an alternative for everyone.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Move Assistants deprecation notes inside zone pivots
The intro NOTE about the Assistants API deprecation was rendered
above the zone pivot, so it had to say something true for both C#
and Python (and ended up mentioning a Python-only migration guide
to C# readers). Move the note inside each pivot so it can be
tailored:
- openai.md C# zone: short note pointing only at the Semantic
Kernel migration guide.
- openai.md Python zone: dedicated note noting that Python no
longer ships an Assistants compatibility surface, pointing at
the Python significant changes guide and the SK migration guide.
- azure-openai.md C# zone: short note pointing only at the SK
migration guide.
- azure-openai.md Python zone: existing IMPORTANT note already
covers the removed compatibility classes and links to the Python
significant changes guide.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update remaining OpenAI Chat Completions link on openai-endpoints
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use 'remote' consistently and mark Tool Approval framework-side
Address review feedback on #1029:
- Replace 'server-side' with 'remote' in the tools/index.md matrices
and in the Copilot Studio prose. 'remote' covers both A2A and
Copilot Studio — agent runs on a remote service, capabilities are
configured on that remote agent rather than through the framework
client.
- Mark Tool Approval as supported (✅) for every provider whose client
invokes function tools locally. Tool approval is handled by the
framework's function-invoking chat client (.NET and Python), not by
the underlying service, so it works wherever local function tools
work. Updated rows on the cross-page matrix and on the Anthropic,
Ollama, GitHub Copilot, Foundry Local, OpenAI, Azure OpenAI, and
Microsoft Foundry provider pages, with a short clarifying note on
each table.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Drop Copilot Studio and A2A columns from the tools matrix
Copilot Studio and A2A agents run on a remote service so every cell
in their columns was just "remote" — no information density. Drop
the columns and call them out in an intro sentence with links to
their provider pages instead. The standalone \`## Tools\` section on
each of those provider pages still explains the situation in prose.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Pivot Tool Types; drop Tool Approval from matrices; add Tool Approval section
- Move the Tool Types list inside zone pivots so each language only
sees the tools it actually has. Drop the redundant '(Python)'
suffix that the previous global table needed.
- Drop the Tool Approval row from both Provider Support Matrix
tables. Tool Approval is framework-side, not per-provider, so a
matrix row that is always ✅ adds no information.
- Add a new \`## Tool Approval\` section between Tool Types and
Provider Support Matrix, with a short blurb pointing at the
tool-approval detail page and noting that it works wherever local
function tools work.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
ms.topic= conceptual Replace with ms.topic = article Co-authored-by: Docs Allowlist Management <docs-allowlist-mgmt@microsoft.com>
Main to Live sync
Contributor
Author
|
Learn Build status updates of commit b1ae522: ✅ Validation status: passedFor more details, please refer to the build report. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Learn Build Service tried pushing to main, but failed due to branch protection rule in this branch. We create this pull request for manual merge. Please merge this pull request to complete this sync.
If you want to make push successfully without creating such pull requests in future, please follow working with branch protection rule to update your branch protection rule.