I’m interested in finding a way to create the KeyCredential using PowerShell - but w/o creating self-signed cert on the developer’s machine as the documentation for New-AzureADApplicationKeyCredential
illustrates.
I’d like to generate the cert using KeyVault as described here and then pass the New-AzureADApplicationKeyCredential cmdlet an alternative parameter set - one that would only take the KeyVaultId and Secret/Certificate name. This doesn't appear to be supported.
Is there an alternative way for me to accomplish the goal of not creating the cert locally, but still affixing it to the ADApplication?