Need to open additional ports on sftpgo container app

Question

Need to open additional ports on sftpgo container app

Matthew Paul 110

I need to open additional ports on my container app to support FTP.

The container app in question is 'sftpgo' on our subscription id 'P11 in the 'rg-ecodriver-capture-prod' resource group, in the 'cae-7vm7ugkmrxyse' azure container apps environment.

The system only allows you to specify 5 ports and says to contact support if you need more. I've done this previously and it's been set up on the same resource in our staging subscription, but the production system has had deployment setup changes (i.e. location), and the port range has been lost.

Is there a way to relax this limit at the subscription level, as it's going to be common for what we do (large amounts of energy data sent via FTP)?

Vallepu Venkateswarlu 10,260 Reputation points Microsoft External Staff Moderator

2026-07-02T09:44:31.49+00:00
Hi Matthew Paul,

Welcome to Microsoft Q&A Platform.

It looks like you’ve run into the default limit of five additional port mappings per Container App. That cap is a per-subscription, per-region quota and there isn’t a switch in the portal to bump it—you’ll need to open a support request for a quota increase.

Here’s what to do:

File a “Service and subscription limits (quotas)” support request in the Azure portal

In the portal, go to Help + support → New support request

For Issue type, choose Quota

For Quota type, select Container Apps additional port mappings

Specify your subscription, region (where your CAE lives), and the new total number of ports you need

While the request is being processed, prepare your Container App update

If you’re using the Azure CLI or an ARM/Bicep template, you’ll configure the new ports under the ingress section’s additionalPortMappings array.

az containerapp update --name sftpgo --resource-group rg-ecodriver-capture-prod --ingress external --target-port 22 --additional-port-mappings '[{"exposedPort":2121,"targetPort":2121,"external":true}, …]'

Make sure your NSG/VNet rules allow the full range of ports you expose After Microsoft approves and applies your quota increase, redeploy or update your Container App with the expanded port list. You should then see all your FTP ports (PASV range, data ports, etc.) come online successfully.

References: https://docs.microsoft.com/azure/container-apps/quotas https://learn.microsoft.com/dotnet/api/azure.provisioning.appcontainers.containerappingressconfiguration.additionalportmappings?view=azure-dotnet

Please "upvote" if the information helped you. This will help us and others in the community as well.

Your answer

Vallepu Venkateswarlu 10,260 Reputation points Microsoft External Staff Moderator

2026-07-02T09:44:31.49+00:00

Hi Matthew Paul,

Welcome to Microsoft Q&A Platform.

It looks like you’ve run into the default limit of five additional port mappings per Container App. That cap is a per-subscription, per-region quota and there isn’t a switch in the portal to bump it—you’ll need to open a support request for a quota increase.

Here’s what to do:

File a “Service and subscription limits (quotas)” support request in the Azure portal

In the portal, go to Help + support → New support request

For Issue type, choose Quota

For Quota type, select Container Apps additional port mappings

Specify your subscription, region (where your CAE lives), and the new total number of ports you need

While the request is being processed, prepare your Container App update

If you’re using the Azure CLI or an ARM/Bicep template, you’ll configure the new ports under the ingress section’s additionalPortMappings array.

az containerapp update --name sftpgo --resource-group rg-ecodriver-capture-prod --ingress external --target-port 22 --additional-port-mappings '[{"exposedPort":2121,"targetPort":2121,"external":true}, …]'

Make sure your NSG/VNet rules allow the full range of ports you expose After Microsoft approves and applies your quota increase, redeploy or update your Container App with the expanded port list. You should then see all your FTP ports (PASV range, data ports, etc.) come online successfully.

References: https://docs.microsoft.com/azure/container-apps/quotas https://learn.microsoft.com/dotnet/api/azure.provisioning.appcontainers.containerappingressconfiguration.additionalportmappings?view=azure-dotnet

Please "upvote" if the information helped you. This will help us and others in the community as well.