[JianW (v1212)]

Summary

• require voice_conversation_engine/1.0.0 for Hosted Voice conversation-engine targets
• preserve ordinary invocations_ws support as an independent protocol, including targets declaring both protocols
• report the dedicated CE WebSocket endpoint and AGENT_<KEY>_VOICE_CONVERSATION_ENGINE_ENDPOINT
• avoid unsupported Inspector/invoke guidance for CE-only local runs

Scope

This is an independent PR based on main. It does not depend on #10901 and does not change Voice preview flags or release metadata. Changes are confined to the azure.ai.agents extension: target validation, endpoint reporting, local guidance, focused tests, and necessary README updates. No schema, request mapping, init lifecycle, telemetry, or deployment-order changes.

Validation

• full extension tests on latest main: GOWORK=off go test -p 1 ./...
• full extension build
• go-fix and diff checks
• earlier Scenario 10 TTL 3-day cloud validation: target/wrapper deployment, readback, text/audio, repeat deployment, unsupported-version rejection, and verified Agent/resource-group cleanup

The cloud evidence was collected on the earlier PR build; local tests/build have been rerun on this independently rebased head.

[azure-pipelines]

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

[Copilot]

🟡 Changes recommended

Conversation-engine-only targets receive unsupported invoke guidance, while validation hints and documentation inaccurately describe the requirements for the supported voice paths.

3 open issues

• Avoid invoke guidance for conversation-engine-only targets · New
• Include legacy protocol and metadata in validation hints · New
• Document both Hosted Voice paths and update preview-flag descriptions · New

What changed in this PR

Adds dedicated Hosted Voice conversation-engine support to the azure.ai.agents extension while preserving legacy bridge compatibility.

Changes:

• Accepts voice_conversation_engine/1.0.0 without legacy bridge metadata.
• Applies the existing Voice preview gate to dedicated conversation engines.
• Adds protocol acceptance, version rejection, and preview classification tests.

Extension user-contract review: blocked (5 files inspected; 0 new contract comments; 0 existing threads matched; prior review history unavailable).

File	Description
cli/​azd/​extensions/​azure.ai.agents/​internal/​project/​service_target_agent.go	Accepts dedicated engines and updates incompatibility guidance.
cli/​azd/​extensions/​azure.ai.agents/​internal/​project/​preview_features.go	Applies the Voice preview gate to conversation engines.
cli/​azd/​extensions/​azure.ai.agents/​internal/​project/​preview_features_test.go	Tests conversation-engine preview classification.
cli/​azd/​extensions/​azure.ai.agents/​internal/​project/​hosted_voice_target_test.go	Tests dedicated-protocol acceptance and unsupported versions.
cli/​azd/​extensions/​azure.ai.agents/​internal/​pkg/​agents/​agent_api/​models.go	Defines the conversation-engine protocol constant.

_{Review effort: Max}

[Copilot]

🟡 Changes recommended

Conversation-engine-only local runs print “In another terminal, try:” without a command because the heading is emitted even when the suggestion list is empty.

1 open issue

• Avoid showing an empty command prompt when no suggestions exist · New

3 resolved since last review

• Include legacy protocol and metadata in validation hints
• Avoid invoke guidance for conversation-engine-only targets
• Document both Hosted Voice paths and update preview-flag descriptions

_{Review effort: Max}

[JianW (v1212)]

Scenario 10 cloud validation passed on the Foundry Dev Tools TTL 3-day subscription using the PR extension bundle (8419ba523): pinned public conversation-engine sample, provision/deploy, target readback with voice_conversation_engine/1.0.0, wrapper conversation_engine readback, Voice endpoint, text and audio smoke (input transcript, completed story, 561,600 output-audio bytes), repeat deploy/smoke, Vienna rejection of target protocol 2.0.0, and cleanup. Both Agents independently returned 404 and the dedicated resource group was deleted.

[Copilot]

🔵 Needs a closer look

Conversation-engine-only targets still auto-launch Agent Inspector or display its installation instructions, even though Inspector does not support that protocol.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Suppress Agent Inspector for conversation-engine-only targets

cli/​azd/​extensions/​azure.ai.agents/​internal/​cmd/​nextstep/​resolver.go:1002

For a conversation-engine-only target, runRun still auto-launches Agent Inspector (or prints its install instructions), even though Inspector only handles Responses/Invocations. Extend the run client profile to suppress that client for conversation-engine-only targets, while preserving it when an Inspector-supported protocol is co-declared.

1 resolved since last review

• Avoid showing an empty command prompt when no suggestions exist

_{Review effort: Max}

[Copilot]

🟡 Changes recommended

Conversation-engine-only targets trigger false missing-deployment errors and an incompatible Inspector client, while cancellation can still produce a misleading “Agent ready” message.

3 open issues

• Suppress Agent Inspector for conversation-engine-only targets · New
• Recheck cancellation before printing the agent-ready heading · New
• Avoid missing-deployment errors for targets without public URLs · New

_{Review effort: Max}

[Copilot]

🟡 Changes recommended

Private monitoring defaults can silently disrupt unrelated workloads’ telemetry on existing VNets, while incomplete DNS checks allow changes to shared zones without adequate safeguards.

2 open issues

• Preserve conversation-engine protocol through readiness routing · New
• Update Hosted Voice example to use the validated target · New

3 resolved since last review

• Avoid missing-deployment errors for targets without public URLs
• Recheck cancellation before printing the agent-ready heading
• Suppress Agent Inspector for conversation-engine-only targets

_{Review effort: Max}

[Copilot]

🟡 Changes recommended

Targets declaring both voice and A2A protocols incorrectly launch or recommend installing Agent Inspector, which supports neither protocol, instead of preserving client-free A2A invocation guidance.

1 open issue

• Treat voice-engine/A2A targets as client-free while preserving A2A · New

2 resolved since last review

• Preserve conversation-engine protocol through readiness routing
• Update Hosted Voice example to use the validated target

_{Review effort: Max}

[Copilot]

🔵 Needs a closer look

Human assessment is needed because the conversation-engine shortcut can bypass required setup for endpoint-only Activity profiles, potentially breaking local messaging.

No open issues 🎉

1 resolved since last review

• Treat voice-engine/A2A targets as client-free while preserving A2A

_{Review effort: Max}

[Copilot]

🟡 Changes recommended

Hosted endpoint show can fail without a default environment despite successful project resolution, and can expose stale conversation-engine URLs because saved metadata completeness and project identity are not validated.

2 open issues

• Treat missing default environment as absent optional metadata · New
• Validate saved project identity and snapshot completeness · New

_{Review effort: Max}

[Copilot]

🟡 Changes recommended

Comparing raw saved endpoints against normalized endpoints causes endpoint show to omit the conversation-engine URL for valid deployments with uppercase hostnames.

1 open issue

• Normalize saved endpoints before comparing them · New

2 resolved since last review

• Validate saved project identity and snapshot completeness
• Treat missing default environment as absent optional metadata

_{Review effort: Max}

[Copilot]

🔵 Needs a closer look

Human assessment is needed because snapshots can retain stale CE URLs across extension versions and deployment changes, causing endpoint reporting to present outdated endpoints as callable.

No open issues 🎉

1 resolved since last review

• Normalize saved endpoints before comparing them

_{Review effort: Max}

[azure-sdk-automation]

azure.ai.agents PR build

Note

This is an unsigned development build. Install it only if you trust this PR.

Install the extension:

azd ext install "https://azuresdkartifacts.z5.web.core.windows.net/azd/extensions/pr/10900/azure-ai-agents.zip"

• Version: 1.0.0-pr.10900.7064118
• Merge commit: a8c13f6