Restrict egress domains for data connectors
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Restrict egress domains for data connectors is a Google Cloud guardrail written in organization Policy Service. Allows only URLs with an allowed FQDN to be used by Gemini Enterprise data connectors in projects with VPC Service Controls enabled or in the enforcedProjects list.
More ai services guardrails ยท About Organization Policy Service
constraints/discoveryengine.managed.allowedEgressFqdns
- Blocks
- Allows only URLs with an allowed FQDN to be used by Gemini Enterprise data connectors in projects with VPC Service Controls enabled or in the enforcedProjects list. (Managed constraint.)
- Breaks
- Google documents that, when enforced, only URLs with an allowed FQDN can be used for data connectors in the covered projects. (source)
- Test before applying
- Google documents that managed constraints support organization policies in dry-run mode, where violations are audit logged and the violating actions are not denied, and that managed constraints support Policy Simulator by default. (source)
- Mechanism
- Organization Policy Service (managed and legacy constraints): Resources in the organization, folder or project where the policy is set and its descendants; Google says application of new policies is usually not retroactive.
- Taken from
- provider documentation, provider documentation
What the source says
"This constraint defines the allowed egress fully qualified domain names (FQDNs) for data connectors." (read 10 Nov 2026).
On what it breaks: "When enforced, only URLs with an allowed FQDN can be used for data connectors in projects with VPC Service Controls (VPC-SC) enabled, or projects in the enforcedProjects list."
Related guardrails
- Region deny that allows Bedrock cross-Region inferenceAWS, Service control policies (SCPs), ai services
- Allow only approved Amazon Bedrock modelsAWS, Service control policies (SCPs), ai services
- Deny Amazon Bedrock API keysAWS, Service control policies (SCPs), ai services
- Restrict public IP access on new Vertex AI Workbench instancesGoogle Cloud, Organization Policy Service (managed and legacy constraints), ai services
- Disable root access on new Vertex AI Workbench notebooks and instancesGoogle Cloud, Organization Policy Service (managed and legacy constraints), ai services
- Define access to models on Vertex AIGoogle Cloud, Organization Policy Service (managed and legacy constraints), ai services
Related pages
Sources
- Restrict egress domains for data connectors, read 10 Nov 2026
- How to test it first, read 10 Nov 2026
Last reviewed 16 Nov 2026.