You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
@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
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?
The text was updated successfully, but these errors were encountered: