17  

1)You upload the certificate to the Service Certificates section on the Windows Azure Portal - just as you did originally.

1）您将证书上载到Windows Azure门户上的“服务证书”部分 - 就像您最初一样。

2) You modify the Service Configuration file to provide the thumbprint of the new certificate instead of the old one. This causes the certificate to be deployed to each instance.

2）您修改服务配置文件以提供新证书的指纹而不是旧证书。这会导致证书部署到每个实例。

3) You do an in-place upgrade or (use a VIP Swap) which causes IIS to start using the new certificate.

3）您进行就地升级或（使用VIP交换）导致IIS开始使用新证书。

4  

First you upload the new certificate using the Management Portal - go to Certificates tab of your cloud service.

首先使用管理门户上传新证书 - 转到云服务的“证书”选项卡。

Then if you believe in in-place reconfiguration (which I don't recommend for this scenario) you can go to Configure tab, scroll down to Certificates, change the thumbprint (you can get it from the Certificates tab) and click Save. Just don't forget to update your .cscfg files so that you have the changes preserved when you redeploy.

然后，如果您相信就地重新配置（我不建议在此方案中使用），您可以转到“配置”选项卡，向下滚动到“证书”，更改指纹（可以从“证书”选项卡中获取）并单击“保存”。只是不要忘记更新.cscfg文件，以便在重新部署时保留更改。

If you don't believe in in-place reconfiguration you'll have to change your .cscfg files and deploy your service into staging with the updated .cscfg and then do VIP swap and delete the previous deployment. This is what I recommend for this scenario because should anything go wrong with in-place reconfiguration you can experience service downtime.

如果您不相信就地重新配置，则必须更改.cscfg文件并使用更新的.cscfg将服务部署到暂存，然后执行VIP交换并删除以前的部署。这是我对此方案的建议，因为如果就地重新配置出现任何问题，您可能会遇到服务停机时间。