Skip to content

Remove deprecated multi-agent workflow samples and update evaluation … - #48795

Open
Howie Leung (howieleung) wants to merge 3 commits into
feature/azure-ai-projects/vnextfrom
howie/reemit
Open

Remove deprecated multi-agent workflow samples and update evaluation …#48795
Howie Leung (howieleung) wants to merge 3 commits into
feature/azure-ai-projects/vnextfrom
howie/reemit

Conversation

@howieleung

Copy link
Copy Markdown
Member

…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

Copy link
Copy Markdown
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.

@github-actions

This comment has been minimized.

@rhurey

Copy link
Copy Markdown
Member

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)

…lti-agent workflow samples

- Introduced a new sample script `sample_agent_publish_to_microsoft365.py` demonstrating how to create and publish a Prompt Agent to Microsoft 365 using the AIProjectClient.
- Removed outdated multi-agent workflow samples: `sample_workflow_multi_agent.py`, `sample_workflow_multi_agent_async.py`, and `sample_workflow_multi_agent_with_mcp_approval.py`.
- Updated evaluation samples to use new models and structures, including changes in role assignment parameters.
- Updated `tsp-location.yaml` to reflect new commit and additional directories for agent insights and Microsoft 365 agents.
@howieleung

Copy link
Copy Markdown
Member Author

RealtimeConversationItem

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

- Updated api.metadata.yml with new hash and parser version.
- Enhanced _patch.py to include new operations for Agent Endpoint Conversations and Agent Insight Monitors.
- Introduced Agent Insight run polling classes for both synchronous and asynchronous operations.
- Created new async and sync patch files for Agent Insight Monitors operations.
- Updated operation classes to support new features and ensure proper integration with existing models.
@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor
[Pilot] PR Pipeline Failure Analysis

What failed

Build: azure-sdk/public #6768621failed

Two distinct failure categories were found:

1. Test collection failures (all platforms)

Tests test_foundry_features_header_on_beta_operations and test_foundry_features_header_on_beta_operations_async failed on all 6 platforms (macos311, ubuntu2404_310, ubuntu2404_310_coverage, Ubuntu2404_313, Ubuntu2404_314, windows2022_312) for both whl and sdist artifacts.

Root cause: A new .beta sub-client agent_endpoint_conversations was introduced by this PR, but the EXPECTED_FOUNDRY_FEATURES mapping in tests/foundry_features_header/base_test.py was not updated to include an entry for it.

Relevant pipeline output
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,...', ...}

File: tests/foundry_features_header/test_foundry_features_header_on_beta_operations.py:104
File: tests/foundry_features_header/test_foundry_features_header_on_beta_operations_async.py:109

Fix: In sdk/ai/azure-ai-projects/tests/foundry_features_header/base_test.py, add an entry for 'agent_endpoint_conversations' to EXPECTED_FOUNDRY_FEATURES with the appropriate Foundry feature flag value.


2. CSpell spelling check failure

The CSpell check flagged 85 issues across 6 files. The unknown words are technical acronyms and terms introduced by the new API surface in this PR.

Relevant pipeline output
##[error]sdk/ai/azure-ai-projects/api.md - Unknown word (Pcma), (pcma), (PCMA), (Pcmu), (pcmu), (PCMU)
##[error]sdk/ai/azure-ai-projects/api.md - Unknown word (MCPHTTP)
##[error]sdk/ai/azure-ai-projects/api.md - Unknown word (DTMF), (dtmf)
##[error]sdk/ai/azure-ai-projects/azure/ai/projects/aio/operations/_operations.py - Unknown word (BYOS), (retriable)
##[error]sdk/ai/azure-ai-projects/azure/ai/projects/models/_enums.py - Unknown word (PCMU), (PCMA), (DTMF)
##[error]sdk/ai/azure-ai-projects/azure/ai/projects/models/_models.py - Unknown word (Pcma), (Pcmu), (MCPHTTP), (BYOS)
##[error]sdk/ai/azure-ai-projects/azure/ai/projects/operations/_operations.py - Unknown word (BYOS), (retriable)
##[error]Spelling errors detected. See: https://aka.ms/azsdk/engsys/spellcheck

Fix: Add the unknown words (BYOS, DTMF, MCPHTTP, PCMA, PCMU, Pcma, Pcmu, dtmf, pcma, pcmu, retriable) to the CSpell allowlist. See https://aka.ms/azsdk/engsys/spellcheck for guidance.

Recommended next steps

  • In sdk/ai/azure-ai-projects/tests/foundry_features_header/base_test.py, add 'agent_endpoint_conversations': '<feature_flag_value>' to EXPECTED_FOUNDRY_FEATURES (use the appropriate feature flag matching the new sub-client).
  • Add the flagged words to the CSpell allowlist per https://aka.ms/azsdk/engsys/spellcheck.
  • See https://aka.ms/ci-fix

Automated fix: Fix found, view and apply fix

Generated by Pipeline Analysis Next Steps · 50.3 AIC · ⌖ 9.45 AIC · ⊞ 6K ·

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants