Azure Bicep fail() function was introduced in Bicep CLI v0.33.93. In short this function allows you to fail your deployment when certain conditions are met. In this blog post we will look at how to use it in real world example.
If you are familiar with Log Analytics you will know that you can delete custom field/column directly from the UI as you can see below:
For example I can delete custom field _ResourceId_s for MyLog0001_CL table. That option has been there for quite some time. A couple of years ago an API was made available so you can delete specific data from a table. This was also know as the purge API. The purge API is basically deleting data based on KQL query. With these APIs you could delete specific fields and data but the table that was created by custom log will still be in the Log Analytics.
I have been away for a while but now I am back again. As always this blog post will cover Azure services, particularly Azure subscriptions, tags, Azure Policy and ARM Templates.
Azure recently introduced the possibility to assign tags on Azure Subscriptions. Currently the full support for that is still in progress but there are few things possible currently like:
On 31st of March I will be bringing session for Azure Virtual Day. The title of the session is Tips and Tricks on Azure Monitor Alerts. I will go through the different types of Azure Monitor alerts and will share my insights on using those. You can check the full schedule of the event from the link below:
Another week another part of the Azure Monitor Alert series. This part put the end of alert based on Azure Activity log. Today we will have a look at:
Cloud Administrator in Azure World 