Automated sync from private repo (2026-07-30) - #863
Merged
foundry-samples-repo-sync[bot] merged 7 commits intoJul 30, 2026
Conversation
…es (#801) * Bump Microsoft.Agents.AI.Foundry.Hosting to latest preview * Bump Microsoft.Agents.AI to latest * bump Microsoft.Agents.AI packages to 1.15 * update method * correct version * update * upgrade version * Bump Azure.AI.Projects to latest --------- Co-authored-by: Yajun Lu (Centific Technologies Inc) <v-yajunlu@microsoft.com>
* feat(hosted-agents): add E2E assertion contracts * fix(hosted-agents): complete approval-based E2E turns * fix(hosted-agents): retain approval response history * feat(hosted-agents): scope MCP approvals per test turn * refactor(hosted-agents): extract Responses invocation helper * docs(hosted-agents): require owned E2E contracts * refactor(hosted-agents): use deterministic approval sequence * refactor(hosted-agents): clarify assertion evidence sources * docs(hosted-agents): explain assertion contract scope * fix(hosted-agents): fail closed on invalid E2E evidence --------- Co-authored-by: Wei Meng <20290571+m5i-work@users.noreply.github.com>
…t creation time (#826) Address the documentation gaps raised in foundry-samples#853: - Call out that Microsoft.App and Microsoft.ContainerService are mandatory for networkInjections.scenario='agent'. If either is NotRegistered the deployment fails AFTER the account resource is accepted (provisioningState: Failed) and must be cleaned up before retry. Point at the existing preflight check and cleanup guidance. - Document that capability-host creation on a network-injected account can take ~30-35 minutes so operators do not cancel a deployment assuming it hung. The provider prerequisite itself was already listed in Prerequisites and is enforced by deployment-tools/preflight/preflight-check.ps1; this change makes the consequences of skipping it explicit. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 39492a7b-bac9-4f93-932d-7490c1044726
…ME (#824) * Fix incorrect guardrail behavior claims in content-safety sample README Verified the sample end-to-end against a live Foundry project (canadacentral, azd 1.29.0 + azure.ai.agents 1.0.0-beta.7). The deploy/invoke/block flow works, but two documented behaviors do not match reality: - "include the policies block but omit raiPolicyName to use Microsoft.DefaultV2" is unreachable: azd rejects the shape at packaging with "policies[0] of type 'rai_policy' requires a policy name". - "Deploying with a placeholder or nonexistent policy ID fails" is wrong and unsafe: the literal placeholder deploys successfully, the agent reports active, and the guardrail then FAILS OPEN — a violating prompt that returns 400 content_filter with a real policy is not blocked at all. The agent behaves identically to one with no policies block. Replace both claims, add a warning about the fail-open placeholder, order the verification troubleshooting so policy existence is checked first, and note that the guardrail covers streaming requests as well. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24b00bc8-8c3e-416d-9229-22e7273824f9 * Address review: use explicit raiPolicies collection URL in troubleshooting Replace the <your-policy-arm-id-without-the-policy-name> placeholder with a full Microsoft.CognitiveServices/accounts/<account>/raiPolicies collection URL, matching the segment names used in azure.yaml. Verified against a live account. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24b00bc8-8c3e-416d-9229-22e7273824f9 * Scope fail-open warning to subscriptions without create-time RAI validation Create-time RAI policy validation exists in the service (AgentController .ValidateRaiConfigAsync -> AgentManager.UnpackRaiConfigAsync) but is gated behind the per-subscription ECS flag AgentsPlatform.AgentsManagement .RaiFeatureEnabled. Where the flag is off, a nonexistent policy deploys and fails open; where it is on, deployment is rejected. Reword so the guidance is correct either way. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24b00bc8-8c3e-416d-9229-22e7273824f9 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24b00bc8-8c3e-416d-9229-22e7273824f9
* Voice hotel booking agent sample client * Fix package-lock.json: use public npm registry for @azure/ai-voicelive * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Jian Miao <jianm@microsoft.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* docs: list all Agent Framework samples Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2888e84e-1355-4f1a-b894-89197f4093f9 * docs: clarify Agent Framework local setup Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2888e84e-1355-4f1a-b894-89197f4093f9 * Change 'Invoking the Responses Agent' to 'Invoking the Agent' Updated the section title for clarity. --------- Co-authored-by: herohua <2174068+herohua@users.noreply.github.com> Copilot-Session: 2888e84e-1355-4f1a-b894-89197f4093f9
Prevent local E2E configuration from being committed or included in azd deployment payloads. Model: GitHub Copilot Authored-by: Vipin Koottayi Co-authored-by: Vipin Koottayi <vkoottayi@microsoft.com>
foundry-samples-repo-sync
Bot
deleted the
sync/private-to-public-20260730-135310
branch
July 30, 2026 13:57
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
7 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.
Automated sync from private repo.
Synced commits: 7
Authors: Amit Bhave,Haflidi Fridthjofsson Helly Zhang,Jian Miao Wei Meng,Ying Hua vtrika
Validation gate: mode=
none; tracked=48; blocked=12.Rollback point:
f81db1d1dce55b271ec664e3c755c78a8fd8edcc— to revert, force-push this SHA tomainand clear the sync-marks cache.Triggered by:
workflow_dispatchRun: https://github.com/microsoft-foundry/foundry-samples-pr/actions/runs/30547314698