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 Usually when we work with Service Bus queues, after a while, we end up with some messages reaching the corresponding Dead-letter queue, which is nothing but a partition inside that queue to store messages that weren’t successfully processed. The reason for the messages ending up in DLQ could be anything starting from lock-duration issue to max delviery count threshold or even a technical issue. Once we have these messages piled up in DLQ, next action should be try to reprocess.

Overview Hello! Microsoft recently announced the general availability of support for Managed Service Identity(MSI) in Azure Automation account. This news has been widely appreciated from Microsoft Azure’s customers as it greatly reduces the pain of managing the Run-As-Account SP certificates, which has been the main authentication method for runbooks running in Automation accounts since the inception of the service. To make the customers adapt this more-secure method, Microsoft has now removed the option to create a Run-As-Account along with the new Automation account.

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.