We need to copy files from a source location that are NOT IN target location (new files).
At the end of copy file process, the file structure in target location is to be the same as source's

is it planned out ?

Does this support movement of content databases from SharePoint on premise to Azure?

Does it do block level data transfer? We regularly use very intermittent, low bandwidth connections so 'full file retry' will often fail. What we need is guaranteed file transfer rather than just flat out speed... maybe a feature where, if file transfer fails, revert to block transfer? That way we'd get the best of both.

Add support for sending data directly to Azure Data Lake

To be honest, haven't yet tried the FDT tool, however, very excited about it. Would the FDT tool be provided as a library for easy integration into external applications? For example, if I have a server in Azure and a client running on a user's workstation, I'd like to have the client use FDT to move files to/from the remote server.
It's probably possible to invoke the FDT client as a separate application from within the client, but, having a library could be a more cleaner way of integration.

Thanks.