Remove deprecated multi-agent workflow samples and update evaluation …

[Howie Leung (howieleung)]

…scripts with new role assignment parameters. Update YAML configuration for additional directories and commit reference.

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Ryan Hurey (rhurey)]

class RealtimeConversationItem(_Model): # pylint: disable=docstring-keyword-should-match-keyword-only

The Realtime classes can come from the OpenAI SDK, right?

---

Refers to: sdk/ai/azure-ai-projects/azure/ai/projects/models/_models.py:14274 in ab6b8d0. [](commit_id = ab6b8d0, deletion_comment = False)

[Howie Leung (howieleung)]

RealtimeConversationItem

Yes
From
node_modules@azure-tools\openai-typespec\src\realtime\models.tsp

[github-actions]

[Pilot] PR Pipeline Failure Analysis

What failed

Build: 6769789 (public) — failed

Tests failing on all platforms (macOS 3.11, Ubuntu 24.04 3.10/3.10-coverage/3.13/3.14, Windows 2022 3.12 — both whl and sdist artifacts):

• sdk.ai.azure-ai-projects.tests.foundry_features_header.test_foundry_features_header_on_beta_operations
• sdk.ai.azure-ai-projects.tests.foundry_features_header.test_foundry_features_header_on_beta_operations_async

Relevant pipeline output

tests/foundry_features_header/test_foundry_features_header_on_beta_operations.py:104: in _discover_test_cases
    assert sc_name in EXPECTED_FOUNDRY_FEATURES, (
AssertionError: New .beta sub-client 'agent_endpoint_conversations' discovered but not found in
EXPECTED_FOUNDRY_FEATURES. Please add an entry for '.beta.agent_endpoint_conversations' to the
EXPECTED_FOUNDRY_FEATURES mapping in base_test.py.
assert 'agent_endpoint_conversations' in {'agents': 'WorkflowAgents=V1Preview,...', ...}

Root cause

This PR introduced a new .beta sub-client agent_endpoint_conversations on the AIProjectsClient, but the guard assertion in tests/foundry_features_header/base_test.py (EXPECTED_FOUNDRY_FEATURES) was not updated. The test module fails at collection time (before any test runs) on every platform and install type.

Recommended next steps

• In sdk/ai/azure-ai-projects/tests/foundry_features_header/base_test.py, add an entry to the EXPECTED_FOUNDRY_FEATURES dict for key 'agent_endpoint_conversations' with the appropriate Foundry feature string value (e.g., 'AgentEndpointConversations=V1Preview' or whatever header value the new sub-client should send — check the sub-client implementation for the expected value).
• Re-run the pipeline after the fix.
• See https://aka.ms/ci-fix

Automated fix: Fix found, view and apply fix

Generated by Pipeline Analysis Next Steps · 42 AIC · ⌖ 6.37 AIC · ⊞ 6K · ◷