Overview In this post, I am going to show you some ways which can help you to monitor the expiry of your Azure AD Applications’ secrets. Whether you have the secrets stored in a keyvault or not, it does not matter. The list of approaches I am mentioning below will help you in either of the cases. But, you should always store the client secrets in a secured storage with KeyVault being the best and recommended solution for it.

Overview Hello! In today’s post, we are going to talk about how we can implement governance and compliance for a very important resource in Azure which is Azure KeyVault. If you want to learn what is KeyVault, you can read more about it here Now, we all know storing secrets and certificates in KeyVault is considered a best practice when it comes to storing and accessing sensitive information in Azure. And in order to follow this practice, multiple teams in an organization start storing the secrets/keys in the vault without following any standards and regulations.

Hello All! Usually, when we start working on a deployment script, we either go with storing the passwords/secrets in variables in plain text or we tend to provide them at runtime (comparatively more secure). We all have been there. But when we are working with a huge script with a large number of parameters, the latter becomes a pain too. So why not try to find a way in which we can keep those secrets secure as well as handy to use as many times as required.