Allow Copilot Automations to run on specific environments (e.g., self-hosted Actions runners) #4188

Problem

Copilot Automations currently execute on GitHub-hosted infrastructure only. This blocks automations that need access to private/internal resources — on-prem databases, internal APIs, VPN-only services, or company intranets — since there's no way to route the execution to a controlled network location.

Proposed Solution

Let users configure an Automation to run on a specific execution environment, similar to how GitHub Actions supports self-hosted runners. Users would register a self-hosted runner (or reuse existing Actions runners) as a valid target, then select it when creating/editing an Automation, instead of being limited to the default hosted environment.

Use Cases

• Automations that query internal/on-prem databases or services not reachable from the public internet.

• Compliance/data-residency requirements where code or data must not leave a private network.

• Reusing existing self-hosted runner infrastructure organizations already maintain for CI/CD.