Microsoft recently introduced a new model for purchasing Azure Log Analytics. To use this new model you will basically have to enable it on per subscription bases. In short you can either continue to use the old models or flip a switch on your subscription to use the new model. You cannot use both models for different workspaces in your subscription and you cannot move between the old models and the new ones without flipping that switch. Of course flipping that switch is easy as going into the Azure Portal -> Azure Monitor -> Usage and estimated costs blade but what about if you want to do this programmatically? Apparently there is a way to do it that way and in this blog post I will show you how.
Seems the new year bring us some bad surprises in terms of security. There has been some rumors and now turned out to be truth that certain processors are vulnerable to certain attacks. Yes processors. That means that affects a wide variety of Operating Systems. As Microsoft puts it:
Microsoft is aware of a new publicly disclosed class of vulnerabilities referred to as “speculative execution side-channel attacks” that affect many modern processors and operating systems including Intel, AMD, and ARM. Note: this issue will affect other systems such as Android, Chrome, iOS, MacOS, so we advise customers to seek out guidance from those vendors.
It took us some time but we’ve managed to update the one and only free OMS book. We had plans to release it earlier but unforeseen things has happened which prevented us to do it earlier. I hope you will understand but you will still enjoy it. The other authors and me put a lot of effort to get it out along with the reviewers.
The new query language of Log Analytics is not included in the book but that should not discourage you as the content is still relevant.
Go grab Inside the Microsoft Operations Management Suite for free. Let us know if you have any feedback.
I mostly would like to thank my fiancée for being patient with me and supporting me while I was writing my chapters.
Make sure to check out this blog post that I’ve wrote on my company’s web site.
Recently I’ve been fairly occupied in writing the second edition of Inside Microsoft Operations Management Suite book but now that I’ve finished my chapters I can go back to writing some blog posts.
Update Workers are like Hybrid Workers but they are automatically registered by the Update Management solution. This creates a problem because there is no way to unregister such server unlike the Hybrid Workers which have PowerShell cmdlets installed locally on the server.
Fear not though. There is easy way to move Update Worker between different workspaces as long as you follow the steps:
There is a new version of the OMSSearch module which mainly includes two new cmdlets.