Wild card managed Azure app certificate added to keyvault as secret and not certificate

Question

I created a managed wild card app certificate in azure, which cost $299.

As part of the creation you must add the certificate to a keyvault and then verify.

After doing these steps (which is a very automated process really) Ive tried to add the certificate into an app services certificates via the Bring your own certificates tab -> Import From Keystore -> Select Key vault certificate . This displays a list of keyvaults and when I go to the drop down to choose our certificate in the Keyvault the drop downs empty.

When looking in the keyvault the app certificate is saved as a secret and not a certificate.

I could export the certificate and import but that would defeat the point of having a managed one that can be synced and updated all at once.
how do i consume my managed wild card certificate in my web apps in a managed way?

Answer 1

@John Harris

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others (Opens in new window or tab)", I'll repost your solution in case you'd like to "Accept (Opens in new window or tab)" the answer.

Issue: Unable to choose wildcard Azure app certificate from KeyVault as a certificate as it is saved as a secret.

Solution: Instead of choosing it from KeyVault, OP moved App Service Certificate from a seperate resource group to production resource group.

If you have any other questions or are still running into more issues, please let me know.
Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer", so that others in the community facing similar issues can easily find the solution.

Thanks,

Akshay Kaushik