I created a MVC3 project and attached an Azure Cloud Service for deployment to an Azure Web Role. I created two .cscfg files for PRODUCTION and TEST. These two services have different SSL certificates with different thumbprints – which are set up in the appropriate .cscfg files. In my role I set up an https endpoint and selected the correct config setting for the SSL Certificate Name.
The problem — Visual Studio will not publish to the web role on Azure unless all .cscfg files contain the exact same SSL thumbprint. If I have different thumbprints for the Certificate in the .cscfg files (for PRODUCTION and TEST) it refuses to publish saying that:
Error: Certificate: ‘SSLCert’ with Thumbprint: for Role: XXXXX has not been uploaded to the cloud service: XXXXX
How do I set up the configuration to allow for separate SSL certificates?
I would like to say that is a known issue with Windows Azure SDK and currently being worked on. I do not have any specific details about the fix availability and can not comment on this regard.
Above you already have some workaround to manually publish the package however if you want to still solve your problem within the toolset, you can transform the CSDEF/CSCFG configuration files during the build step as described below:
http://blogs.msdn.com/b/philliphoff/archive/2012/07/02/transform-windows-azure-service-model-files-during-packaging.aspx
Once you transform your config file, you can still use the same build/publish steps and you don’t require manual publishing.