Zum Hauptinhalt springen

Enable Global Secure Access for Copilot Studio Agents

Implementation Effort: Low - Enable supported environment forwarding after prerequisites and pilot planning are complete.
User Impact: Low - Forwarding alone does not create blocking policies; subsequently attached policies can interrupt agent actions.
Documentation checked: 2026-11-11

Overview​

Microsoft Copilot Studio integrates with Global Secure Access (GSA) to route supported agent interactions through our Security Service Edge. Organizations can apply supported destination, threat-intelligence, and content policies, and monitor the resulting traffic.

Enable the integration for the intended Power Platform environments or environment groups. New custom connectors inherit the setting; existing custom connectors must be edited and saved. Forwarding and policy enforcement are separate steps.

This supports Assume breach by reducing unmonitored agent egress and Verify explicitly by making supported interactions observable and subject to network policy.

Prerequisites​

  • Complete AI_163 readiness and confirm licensing and feature availability. Some connector support is in preview; review the supported connector list in the linked Power Platform documentation and obtain approval for preview use where required.
  • Global Secure Access Administrator and Power Platform Administrator access for their respective configuration steps.
  • A Power Platform environment with Dataverse added.
  • An inventory of supported connectors/actions and a pilot environment with a recovery plan.

Implementation guidance​

  1. In Power Platform admin center, browse to Security > Identity & access > Global Secure Access for Agents.
  2. Select the intended environment or environment group, select Set up, and enable the setting.
  3. Apply AI_023 to existing custom connectors. Do not assume enablement retrofits them automatically.
  4. Configure applicable policies and complete AI_027 baseline attachment. CA-linked security profiles are not currently supported for this integration.
  5. Test supported HTTP actions, connectors, and MCP interactions used by the environment. Compare them with the current supported connector list before expanding rollout.

Validation and completion evidence​

  • Record enabled environments, owners, rollout date, and connector inventory.
  • Demonstrate a supported permitted action and an action blocked by an attached baseline policy.
  • Correlate each test with traffic logs. The recorded agent name is currently its unique schema name.
  • Document expected error handling: blocked HTTP actions can return 502 Bad Gateway; connectors can return 403 Forbidden.

Scope and limitations​

Do not describe this integration as protection for every Copilot Studio transaction. Documented exclusions include Bing/public-website/Wikipedia knowledge transactions, Dataverse and Azure SQL knowledge-source requests, and LLM requests for orchestration or result enhancement. A supported Dataverse connector does not imply support for the Dataverse knowledge-source path.

Only listed connectors are supported. Third-party GSA DLP partner integrations are not supported.

This control does not route local endpoint agents; use Agentic Acquire for that scenario.

Reference​