One of my blog readers has asked me about policy for sending Azure Activity logs to Log Analytics. As I have written before this is now possible via diagnostic settings at subscription level and thus is easier to make this into policy.
Today we are releasing another chapter in preview for Inside Azure Management v4 book. This one is focused on automation in Azure. As I have mentioned before this will be free book with option to purchase via Amazon as well. On this blog post I would like to thank the main authors of the book Pete Zerger, Tao Yang and Kevin Greene. Additionally I would like to thank as well to Ryan Irujo, Alexandre Verkinderen and Bert Wolters who also helped with a few chapters. Download the chapter and subscribe for future book updates from by clicking on the book cover below.
These are challenging times for the whole world but to stay true to ourselves we are preparing for the release of the 4th edition of Inside Azure Management book. We expect to be ready no later than 15th of May but as you can understand many of us are busy supporting our customers from home. The book as always will be free download but of course you will be able to purchase it via Amazon as well if you want to. Return to this blog post in a few days to check for the Amazon link. We have worked hard to update the content to the latest changes inside Azure but also to give you some new scenarios.
In IT naming of resources has been around for quite some time. In some of the early days IT personal was using super hero names, constellation names, etc. to name their servers. That was when the number of servers count was equal or less than your fingers. Over the years the number of servers has went up which required using naming convention. Another need for the naming convention was also the different role each server had. Of course with the coming of the cloud the result is that even more resource started to be generated. Strangely though we haven’t changed much our guidelines for naming resources much compared to how we did it on-premises. But may be it is time to change them?
I have promised that I will write the last part of this series and I am doing it later than never. After the December holidays I have been occupied with some community stuff that hopefully will see light in the next months. Due those community duties I was not able to write the last part sooner.
In this last part we will cover Azure Alerts Common schema. I will try not to cover things that are already in the official documentation but I want to mention a few important things. If you haven’t checked the documentation please do before reading the rest of the blog post.