Clean up env vars automatically added to agent.yaml during init

[Copilot]

Microsoft samples are migrating to FOUNDRY_PROJECT_ENDPOINT (auto-injected by the hosted agent platform), so azd no longer needs to bake AZURE_AI_PROJECT_ENDPOINT / AZURE_OPENAI_ENDPOINT into agent.yaml during init.

Changes

• Remove old env vars from agent.yaml init (init_from_code.go): Stop adding AZURE_OPENAI_ENDPOINT and AZURE_AI_PROJECT_ENDPOINT to the environment_variables section. Model-specific vars like AZURE_AI_MODEL_DEPLOYMENT_NAME are still added when applicable.

• Add FOUNDRY_ env var translation for azd ai agent run* (run.go): Locally running agents now get the same env var names the platform injects into hosted containers:

  AZURE_AI_PROJECT_ENDPOINT  → FOUNDRY_PROJECT_ENDPOINT
  AZURE_AI_PROJECT_ID        → FOUNDRY_PROJECT_ARM_ID
  AGENT_{SVC}_NAME           → FOUNDRY_AGENT_NAME
  AGENT_{SVC}_VERSION        → FOUNDRY_AGENT_VERSION
  

  Per discussion, azd env keys (AGENT_SVC_NAME_NAME, etc.) remain unchanged for multi-agent support — only the process env passed to the running agent gets the FOUNDRY_* aliases.

• Expose ServiceName on ServiceRunContext (helpers.go): Needed to derive the service-specific AGENT_{SVC}_* keys for the FOUNDRY mapping.

• appendEnvVar helper (init_from_code.go): Nil-safe append since EnvironmentVariables is now nil by default instead of pre-populated.

[jongio]

Translates azd env keys to FOUNDRY_* aliases for local-dev parity with hosted containers.

Issues to address:

• run.go:389 - appendFoundryEnvVars can silently override a user-set FOUNDRY_* value when the corresponding AZURE_* key also exists in the azd env

One question: is there a FOUNDRY_* equivalent for AZURE_OPENAI_ENDPOINT? It's dropped from agent.yaml but doesn't appear in the translation mapping.

[therealjohn]

I ran this branch and it works.

[Copilot]

Pull request overview

This PR updates the Azure AI Agents extension to stop writing legacy Azure endpoint environment variables into agent.yaml during init, and instead aligns local azd ai agent run behavior with the hosted agent container environment by translating azd env keys to FOUNDRY_* aliases.

Changes:

• Stop adding AZURE_OPENAI_ENDPOINT and AZURE_AI_PROJECT_ENDPOINT to agent.yaml during init (model deployment vars still included when applicable).
• Translate local azd environment values to FOUNDRY_* env vars when running agents locally (azd ai agent run).
• Expose ServiceName on ServiceRunContext to derive AGENT_{SVC}_* keys for translation.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
cli/azd/extensions/azure.ai.agents/internal/cmd/run.go	Adds appendFoundryEnvVars and invokes it during local run to supply FOUNDRY_* env aliases.
cli/azd/extensions/azure.ai.agents/internal/cmd/run_test.go	Adds unit tests for appendFoundryEnvVars mappings and skip behavior.
cli/azd/extensions/azure.ai.agents/internal/cmd/init_from_code.go	Removes pre-populated endpoint env vars from generated agent.yaml and adds nil-safe appendEnvVar.
cli/azd/extensions/azure.ai.agents/internal/cmd/init_from_code_test.go	Updates agent.yaml writing assertions to ensure removed env vars are not emitted.
cli/azd/extensions/azure.ai.agents/internal/cmd/helpers.go	Adds ServiceName to ServiceRunContext and populates it during resolution.

[github-actions]

📋 Prioritization Note

Thanks for the contribution! The linked issue isn't in the current milestone yet.
Review may take a bit longer — reach out to @rajeshkamal5050 or @kristenwomack if you'd like to discuss prioritization.

[jongio]

Previous comments addressed. Env var collision handling and process env checks look good. Clean PR.