1 voteIan Mercer shared this idea ·
We’ve been unable to reproduce this scenario. Please upload a sample ARM template that you used so can investigate this further.
JasonIan Mercer commented
As @Joel points out the issue happens when you have installed a certificate from the portal and then attempt to do the same from a template. Looking in Azure Resource Explorer the reason for this may be the specific naming that Azure creates when you do a manual upload.
e.g. Portal created certificate: <thumbprint>-<resourcegroup>-appse<location>webspace
Unless you match this exact name you will be trying to create two certificates with different names and the same thumbprint.