Update existing Microsoft Copilot Studio connectors to route through Global Secure Access
Implementation Effort: Medium - Requires inventorying existing custom connectors and coordinating their routing updates with application owners.
User Impact: Low - Routing updates are normally transparent, but subsequently enforced policies can block existing actions.
Overview
Enabling Global Secure Access (GSA) for a Microsoft Copilot Studio environment does not automatically apply forwarding to existing custom connectors. Updating those connectors closes the gap between environment enablement and protection of the agents already using them.
This supports Verify explicitly by establishing coverage for each connector rather than assuming it inherited the environment setting. It supports Assume breach by reducing unprotected legacy routes to external services.
Prerequisites
- Copilot Studio environment forwarding is enabled.
- Administrators or owners have permission to maintain the affected connectors.
- An inventory identifies connector destinations, owners, agent usage, and business-critical dependencies, including shared connectors.
- The current supported connector list, a test window, and a recovery process are agreed with application and network owners.
Limitations
- Existing connectors need a separate routing update; new custom connectors created after enablement inherit the configuration automatically.
- Forwarding does not prove that policies are enforced. The baseline security profile must activate the intended supported policies.
- Unsupported or unverified connectors remain coverage gaps, even when the environment setting is enabled.
- Connector removal and permission changes require separate approval; they are not implicit parts of a routing update.