'runtimes' Folder after Publishing a .Net Core App to Azure Publish Via VS Online

Like @Gregory_Ott I was facing a similar issue where my deployment was an FDD deployment and the 'runtimes' folder was still being created. All I did was, mentioned the runtime and set the self-contained property to false. In the following example I have used dotnet to publish:

dotnet publish -c Release -o ..\publish --runtime win-x64 --self-contained false

The following link should help you with the deployment: https://docs.microsoft.com/en-us/dotnet/core/deploying/deploy-with-cli

These exist because you are building your application as a self contained application as opposed to one that is dependent upon the framework being installed on the machine executing it. Documentation can be found at https://docs.microsoft.com/en-us/dotnet/articles/core/deploying/ describing the various options that can be used to control this output.