Forum Discussion
Pipeline IP Question
Whilst this doesn't address your specific issue - I'd like to suggest an alternative approach.
Whitelisting a large range of public IP addresses on your FTP server isn't ideal. If it's possible for you to do so, I'd suggest looking at deploying an Azure resource such as a Virtual Machine (VM) on which you can install the Azure DevOps agent. You can add the VM as a self-hosted agent and set your pipeline to run on there. As the Azure VM is under your control, you can set its public IP address to be static and therefore only need to whitelist the one public IP address on your FTP server. To save on costs, you can power off the Azure VM when you don't need it (either manually or you can automate it).
References:
Whilst this doesn't address your specific issue - I'd like to suggest an alternative approach.
Whitelisting a large range of public IP addresses on your FTP server isn't ideal. If it's possible for you to do so, I'd suggest looking at deploying an Azure resource such as a Virtual Machine (VM) on which you can install the Azure DevOps agent. You can add the VM as a self-hosted agent and set your pipeline to run on there. As the Azure VM is under your control, you can set its public IP address to be static and therefore only need to whitelist the one public IP address on your FTP server. To save on costs, you can power off the Azure VM when you don't need it (either manually or you can automate it).
References: