I have used VS 2013 for years to web Deploy Apps to Classic Azure VMs without issues. You simply enter the Server name without specifying http or http, ex. abc.com:8172, and Web Deploy converts it on the fly to https. It does not care whether the certificate is trusted or not.
With the new Azure VMs that are based on the Resource Manager, Web Deploy fails to connect if the certificate is untrusted. It does not tell you that it is a certificate problem but once you place http:// before the host, it deploys easily. This suggest that it will not use untrusted certificate, the sort that comes with Azure platform, but no where does it tell you how to overrie this behaviour.
Some have suggested that this can be overridden but without saying exactly how. An article on Stackoverflow says, "In the publish profile window, You need to check the 'Allow untrusted certificate' checkbox", but it does not say where to find
this checkbox in VS 2013. It may be that previous versions of VS had this check box but the VS 2015 Web Deploy Profile dialog does not. Is there a config file where you tell Web Deploy to accept untrusted certificates? If so, then how? Has anyone successfully
Web Deployed from VS 2013 to the new Azure VMs securely with the untrusted certificates from Azure?