Recs.
Updated
Specs
Pros
Pro Can be public facing or internal only
If you need the solution to be accessible over the internet (e.g. for third parties to use); it can be. If you don't have that need though, you can improve security by making it accessible only within your own network, by associating a private endpoint with the storage account.
Cons
Con Limitted options for users
Each user must be setup under the SFTP service and given a root directory, then they're assigned a password or key. There's no option to use other authentication mechanisms (e.g. AAD), or to manage users outside of the SFTP solution (e.g. AAD groups), or even to specify your own credential(s) for the account (though this point is double edged, as this does improve security).
Con Doesn't support FTP(S), or many other protocols
This solution only supports FTPS*; other common protocols such as FTP(S) and WebDav can't be used with this solution.
- Note: There are other ways of accessing the storage account; e.g. Azure Storage Explorer, via the native REST API, or using the Azure SDK.