Certificate Authentication in Key Vault
<p>I have some secrets that I would like to keep in Azure Key Vault. I know I can use a client id and certificate to authenticate with Key Vault instead of using a client and and secret following these steps:</p>

<ol>
<li>Get or Create a Certificate</li>
<li>Associate the Certificate with an Azure AD application</li>
<li>Add code to your application to use the Certificate</li>
</ol>

<p>Most examples use either makecert or New-SelfSignedCertificate to create the certificate. Is a self signed certificate problematic in this case for a production application? This is only for an application to authenticate with Azure Key Vault and it's not something a client will ever see in their browser.</p>

<p>If a self signed cert is still frowned upon in this case then is purchasing a cert from a trusted authority the same process as purchasing an SSL/TLS certificate? Is it even the same type of certificate?</p>