Thank you for posting your query on Microsoft Q&A. From above statement I concluded that you want to store and encrypt secrets in Azure Key Vault with your own keys.
Please do correct me if this is not the case.
At this point in time we could use customer managed keys for encryption only for storage blobs.
For Azure Key vault secrets as per Encryption docs:
All secrets in your Key Vault are stored encrypted. Key Vault encrypts secrets at rest with a hierarchy of encryption keys, with all keys in that hierarchy are protected by modules that are FIPS 140-2 compliant. This encryption is transparent, and requires no action from the user. The Azure Key Vault service encrypts your secrets when you add them, and decrypts them automatically when you read them. The encryption leaf key of the key hierarchy is unique to each key vault. The encryption root key of the key hierarchy is unique to the security world, and its protection level varies between regions:
- China: root key is protected by a module that is validated for FIPS 140-2 Level 1.
- Other regions: root key is protected by a module that is validated for FIPS 140-2 Level 2 or higher.
However if this is impacting your business requirements, I recommend you to post your idea on our feedback portal and let me know so that I could also vote for it.
Thanks,
Akshay Kaushik
Please "Accept the answer" (Yes), and share your feedback if the suggestion answers you’re your query. This will help us and others in the community as well.