Ftp connection stopped working on Logic App consumption

Hi @KaziNad ,

"Unable to connect to the remote server… Please verify server logs" usually means the Logic App can’t establish an FTP session with the server from where the connector is running. Since the connection worked for years and then suddenly failed, it’s often related to a change in the FTP server config or network/TLS expectations, or (less commonly) changes in how many concurrent connections your workflow is making.

Here are the most useful things to check based on the provided Logic Apps FTP documentation:

1. Verify the FTP connection details in the Logic App connector:

In your Logic App, update/retest the FTP connection settings used by the FTP actions (host, username/password, port, and whether you’re using the right mode like text/binary transport options if relevant). The FTP connector guidance includes where and how to “create a connection” for Logic Apps workflows.

• If the server started requiring a different connection method/behavior, the existing stored connection may no longer work even though the workflow still deploys.

2. Check for server-side changes that block connectivity

Because the error explicitly says to check server logs, the most likely culprit is something on the FTP server side that changed recently, such as:

• FTP service restarted/reconfigured
• Firewall rules changed
• Rules changed around allowed clients/IPs
• FTP TLS/SSL behavior changed (implicit/explicit TLS requirements, certificate changes, etc.)

Even if you can't access server logs, you can usually ask the FTP server owner/admin to confirm whether anything changed around network access rules or FTP/TLS configuration.

3. If your workflow downloads multiple files in parallel, reduce parallelism

The documentation includes a specific “degree of parallelism” style fix for Logic Apps FTP connectivity failures after server configuration changes. If your workflow uses a For each loop to process multiple files, check the degree of parallelism (example from the known issue: reducing parallelism from 10 =>1 made the FTP connection succeed again).

What to do:

• Find the loop that calls the FTP connector (for example, “Get file content” for each file).
• Set Degree of parallelism = 1 (temporarily to test).
• Re-run / wait for the next batch to confirm the connectivity is stable.

This is especially relevant if your FTP server stopped allowing multiple simultaneous connections.

4. Use the correct trigger/action pattern for Consumption + managed connectors

If you’re using the FTP managed trigger in Consumption or Standard with managed triggers, the known issues note that triggers returning arrays may require additional handling like using Get file metadata and then Get file content, typically inside a For each.

While this isn't directly the same as "can't connect," it can affect how many calls you end up making to the FTP server and therefore how quickly you hit any server limits.

Hi @Pravallika KV ,

Thank you for the suggestions, but I have tried everything I could.

I found something very interesting today. We use westeurope azure region, but today I tried another region and the connection worked very well. The owner of the ftp server states there are no changes at all on his side.

So this is a regional problem in Azure Logic App connectors. Could you please forward this to the appropriate team?

Connection with timeout: x-ms-request-id=f70b7def-ebe2-427f-a7b2-d8efbb385990

Connection with no problem: x-ms-request-id: 8cbc2174-a3d0-4bac-9a2e-e032267bea9a

Many thanks for your help in advance.

Hi @KaziNad , could you please try again now and confirm if the issue still persists?