Cloud applications and services use cryptographic keys and secrets to help keep information secure. Azure Key Vault safeguards these keys and secrets. When you use Key Vault, you can encrypt authentication keys, storage account keys, data encryption keys, .pfx files, and passwords by using keys that are protected by hardware security modules (HSMs).

Create KeyVault

The following table shows you the steps for Azure KeyVault Creation:

| Task | Image | | —- | —– | | 1. Open Azure Portal | | | 2. Start with Create a resource | _images/keyvault1.pngCreateNewResource | | 3. In the search field type in Key Vault and conform with enter | | | 4. On the detail page click Create | _images/keyvault2.pngCreateKeyVault | | 5. Name, Subscription, Resource Group and Location are required fields | _images/keyvault3.pngRequiredFields | | 6. Conform with Create an wait for successful deployment | | | 7. Open the recently created Key Vault | | | 8. Click Add new to add a new access policy | _images/keyvault4.pngAddNew | | 9. Select Key, Secret & Certificate Management as template and add RealmJoin as principal | _images/keyvault5.pngKey,Secret & Certificate | | 10. For Cryptographic Operations add Decrypt, Encrypt, Unwrap Key, Wrap Key, Verify and Sign | _images/keyvault6.pngCryptographic Operations | | 11. Confirm with Ok and Save | | | 12. Finally, go to Overview and share the DNS Name with the Glück & Kanja support | _images/keyvault7.pngDNS Name | | Example Value: | |

KeyVault Storage of Secrets

RealmJoin will not be store the secret in any proprietary storage but instead create an Azure KeyVault Secret to store it in a secure and auditable way. The KeyVault API is documented here:

The entry in KeyVault will be added with the device name as a key and the plain GUID as the secret value. See the following example screenshot: