chore: main to dev down merge

[Yamini Dhiman (Yamini1-Microsoft)]

Purpose

• This pull request introduces improvements to the process of configuring and troubleshooting Microsoft Foundry agents for integration with Copilot Studio, both in documentation and infrastructure scripts. The changes ensure that the required Activity protocol and authorization schemes are enabled for agents, preventing common setup errors and streamlining deployment.

Documentation updates:

• Enhanced the deployment guide to clarify the agent naming and configuration steps, specifying that the Foundry agent should be named ChatAgent and the Fabric Data Agent should be named RetailSC Ontology Agent.
• Added a troubleshooting section to the deployment guide to address the common "Agent endpoint does not support activity" error, with instructions and an Azure CLI example for enabling the required protocols.

Infrastructure automation improvements:

• Added a new enable_activity_protocol function in agent_api.py to programmatically enable the Activity, Responses, Invocations, and A2A protocols and required authorization schemes on a Foundry agent endpoint.
• Updated the agent setup workflow in step_agent_setup.py to call enable_activity_protocol after agent creation, ensuring agents are configured correctly for Copilot Studio integration.
• Refactored and clarified code for improved readability and maintainability in both agent_api.py and step_agent_setup.py. [1] [2] [3]

These changes collectively reduce manual configuration steps and help prevent integration issues when deploying and connecting Foundry agents with Copilot Studio.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[Copilot]

Pull request overview

This pull request improves Microsoft Foundry agent setup for Copilot Studio integration by automating agent endpoint protocol configuration (to prevent the “endpoint does not support activity” error) and updating the Copilot deployment guide with clearer agent naming and troubleshooting steps.

Changes:

• Added an enable_activity_protocol() helper to patch an agent endpoint to enable Activity/related protocols and required authorization schemes.
• Updated the Foundry agent setup step to call enable_activity_protocol() after agent creation.
• Updated the Copilot deployment guide with explicit Foundry/Fabric agent naming and a troubleshooting section with an az rest example.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
infra/scripts/foundry/step_agent_setup.py	Calls the new endpoint protocol-enablement step after creating/updating the Foundry agent.
infra/scripts/foundry/agent_api.py	Adds enable_activity_protocol() to patch agent endpoint protocol configuration + auth schemes for Copilot Studio.
docs/copilot/DeploymentGuide.md	Clarifies required agent naming and adds troubleshooting guidance for the Activity protocol error.