Skip to content

Update Python BYO samples to AgentServer 2.1 GA - #941

Draft
Shiva S (Shivakishore14) wants to merge 1 commit into
microsoft-foundry:mainfrom
Shivakishore14:update/agentserver-2.1-ga
Draft

Shiva S (Shivakishore14) wants to merge 1 commit into
microsoft-foundry:mainfrom
Shivakishore14:update/agentserver-2.1-ga

Conversation

@Shivakishore14

@Shivakishore14 Shiva S (Shivakishore14) commented Aug 26, 2026

Copy link
Copy Markdown
Member

Summary

  • pin azure-ai-agentserver-core and azure-ai-agentserver-responses to 2.1.0
  • pin azure-ai-agentserver-invocations to 1.1.0
  • regenerate the existing portable dependency locks required by the Hosted Agent dependency policy
  • apply only the compatibility migrations required by the GA SDKs: explicit resilient-task opt-in, application-owned state replacing removed task/conversation metadata, and the GA get_input_expanded import path

No unrelated direct dependency upgrades or sample behavior changes are included.

Validation

  • Hosted Agent dependency-policy check with full transitive resolution
  • Python compilation and Ruff undefined-name checks for the required compatibility migrations
  • uv lock and portable export synchronization
  • exact file parity with the validated GA update from microsoft-foundry/foundry-samples-pr#906
  • public build-readiness validation passed

CI status

The repository trusted job intentionally rejects fork PRs before Azure login and live-service testing. A maintainer must promote commit 2315d00b to a same-repository branch to run the trusted live-service gate.

Pin Core and Responses to 2.1.0 and Invocations to 1.1.0, including the required resilient-state API migrations.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Luffy Chen (XOEEst) pushed a commit to XOEEst/foundry-samples that referenced this pull request Aug 29, 2026
…icrosoft-foundry#941)

The AI Services account in the managed virtual network template sets
networkInjections[0].subnetArmId to an empty string together with
useMicrosoftManagedNetwork: true. subnetArmId is an ARM resource identifier,
so an empty string fails ARM validation with LinkedInvalidPropertyId
("Expect fully qualified resource Id that start with '/subscriptions/...'"),
which blocks account creation.

For the managed virtual network scenario the subnet is provisioned by the
platform, so subnetArmId should be omitted. Removing the empty value lets the
account create succeed while useMicrosoftManagedNetwork: true drives
managed-network provisioning.

Updates the bicep module, the compiled azuredeploy.json, and the azure-cli example.

Co-authored-by: vtrika <vtrika@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant