Aller au contenu principal

Enable Global Secure Access for Microsoft Copilot Studio agents

Implementation Effort: Low - Enable supported forwarding once prerequisites are in place.
User Impact: Low - Forwarding alone does not block traffic; subsequently enforced policies can affect agent actions.

Overview​

Microsoft Copilot Studio integrates with Global Secure Access (GSA) to make supported agent interactions observable and subject to destination, threat-intelligence, and content policies. This supports Verify explicitly through network policy decisions and Assume breach by reducing unmonitored agent egress.

Prerequisites​

  • Complete AI network readiness, including licensing, feature availability, and approval for applicable preview features.
  • Global Secure Access Administrator and Power Platform Administrator access for their respective configuration tasks.
  • A Power Platform environment with Dataverse.
  • An inventory of supported connectors and actions, plus a pilot environment with a recovery plan.

Limitations​

  • Forwarding is not enforcement. Copilot Studio uses the baseline security profile; Conditional Access-linked security profiles are not supported for this integration.
  • New custom connectors inherit the forwarding setting, but existing custom connectors do not inherit it automatically.
  • Coverage excludes Bing, public-website and Wikipedia knowledge transactions; Dataverse and Azure SQL knowledge-source requests; and large language model requests for orchestration or result enhancement. Supporting a Dataverse connector does not imply support for its knowledge-source path.
  • Only listed connectors are supported. Third-party GSA data loss prevention partner integrations are not supported.
  • Local endpoint agents require a separate acquisition path, such as Agentic Acquire.

Reference​