The agent cannot reach a package registry during its task. What is the likely cause?
Why C is the answer
The firewall limits its internet access, so add the host to the allowlist
By default, a firewall limits Copilot's internet access. You manage it from the Internet access settings.
In detail
- A firewall limits the agent's internet access by default.
- Add the host to the allowlist.
- Add only the hosts that are needed.
Use case
An illustrative scenario, not a real incident.
A build fails fetching a package from a private registry. The firewall limits internet access, so an admin adds that host to the allowlist.
See it in different ways
flowchart TD A["Cloud agent"] --> B["Pushes to a single branch"] A --> C["Cannot approve or merge"] A --> D["Workflows wait for approval"] A --> E["Internet access limited by a firewall"]
mindmap
root((Agent limits))
Identity
Write access to trigger
Repository
One branch
Branch protection
Tools
MCP allow list
Tool permissions
Network
Firewall allowlistsequenceDiagram participant P0 as Agent participant P1 as Firewall participant P2 as Registry P0->>P1: Fetch package P1-->>P0: Host not on the allowlist P1->>P2: Allowed after it is added
Key point: The firewall limits the agent's internet access.
Why the other options are wrong
- A. The agent has reached its limit of one network request per session
- There is no one-request limit.
- B. The pull request template does not mention the package registry
- A template has no effect on network access.
- D. The repository has too many open issues for it to download packages
- Open issues have no effect on the network.