document update web/certificates in a resource group without having to delete SSL binding of a website
In a web app, we use custom domains with SSL binding to certificates. This certificate (Microsoft.Web/Certificates) is, when importing it in the website, automatically added to the resource group with a very bad name, containing the thumbprint.
Now we are scripting more and more of our resources in bicep, we want to also script this certificate and bind it to key vault. We now scripted our certificate with a better name, but we can not create the certificate because there is already an existing certificate with the same thumbprint.
Is there a guidance on how to fix this without having to remove the SSL binding?
coming back to this, I have tried several things:
- adding a certificate in another resource group, doesn't seem to want a reference to another RG?
- adding a certificate in another region in the same RG: complains about not finding the serverFarmId which is specified on the certificate, which exists
@santo2
Thank you for reaching out to us. We are looking into this issue and will get back to you regarding this.
Hi guys, any update on this?
Hi :-)
Hello, is there still no-one who had a look at this?
@snehaamicrosoft could you please provide an update? We are blocked in moving forward to a full bicep automation... This has been unanswered for very long
@ajay-msft, @Sandeg-MSFT