Update Existing Copilot Studio Connectors to Route Through Global Secure Access
Implementation Effort: Medium - Requires identifying all existing Copilot Studio custom connectors and editing each one to apply the Global Secure Access routing configuration; new connectors inherit routing automatically.
User Impact: Low - Routing updates are normally transparent, but newly enforced policies can block existing actions.
Documentation checked: 2026-11-11
Overview
Enabling Global Secure Access (GSA) for a Copilot Studio environment does not automatically update existing custom connectors. Edit and save each existing custom connector to apply the forwarding configuration to its traffic. New custom connectors created after enablement use the configuration automatically.
This task closes a migration gap between enabling the environment and enforcing protection for its supported existing connector traffic. It also establishes an inventory and owner for each route.
This supports Verify explicitly by requiring observed forwarding, not an assumed inheritance of settings, and Assume breach by identifying unprotected legacy routes.
Prerequisites
- Complete AI_022 environment enablement.
- Identify administrators/owners permitted to maintain connectors.
- Review the current supported connector list and known exclusions.
- Agree a test window, rollback process, and policy configuration with the network team.
Implementation guidance
- Inventory existing custom connectors in every enabled environment, including connectors shared by multiple agents or solutions. Record destination, owner, agent usage, and business criticality.
- Review unused connectors and unapproved destinations with the application owner. Removal or permission changes require their own approval.
- Open, edit, and save each in-scope existing custom connector using the supported Power Platform experience.
- Invoke a representative agent action through each updated connector. Confirm the request is visible in GSA logs.
- After AI_027 activates the intended policies, validate both approved and prohibited destinations.
- Record exceptions and include connector routing validation in change and release procedures.
Validation and completion evidence
- Each in-scope connector has a recorded update date, owner, test result, and correlated transaction.
- A new connector demonstrates automatic forwarding.
- A representative migrated connector is subject to the expected baseline policy.
- Unsupported or unverified connectors are explicitly recorded, not marked protected.