I deploy an Azure Website using VS2013, to a test website and to a production website. The two have identical settings (different domain of course) - There is one feature that doesn't work only in production.
I (strongly) suspect that there is an old 3rd party dll (related to that feature) on the production bin folder that causes trouble.
There is no RDP for Azure Websites, so I can't confirm.
Is there a way to force Azure to publish the website to a clean folder?