An Azure service for ingesting, preparing, and transforming data at scale.
Thanks for reaching out! Currently the built-in Azure Data Factory SFTP connector only accepts OpenSSH keys in the classic RSA (or legacy DSA) PEM format – it doesn’t yet support ECDSA private keys. You’ll see in the docs (under “Use SSH public key authentication”) that the connector only recognizes:
• Keys beginning with “-----BEGIN RSA PRIVATE KEY-----” • (Or “-----BEGIN DSA PRIVATE KEY-----”)
Because ECDSA keys start with “-----BEGIN EC PRIVATE KEY-----” (or with the newer OpenSSH “PRIVATE KEY” banner), the ADF connector will reject them today.
Possible workarounds:
- Stick with an RSA key pair for your ADF → SFTP link, and rotate it regularly per your security policy.
- If you must use ECDSA, stand up a self-hosted integration runtime (e.g. on a Linux VM) and invoke your own SFTP script (ssh/scp or a small Azure Function/python script) that supports EC keys—and have ADF trigger that script.
- Submit a feature request on UserVoice/Feedback for ECDSA support in the ADF SFTP connector.
If none of these fit, you could also look at the new Azure Blob Storage SFTP service (if you’re targeting Azure Storage rather than a third-party box) since that SFTP endpoint does support ECDSA host/public-key algorithms.
Let me know if that helps or if you need more detail on any of the workarounds!
Reference links
• SSH public-key auth in ADF SFTP connector (RSA/DSA only):
https://learn.microsoft.com/azure/data-factory/connector-sftp#linked-service-properties
• Supported algorithms in Azure Blob Storage SFTP (ECDSA hosts allowed): https://learn.microsoft.com/azure/storage/blobs/secure-file-transfer-protocol-support#supported-algorithms