Shell tool network_policy.allowlist rejected because container network access is disabled

Question

Shell tool network_policy.allowlist rejected because container network access is disabled

Dilan Wijenayake 0

I am using the Azure AI Foundry Responses API with a shell tool configured with environment.type: 'container_auto'. I need the shell container to access only an allowlisted domain (www.github.com)

{
   type: 'shell',
   environment: {
      type: 'container_auto',
      memory_limit: '1g',
      file_ids: fileIds,
      network_policy: {
         type: 'allowlist',
         allowed_domains: ['www.github.com'],
        }
     },
 }

Which Azure AI Foundry, Azure tenant, subscription, or organization policy controls network access for container_auto shell environments? Can an administrator enable allowlisted outbound domains, and where is that setting configured?

I am specifically looking for the policy name, portal location, required permissions, or support request needed to enable this capability.

Dilan Wijenayake 0 Reputation points

2026-09-04T10:15:41.04+00:00

Error I get: 400: Network policy 'allowlist' is not permitted because the organization policy disables container network access.

1 answer

Your answer

Dilan Wijenayake 0 Reputation points

2026-09-04T10:15:41.04+00:00

Error I get: 400: Network policy 'allowlist' is not permitted because the organization policy disables container network access.

Answer 1

Welcome to Microsoft Q&A,

@Dilan Wijenayake I hope you are doing well,

The 400 error indicates that the allowlist configuration is being rejected because container network access is disabled for your organization/environment. This happens before the shell container executes, so changing allowed_domains or the API request itself will not resolve it.https://learn.microsoft.com/en-au/answers/questions/5838962/unable-to-use-openai-responses-api-shell-tool-with

I recommend checking the following:

In the Azure portal, open the Azure AI Foundry/Azure OpenAI resource used by the Responses API.

Check Networking and look for the outbound network access configuration.

If outbound access is restricted, determine whether your organization allows changing that setting.

If the setting is unavailable or locked, check Azure Policy assignments at the subscription or management-group level. A higher-level policy may be enforcing the restriction.

After network access is permitted, retry the same container_auto request with your allowlist for www.github.com.

Microsoft documentation https://learn.microsoft.com/en-us/azure/ai-services/cognitive-services-virtual-networks?tabs=portal confirms that the shell container supports an allowlist network policy with specified domains. If your organization intentionally disables container network access and you cannot change the policy, the alternative is to perform the GitHub/network operation in your own application/backend and pass the resulting data to the model.

If this answer helped clarify the platform capabilities and save you troubleshooting time, please consider marking it as Accepted. This helps others in the community find similar solutions.