Question

When I 'publish' my solution to azure from visual studio, the instances are created and assigned a certificate from the local cert store "Windows Azure Tools Certificate". However when I package the solution and upload manually via the portal, the deployment fails complaining that there is no corresponding certificate with the specified thumbprint.

I need to provide a 'proof of concept' deployment package to a vendor for them to install on their local azure environment for testing, but I'm not sure how to approach the certificate issue.

  • Is there a way to include the certificate in the deployment package package?
  • When did the "Azure Tools Certificate" in my local certificate store get created?
  • What is the best approach to providing a deployment package to a third party to ensure the valid certificates are in place?
Was it helpful?

Solution

The Windows Azure Tools Certificate is the RDP certificate that is automatically created for you. You can remove RDP from the package and then send a clean package to them with no certificates. If they want to enable RDP on that package then they can just deploy it to Azure and then turn on RDP in the configuration dashboard for that service.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top